Low cost, low power, android ARM system board by Mini-Box.com - pico WiKi - User contributions [en]

Compiling Android from sources

2025-12-18T11:26:01Z

Admin: Change the link to tar.gz file on Google Drive

=Getting Project Source Code=
Our project is hosted at http://gitorious.org/picopc-android-eclair/ 
Follow below steps, it shows how to set up the building environment, how to download android source code and how to build it from scratch.

=Precondition: Sun JDK=
You would need Sun JDK version 1.5 to build Eclair. However, Sun JDK version 1.5 is known to be EOL (End-Of-Line), and Ubuntu Linux 9.10 no longer ships with sun-java5-jdk.

If you are using Ubuntu Linux 9.10, just add these two line in file /etc/apt/sources.list:

deb <nowiki>http://us.archive.ubuntu.com/ubuntu/</nowiki> karmic-updates multiverse
deb-src <nowiki>http://us.archive.ubuntu.com/ubuntu/</nowiki> karmic-updates multiverse

If you are using Ubuntu 10.04 LTS (Lucid Lynx), add this line to file /etc/apt/sources.list:
deb <nowiki>http://ir.archive.ubuntu.com/ubuntu</nowiki> hardy-updates main multiverse
and install Sun JDK 1.5:

$ sudo apt-get update
$ sudo apt-get install sun-java5-jdk
To set the system to use Java 5, you need to update your java alternatives by running

$ sudo update-alternatives --config java
Choose java-1.5.0-sun and it should be done.

=Precondition: git and repo=
Before you download the source, you will need git and repo tools.

On an Ubuntu 9.04 host, you can do the following:

Getting git:

$ sudo apt-get install git-core
Getting repo:

$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
For reference details about Repo, see Using Repo and Git.

= Get picoPC-android source =
==Android Gingerbread==

Download the picopc android gingerbread source code (sources available [http://gitorious.org/picopc-android-gingerbread here]):

$ mkdir picopc-android-gingerbread
$ cd picopc-android-gingerbread
$ repo init -u git://gitorious.org/picopc-android-gingerbread/manifest.git
$ repo sync

==Android Eclair==

Download the picopc android eclair source code (sources available [http://gitorious.org/picopc-android-eclair here]):

$ mkdir picopc-android-eclair
$ cd picopc-android-eclair
$ repo init -u git://gitorious.org/picopc-android-eclair/manifest.git
$ repo sync

'''Archive (warning might get outdated use git):''' 
https://drive.google.com/file/d/1BOcF-lEKEOq3LkEgE4hGvqZw472P4cy8/view?usp=sharing with the md5sum: 057cc88e1a374f68e3b992ca64fe612f
'''Warning: the size of the archive it's 3,264Gb'''

=Build picoPC-android from source=
==Android Gingerbread==
Setup picopc configurations:
$ cd picopc-android-gingerbread
$ . build/envsetup.sh

Start the building process by executing android build system 'm' command

$ make update-api (only on first compilation)
$ TARGET_PRODUCT=picopc m

==Android Eclair==
Setup picopc configurations:
$ cd picopc-android-eclair
$ ln -sf build/buildspec.mk buildspec.mk
$ . build/envsetup.sh

Start the building process by executing android build system 'm' command

$ m

=Installing picoPC-android files=
==Android Gingerbread==
Once successfully built you can use the picopc-tools to extract the rootfs and system images by running the script in: 
$ picopc-tools/android-tools/rootfs-creator/android-2.3/rootfs-generator.sh

The resulting files from the latest/ folder can be copied in the rootfs partition on microSD

==Android Eclair==
Once successfully built you can use the picopc-tools to extract the rootfs and system images by running the script in: 
$ picopc-tools/android-tools/rootfs-creator/android-2.1/rootfs-generator.sh

Talk:Main Page

2020-10-20T11:58:14Z

Admin: Created page with "== Populating MN9 with flash memory - can't find memory == Hi All. I would like to populate the NAND flash footprint on this board. The schematic calls for MT29F2G08ABDWP,..."

== Populating MN9 with flash memory - can't find memory ==

Hi All.

I would like to populate the NAND flash footprint on this board. The schematic calls for MT29F2G08ABDWP, but I can't find this part anywhere.

Which compatible replacement part do you recommend and where could I buy it?

Thanks
Philip
----
''While we were testing NAND, we encountered a lot of CRC errors over a longer period of usage (writes/reads). The number of bad CRC sectors were rising, resulting in unable to load OS from NAND. We didn't get a clear response from ATMEL why this happens but as far as we understood from them, it's related to their implementation of atmel_nand.''

== High delivery cost ==

Hi Mini-Box team!

You have a great product with a really affordable price. But there is one issue - shipping costs.
Board + LCD costs about $104, shipping (to Ukraine - my location) costs $205. Nonsense.

regards,
Alex
----
''I think you choose the "no risk" shipment method by '''UPS''' and that's right the shipping from US to Ukraine is that much because of the distance and risk they assume for it. There are two other methods of shipping, cheaper, but on your risk: 
''You can use: '''Express Mail® International for $47.05''', or '''Priority Mail® International for $37.50''' 
''For more information please contact our sales department on: sales-queries at mini-box.com''
----
Hi all!

Sorry to bust in like this, but could you add some mini PCIe GSM/GPS devices that work with this board?

Regards,
Alex
----
''you have to look for a miniPCIe GSM/GPS that has USB support, like this one: http://www.thinkwiki.org/wiki/Ericsson_F3507g_Mobile_Broadband_Module'' 
''we didn't test it, but the board miniPCIe it's with USB only support''
----

== JTAG/ICE port ==

Question: why there is no ARM JTAG port? 4 USB ports, but no JTAG? Thanks.

== SPI Interface ==

I would like to interface to the SPI driver from an Android java app. Anyone has an example on how to do this? Or maybe point me to a resource that I can start at? thx

===Re: SPI Interface -- [[User:Admin|http://www.mini-box.com]] 02:25, 10 October 2011 (MDT)===

: You should read this: http://www.mjmwired.net/kernel/Documentation/spi/spidev and the example ''spidev_test.c''
: [http://arm.mini-box.com/index.php?title=Kernel_changes_for_custom_hardware#Working_with_SPI See this page].

== C++ Compiler -- [[Special:Contributions/66.195.157.18|66.195.157.18]] 14:03, 10 October 2011 (MDT) ==

I would like to compile a few simple programs on the Mini-box PICo board. What is the simplest way to add a C++ compiler and libs?

== Debian armel -- [[Special:Contributions/24.6.3.23|24.6.3.23]] 15:13, 15 October 2011 (MDT) ==

Hi,

I have Debian armel running on this board now with kernel 3.04 (Zero extra patches :)).

Aside from an issue with the second bank of memory (I'm compiling a kernel that should fix it now) everything works great..

The steps to get this running are:

1 Get another SD card and use another debian machine to create a base chroot for armel on it, use the --foreign option so that it doesn't do the second stage setup.

2 Boot up with the Angstrom image and insert the sdcard with the debian chroot into the reader socket

3 chroot into the debian chroot from Angstrom and run the second stage setup thats in /debootstrap

4 Install GCC etc in the debian chroot and build a kernel (I can supply a working config for 3.0.4).. you need to build a uImage. This will take a few hours!

5 move the linux.bin on the boot sdcard to linux.bin.old or something and copy your new uImage in its place

6 boot angstrom with this kernel to make sure it works

7 chroot into your chroot again, install openssh-server etc so that you can login from debian when you start using it, configure your network interface.. use ifup to test it

8 remove both of the cards, backup the old angstrom root form the boot card, delete its partition and create a new one of the size you need and format it with mkfs.ext3

9 copy the debian chroot from the other sd card into the new root on the boot card.

10 boot it :)

Cheers,

daniel

===Re: Debian armel -- [[User:Admin|http://www.mini-box.com]] 15:55, 15 October 2011 (MDT)===

: Hi Daniel and thank you for your input. Would you like to create a page on our wiki and share complete information about your working? You have to make an account and then to create that page. Thank you

====Re: Re: Debian armel -- [[User:Dgpalmer|Dgpalmer]] 18:16, 15 October 2011 (MDT)====

Hi,

I have started writing the page in Debian. I don't really understand mediawiki's formatting stuff.. so feel free to format it how you like. At the moment I can't get the second bank of RAM to be accessible and I'm trying to get the perfect kernel config.. compiling on the board itself takes a while. ;)
I'll finish up the page later on and fill it out a bit more.

The issue with the second bank is this;

Machine: Atmel AT91SAM9M10G45-EK
Ignoring RAM at 20000000-27ffffff (vmalloc region overlap).

=====Re: Re: Re: Debian armel -- [[User:Admin|http://www.mini-box.com]] 01:36, 17 October 2011 (MDT)=====

::: Hi, Daniel. I published a link to the Debian page on the main page, [http://arm.mini-box.com/index.php?title=Main_Page#Compiling_OS_from_sources here]. If you have any progress you would like to share, please update that page and I will arrange it to wiki format for you. Thank you.

== Mainline support -- [[User:Dgpalmer|Dgpalmer]] 22:58, 15 October 2011 (MDT) ==

As part of getting Debian working on the board I've prepared a few small patches (mainly so that we don't have to use someone else's board type).. Do you guys mind me submitting them for inclusion in the kernel? I'm not sure if they would go in, but its worth a try.

This looks better than it did before ;)

[ 0.000000] Linux version 3.1.0-rc4-dgp (root@ein) (gcc version 4.6.1 (Debian 4.6.1-15) ) #3 Sun Oct 16 04:53:22 UTC 2011
[ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Mini-Box.com pico-SAM9G45

===Re: Mainline support -- [[User:Npavel|Npavel]] 09:01, 16 October 2011 (MDT)===

: We would like to do that, and add a proper board- configuration file, but we're waiting to see if there are any changes to the hardware for the upcoming enclosure/lcd/touch panel.
If you don't mind you can upload the patches, and refer them in the kernel building page till we have a patch. I will make sure that you are included in the credits in our next patch.

====Re: Re: Mainline support -- [[Special:Contributions/24.6.3.23|24.6.3.23]] 21:58, 16 October 2011 (MDT)====

Hi,

I have basically copied the board file that was being used and cleaned up the stuff for the LEDs etc.. and added them to the Kconfig so that you can select the right board :) And added some fixes from other places like enabling the pwm led driver for at91. I've got a pretty clean config that can be used as a defconfig for the board as well.

I'm having trouble getting the second bank of RAM to be usable in 3.1. I need/want to use 3.1 because of fixes/improvements in the mmc driver.
I noticed that you have a patch in the arm linux tracker for 2.6.32. I can't for the life of me get this working (it seems some of the arm memory mapping stuff has changed).
Apparently reordering the banks so that the lower addressed one is first, enabling highmem support and loading the kernel to the lower bank works (near the end of this post -- http://lists.arm.linux.org.uk/lurker/message/20110726.133702.b4d4e58f.en.html).

Do you have any thoughts? Everything is running great.. but only with 128MB of RAM.

=====Re: Re: Re: Mainline support -- [[User:Npavel|Npavel]] 00:23, 18 October 2011 (MDT)=====

::: It looks like we first need to fix Atmel MCI driver.

======Re: Re: Re: Re: Mainline support -- [[Special:Contributions/24.6.3.23|24.6.3.23]] 20:51, 18 October 2011 (MDT)======

The Atmel MCI driver is fixed in the 3.1rc? series. I'm running 3.1.0rc4 right now. Apparently, it has some improvements over the older driver like the ability to use the DMA controller. Atmel seems to have been fairly active lately.

I have the kernel loading into the lower bank of RAM now..

-I- Card size: 1886 MB

-I- Copy "linux.bin" from SdCard to 0x20000000

-I- load: 20008000 jump: 20008000

-I- Loading to 0x20007fc0 with size 0x001947e8

-I- MEDSdcard init

So I see this instead

Ignoring RAM at 70000000-77ffffff (vmalloc region overlap).

I think now we can have a decent memory setup.. instead of having the lower bank mapped after the high bank.

=======Re: Re: Re: Re: Re: Mainline support -- [[Special:Contributions/24.6.3.23|24.6.3.23]] 00:46, 19 October 2011 (MDT)=======

I have both banks of RAM working in 3.1rc4 now. I'll clean up my changes to the kernel and get a patch together that everyone can use.

daniel@ein:~$ dmesg
[ 0.000000] Linux version 3.1.0-rc4-dgp (root@ein) (gcc version 4.6.1 (Debian 4.6.1-15) ) #13 Wed Oct 19 06:37:31 UTC 2011
[ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Mini-Box.com pico-SAM9G45
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] AT91: Detected soc type: at91sam9g45
[ 0.000000] AT91: Detected soc subtype: Unknown
[ 0.000000] AT91: sram at 0x300000 of 0x10000 mapped at 0xfef68000
[ 0.000000] On node 0 totalpages: 65536
[ 0.000000] Normal zone: 2816 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 62720 pages, LIFO batch:15
[ 0.000000] Clocks: CPU 400 MHz, master 133 MHz, main 12.000 MHz
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 62720
[ 0.000000] Kernel command line: mem=128M@0x20000000 mem=128M@0x70000000 console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootdelay=1 rootwait=1
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 128MB 128MB = 256MB total
[ 0.000000] Memory: 256516k/256516k available, 5628k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffa00000 - 0xffe00000 ( 4 MB)
[ 0.000000] vmalloc : 0xd0800000 - 0xfee00000 ( 742 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc02ee000 (2968 kB)
[ 0.000000] .init : 0xc02ee000 - 0xc0309000 ( 108 kB)
[ 0.000000] .data : 0xc030a000 - 0xc032b6a0 ( 134 kB)
[ 0.000000] .bss : 0xc032b6c4 - 0xc0338798 ( 53 kB)
[ 0.000000] NR_IRQS:192
[ 0.000000] AT91: 160 gpio irqs in 5 banks
[ 0.000000] Console: colour dummy device 80x30

========Re: Re: Re: Re: Re: Re: Mainline support -- [[User:Npavel|Npavel]] 10:33, 24 October 2011 (MDT)========

:::::: I added a new kernel branch minibox-picopc-3

=========Re: Re: Re: Re: Re: Re: Re: Mainline support -- [[Special:Contributions/24.6.3.23|24.6.3.23]] 21:26, 25 October 2011 (MDT)=========

Hi,

I couldnt that you had done anything to the upstream source.. so I've created a clone. I will merge my patches into my clone. You can then pull/clean up anything you what to put into the official version.

Cheers,

Daniel

==========Re: Re: Re: Re: Re: Re: Re: Re: Mainline support -- [[User:Npavel|Npavel]] 04:12, 4 November 2011 (MDT)==========

:::::::: You can use this branch for additions: https://gitorious.org/picopc-kernel/kernel/commits/minibox-picopc-3.1-testing

== User Keys/pins -- [[Special:Contributions/76.219.174.46|76.219.174.46]] 19:53, 21 October 2011 (MDT) ==

Hello,
I want to use the "User pins" on the processor,

Marked in the schematic:
"LEFT" = E7
"RIGHT" = B5
"OK" = D6
"USR[1..4]" = F7, A4, C5, B4

I know the schematic says DNP the "[LEFT] [RIGHT] [OK] & User buttons" traces, but is there any other way to get to the "USR" pins on the processor?

PS: I can't wait to see the enclosures for the board:)

== Using ADB USB on Linux -- [[Special:Contributions/95.115.230.174|95.115.230.174]] 03:42, 23 October 2011 (MDT) ==

... doesn't seem to work for me! 
I tried with a couple of different udev rules on Ubuntu 11.04 and Ubuntu 11.10 ... no success, 'adb devices' comes up empty, although 'lsusb' lists the device as: 
Bus 001 Device 005: ID 18d1:9018 Google Inc.
Some strange effect with the 'Eclair' image - the device doesn't show up at all! Any ideas how to make this work - it's a nice board, but basically useless as a development platform right now. 
Regards, 
Steffen Elste

===Re: Using ADB USB on Linux -- [[Special:Contributions/95.115.230.174|95.115.230.174]] 06:02, 23 October 2011 (MDT)===

Update:
Got it working finally - if the board is powered only via the Micro-USB connector 'lsusb' shows the device but 'adb devices' doesn't find it! 
I'm now using this udev rule: 
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="9018", MODE="0666"
which works on either Ubuntu 11.04 and 11.10 
Regards, 
Steffen Elste

== connecting to a bigger LCD -- ==

Hi

I'm looking to connect the pico-SAM9G45 to an 15'' or 17'' LCD screen (not through VGA). I wondered if you know of an LCD screen that would fit? can we connect LVDS screens?

I would appreciate any help.

thanks very much

Lior

== Ethernet access -- [[User:Jex|Jex]] 05:59, 6 November 2011 (MST) ==

Hi,
I just writed and installed my MicroSD with Angstrom Linux and start my card with power on mini USB and ethernet port connected on my router...
My router tell me the ethernet connexion is not running. Then I don't know the IP address of the pico card and can't connect via RSH. Is it a bug or have I first to connect with serial port to configure Linux / Ethernet ?
Best regards. Jacques

===Re: Ethernet access -- [[User:Npavel|Npavel]] 01:22, 7 November 2011 (MST)===

: Make sure your router has a running DHCP server.

====Re: Re: Ethernet access -- [[User:Jex|Jex]] 10:19, 7 November 2011 (MST)====

I restarted the MicroSD Linux installation with a Windows 7 computer. With WinImage tool, I verified the image is correct. It seems OK : I constructed an image of MicroSD after burning and I saw the Linux files in the image. Then I restarted the card with Ethernet. Now, my router tell me there is a connexion, and the Ethernet LED's are active. OK.
Now, can I connect me over Ethernet with rlogin, SSH, or telnet ?
What is the predefined password for root ?

=====Re: Re: Re: Ethernet access -- [[User:Jex|Jex]] 14:10, 9 November 2011 (MST)=====

::: OK, now I can connect with SSH on port number 22... root/root. The problem was to know the IP Address.

== Randomized MAC Address at boot !! -- [[User:Jex|Jex]] 14:16, 9 November 2011 (MST) ==

Hello,
To connect on the card over Ethernet, we need to know the IP address of picosam9.
But, each time we restart the card a new (randomized) MAC address is used. Then, DHCP provides a new IP address to the card at each reboot... Please How can we stabilize the eth0 MAC at boot ?

===Re: Randomized MAC Address at boot !! -- [[Special:Contributions/86.124.49.29|86.124.49.29]] 08:25, 14 November 2011 (MST)===

: There are different methods but the easiest one is to run this command at startup:

ifconfig eth0 hw ether 00:01:02:03:04:05

====Re: Re: Randomized MAC Address at boot !! -- [[Special:Contributions/60.251.198.233|60.251.198.233]] 02:36, 24 February 2012 (MST)====

Hi,

Please advise how to write a permanent MAC address while building a new image.

Thanks,
James

== 3g modem -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 04:28, 14 November 2011 (MST) ==

I inserted an Option GTM617W modem in a pico-SAM9G45 board. The modem is detected and after enabling the hso driver in the kernel the serial ports are setup correctly. However when I reboot the board (without power-cycling) the modem is not detected anymore! To get the modem working again without power-cycling I have to pull the PERST# on the mini PCI express port to 0V. When I release this pin the modem is detected again. I also tried to reset the usb hub by shortening C74, but that does not make the modem detectable again. For now we have a workaround by connecting PERST# to USR1. And in the OS when the modem has not been detected just toggle the USR1 gpio and wait for the kernel to detect it again.

We also have another 3g modem (Huwei E770) but this modem is sometimes not detected (conditions to be detectable are very random). Hub reset or PERST# toggle do not help much.

Now comes the interesting part: When I insert one of the modems above into an USB to mini pci express converter it is impossible to not detect the modem! (everything works as expected)

I suspect the 3.3v power supply on the pico-SAM9G45 board from not delivering enough power to the pci bus, causing the 3g modem in a undesirable state.

===Re: 3g modem -- [[Special:Contributions/86.124.49.29|86.124.49.29]] 08:27, 14 November 2011 (MST)===

: I reported this to the hardware team. Does [http://arm.mini-box.com/index.php?title=Kernel_changes_for_custom_hardware#Power_cycle.2FReset_miniPCI-E_cards_or_USB_devices this method] work for detection ?

====Re: Re: 3g modem -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 12:26, 14 November 2011 (MST)====

:: No, when it is not detected I can not deauthorize my not detected device. What remains is deauthorize the USB hub but that does not make any difference.
:: Why are Q2 and related components not placed? This could help me to switch off/on the USB pci device.

=====Re: Re: Re: 3g modem -- [[User:Npavel|Npavel]] 12:46, 14 November 2011 (MST)=====

::: Does this happen with an external power supply (12V for example) or you use microUSB port for power ?

======Re: Re: Re: Re: 3g modem -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 00:40, 15 November 2011 (MST)======

:::: I just tried it with 15V and 5V on the external power supply and I connected the board with microUSB. All gave the same result. (GTM617W modem, powerup works fine, after reboot it is not detected, after toggling PERST# it is detected again)

== Option GTM671W -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 03:27, 28 November 2011 (MST) ==

The Option GTM671W (only 3g part, wifi uses the pci lanes) 3g modem finally works correctly on the pico-SAM9G45 board. But due to some mini pci express violations an adapter board with some disconnected lines had to be used!

The lines 47, 49 and 51 are defined as reserved. However, the pico-SAM9G45 connects 5V to it. When this modem is used directly it becomes very hot and it is sometimes not detected as an usb device. When the modem stays on for several hours it becomes broken due to the high temperatures, this renders the modem useless and it becomes detected as another device.

To connect this modem to the pico-SAM9G45 board an adapter board is needed because the modem is half-height. On this board the lines 47, 49 and 51 MUST be scratched. After this modification the modem functions correctly.

The question remains why does the pico-SAM9G45 connect 5V to these lines? It is not in the mini pci express 1.2 specification (5V isn't even mentioned there). Is this to be fixed in a future hardware revision?

== HUAWEI EM770 -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 03:53, 28 November 2011 (MST) ==

The HUAWEI EM770 3g modem finally works correctly on the pico-SAM9G45 board. But due to some mini pci express violations an adapter board with a disconnected line had to be used!

Line 20 is defined as W_DISABLE#. According to PCI Express Mini Card Electromechanical Specification Revision 1.2 October 26, 2007, page 48 the modem must pull-up this signal when it implements this function. However, the pico-SAM9G45 connects 3.3V to it. When this modem is used directly it is not detected as an usb device.

When I put an adapterboard in between and scratch line 20 the modem functions correctly!

The question remains why does the pico-SAM9G45 connect +3.3V to this line? It is not very clear to me in the specification but I don't think de-asserted means just connect 3.3V to it, because the card already has a pull-up on this line. Is this to be fixed in a future hardware revision?

===Re: HUAWEI EM770 -- [[User:Npavel|Npavel]] 05:21, 28 November 2011 (MST)===

: Thanks for your findings I alerted the hardware dev team and waiting for an answer.

== Problem compliling Ångström OS on openSUSE 11.4 (32bit) -- [[Special:Contributions/195.234.6.80|195.234.6.80]] 07:33, 19 December 2011 (MST) ==

I've bought pico-SAM9G45. Delivery cost is quite affordable (USPS Express Mail, Ukraine).
Installed and run pre-built OS. Everything is okay.
I tried to build the kernel or a base image Angstrom distribution. After running the commands:

…

MACHINE=picosam9 ./oebb.sh bitbake virtual/kernel

MACHINE=picosam9 ./oebb.sh bitbake base-image

I've got the following error:

“ERROR: Poky's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Do not use Bitbake as root.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed”

What could be wrong?

===Re: Problem compliling Ångström OS on openSUSE 11.4 (32bit) -- [[Special:Contributions/188.227.12.162|188.227.12.162]] 03:10, 31 January 2012 (MST)===

Just don't start bitbake under root account.
I've got another problem with Angstrom: it says that MACHINE=picosam9 is unknown name and doesn't build anything. Does anybody know, how to fix it?

====Re: Re: Problem compliling Ångström OS on openSUSE 11.4 (32bit) -- [[Special:Contributions/207.58.255.194|207.58.255.194]] 11:18, 1 February 2012 (MST)====

I have not been successful generating and compiling the Angstrom build by following the instructions on the Mini-box site. Running the setup-scripts and oebb.sh generates a directory structure that is different than the one specified by Openembedded. I think this is part of the problem There is no mention in the instructions on any mods to local.conf or BBPATH. When I try MACHINE=picosam9 bitbake gpe-image it eventually states 'there is nothing to build'. I have twice built kernel/fs using Openembedded/Angstrom on Atmel devices and there were issues (always issues with Linux) but they were fixed with available patches, etc.

== RS232 to TTL adapter 3.3V -- [[Special:Contributions/193.141.16.74|193.141.16.74]] 08:23, 19 December 2011 (MST) ==

Perhaps it is wise to inform users about the fact that the USARTs operate at 3.3V. When using a standard TTL (5V) to RS232 adapter the processor is operating beyond the absolute maximum ratings.

== USB keyboard -- [[User:Linus63|Linus63]] 06:04, 30 January 2012 (MST) ==

Hello,

I want to know how to connect an USB keyboard with a SAM9G45 card?

Thanks in advance

== Serial on J9 -- [[Special:Contributions/151.13.69.69|151.13.69.69]] 03:46, 7 February 2012 (MST) ==

Hello,
I successful work with serial on J7, using /dev/ttyS2...
but on J9, who ttyS* I use?

Thank

===Re: Serial on J9 -- [[User:RGB&|RGB&]] 08:39, 7 February 2012 (MST)===

: UART2 on J9 is not registered in the kernel. You have to registered it in /kernel/arch/arm/mach-at91/board-sam9m10g45ek

====Re: Re: Serial on J9 -- [[Special:Contributions/151.13.69.69|151.13.69.69]] 10:19, 7 February 2012 (MST)====

:: Much thanks ... I try as soon as I can... However, you must recompile the kernel, what I wanted to avoid.

== ICS Display -- [[User:Rweiland|Rweiland]] 13:28, 10 February 2012 (MST) ==

When booting ICS alpha 1 with 7" Hannstar LCD, I get a digital clock when pressing back button, or "Make yourself at home" when pressing menu. Nothing else. Cockpit error, or expected behavior? Gingerbread works.

Cheers, and thanks for a great product!
Ron

== RTS/CTS on J7 not work -- [[Special:Contributions/151.13.69.69|151.13.69.69]] 05:00, 20 February 2012 (MST) ==

Hello,
using /dev/ttyS2 on J7 and setting by
"stty -F /dev/ttyS2 19200 -raw -echo crtscts", RTS/CTS signal is not enabled properly.

What should I do?

Thank

== NFS or Samba Access from picosam9 -- [[User:Jex|Jex]] 18:19, 7 May 2012 (MDT) ==

Hello,
I use the Angtrom precompiled OS. When I try to mount a filesystem on NFS ressource or Samba ressource I have an error (example for nfs : no such device). Is NFS or CIFS compiled in kernel ? Anyone have succes with networked filesystem ?
Regards

== Need help with powering up pico-SAM9G45 -- [[User:Jphil|Jphil]] 02:50, 10 June 2012 (MDT) ==

I just got my pico-SAM9G45, power adapter and 4.3 LCD screen. all are connected and I have loaded android image on an SD card, not microSD card.

I plugged everything in and powered it up, nothing shows up on the screen.

Are there some basic steps to get it going, first time using this type of motherboard and system, what am I missing?

PLEASE HELP!!!!

THX, Joel

===Re: Need help with powering up pico-SAM9G45 -- [[User:Sweidinger|Sweidinger]] 09:46, 13 June 2012 (MDT)===

: Hi Joel,
i'm an newbie in this board, too.
But I think board can not boot from SD-Card, only from microSD.
Lets have try with the microSD an tell me, if it works. ;-)

Greetings, Stefan

== Howto write an Android App wich controls the Hardware I/O's -- [[User:Sweidinger|Sweidinger]] 05:50, 16 June 2012 (MDT) ==

Hello there,
can someone make a simple Howto for the Android SDK to control the onboard I/O's?

Greetings from Germany ;-)
Stefan.

File:Picture3.jpg

2020-10-20T11:30:57Z

Admin:

File:Picture2.jpg

2020-10-20T11:30:40Z

Admin:

File:Picture1.jpg

2020-10-20T11:30:16Z

Admin:

Connecting With Sam-BA

2020-10-20T11:30:03Z

Admin:

{{MicroUSB-OTG-port}}
 
Download a suitable version of Sam-BA from [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883 here] and install it. 

==Sam-BA on Windows ==

Plug in the pico-SAM9G45 board and it should appear as "atm6124.Sys AMTEL AT91xxxxx Test Board" 

[[File:picture1.jpg|link=]]

Start SAM-BA GUI Application. 
Choose the USB Connection /usb/ARM0. 
Select the the at91sam9g45-ek board in the drop-down menu and press connect. 

[[File:picture2.jpg|link=]]

In the main SAM-BA window you will have:

[[File:picture3.jpg|link=]]

==Sam-BA on Linux ==
Unload usbserial module if it is already running by issuing:
sudo rmmod usbserial
Load usbserial kernel module:
sudo modprobe usbserial vendor=0x03eb product=0x6124
Verify that the USB connection is established:
lsusb -d 03eb:6124

Bus 004 Device 006: ID 03eb:6124 Atmel Corp

Know which USB connection is established:
dmesg
...
kernel: usb 4-2: new full speed USB device using uhci_hcd and address 5
kernel: usb 4-2: configuration #1 chosen from 1 choice
kernel: usbserial_generic 4-2:1.0: generic converter detected
kernel: usbserial_generic: probe of 4-2:1.0 failed with error -5
kernel: usbserial_generic 4-2:1.1: generic converter detected
kernel: usb 4-2: generic converter now attached to ttyUSBx

=> you will have to use /dev/ttyUSBx instead of \usb\ARM0 to connect to your board

NOTE: On some Linux systems, instead of /dev/ttyUSB0, the device that is created may be /dev/ttyACM0 (the dmesg command will show the device). The sam-ba utility will not look for or find this device. The workaround is to create a symbolic link called /dev/ttyUSB0 before running the utility:

<pre>sudo ln -sf /dev/ttyACM0 /dev/ttyS0</pre>

sam-ba will then work correctly. Remember to remove the symbolic link when you are finished using the the utility, so that the system can create a real /dev/ttyUSB0 if needed.

File:Pico-SAM9G45-back-view.jpg

2020-10-20T11:28:12Z

Admin: Blanked the page

Adding a new LCD

2020-10-20T08:26:32Z

Admin: Protected "Adding a new LCD" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

*Use the steps from [[Kernel Building]] page to obtain latest Kernel sources and the tool chain.
*Open the folder '''arch/arm/mach-at91/'''
*Edit the '''board-sam9m19g45ek.c''' on line '''204''' to add your LCD specifications, like: refresh rate, pixcloc, hsync_len etc

Adding a new LCD

2020-10-20T08:26:16Z

Admin: Created page with "*Use the steps from Kernel Building page to obtain latest Kernel sources and the tool chain. *Open the folder '''arch/arm/mach-at91/''' *Edit the '''board-sam9m19g45ek.c''..."

About Mini-Box.com

2020-10-20T08:24:20Z

Admin: Protected "About Mini-Box.com" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

<div style="display: block; width:70%;">
<div style="display: block; float: right; width: 200px; border: 1px solid #ccc; padding: 10px; margin-left: 10px; margin-top: 10px;">Our manufacturing runs are usually cargo sized loads ranging from 5,000 to 50,000 unit runs, with lead times ranging from 4 to 12 weeks, depending on product type. The main warehouse is located in Fremont, CA and we also have an international network of distributors. For small to medium orders, you can buy directly from our web site at [https://www.mini-box.com Mini-box.com]. For larger orders please contact our sales staff or our [https://www.mini-box.com/site/resellers.html international distributors].</div>
[https://www.mini-box.com Mini-box.com], a subsidiary of [http://www.ituner.com Ituner Networks Corp.], is a design and manufacturing company specialized in embedded computers and peripherals. Founded in 1996, [https://www.ituner.com Ituner Networks Corp.] is a privately owned Corporation located in Silicon Valley. Inspired by the unprecedented success of the small form factor mainboards, [https://www.mini-box.com Mini-box.com] has since directed its focus on designing and developing smaller, more compact mini-ITX PC peripherals.
Our engineers have led the market in the miniaturization of the power supply, with the introduction of the first mini-itx power supply. Our PSUs plug directly into the ATX connector thus eliminating the need for the ATX extension cable harness. These miniaturized power supplies are ideal for small PCs where space utilization is paramount for good industrial designs. Since then, [https://www.mini-box.com Mini-box.com] has led the market by designing, developing and manufacturing a wide range of of Patent Pending, high efficiency plug-in small PC [https://www.mini-box.com/s.nl/sc.8/category.13/.f power supplies] modules with a variety of power outputs, footprints and input voltage ranges.
[http://www.ituner.com Ituner Networks Corp.] is manufacturing a series of versatile small mini-ITX and small formfactor enclosures. Among them are the M350 Universal mini-ITX enclosure, M300, M200-LCD, M-200 line of [https://www.mini-box.com/s.nl/sc.8/category.87/.fmini-ITX enclosures] and the [https://www.mini-box.com/ALIX WRAP-boxes]. Our enclosures are designed for general purpose computing, WIFI applications, medical, and industrial applications. For automotive applications, the innovating work of our design team has resulted in the award winning [https://www.mini-box.com/Car-PC-Automotive-Computing-Solutions VoomPC series of enclosures and barebone systems].
[https://www.mini-box.com Mini-box.com] is also the manufacturer of the [https://www.mini-box.com/picoLCD PicoLCD] - a family of Intelligent USB LCD displays with resolutions ranging alphanumeric to TFT color in QVGA, HQVGA, VGA and beyond. 
 
Corporate Address 
Ituner Networks Corp 
44244 Fremont Blvd.
Fremont, CA 94538 

Contact Information 
Sales: [[File:sales.gif]] 
Technical Support: [[File:Support.gif]] 
OEM Inquiries: [[File:Oem.gif]]
Telephone 
U.S. and Intl callers.: 1-510-573-0783 
Fax: 1-510-573-6981
<div style="clear: both;"></div>
</div>

About Mini-Box.com

2020-10-20T08:24:10Z

Admin: Created page with "<div style="display: block; width:70%;"> <div style="display: block; float: right; width: 200px; border: 1px solid #ccc; padding: 10px; margin-left: 10px; margin-top: 10px;">..."

Low cost, low power, android ARM system board by Mini-Box.com - pico WiKi:About

2020-10-20T08:23:56Z

Admin: Protected "Low cost, low power, android ARM system board by Mini-Box.com - pico WiKi:About" ([Edit=Allow only administrators] (indefinite))

File:Pico-SAM9G45-J9-schematic.jpg

2020-10-20T07:59:26Z

Admin:

Android Buttons

2020-10-20T07:59:05Z

Admin:

Using J9, you can enable the actions for the '''HOME''', '''BACK''' and '''MENU''' buttons. 
- Pin 11(TXD2) is for the '''BACK''' button, 
- Pin 12(SPI1_SCMK) is for '''HOME''' button, 
- Pin 13(RXD2) is for the '''MENU''' button. 
- For Ground you can use a single pin. Pin 5 or pin 6. 
Please see the images bellow. 
[[File:J9-connector.jpg|link=]] 
 
'''J9''' connector schematic: 
[[File:pico-SAM9G45-J9-schematic.jpg|link=]]

Android Buttons

2020-10-20T07:58:53Z

Admin:

Android Buttons

2020-10-20T07:58:06Z

Admin: Created page with "Using J9, you can enable the actions for the '''HOME''', '''BACK''' and '''MENU''' buttons. - Pin 11(TXD2) is for the '''BACK''' button, - Pin 12(SPI1_SCMK) is for '''..."

Using J9, you can enable the actions for the '''HOME''', '''BACK''' and '''MENU''' buttons. 
- Pin 11(TXD2) is for the '''BACK''' button, 
- Pin 12(SPI1_SCMK) is for '''HOME''' button, 
- Pin 13(RXD2) is for the '''MENU''' button. 
- For Ground you can use a single pin. Pin 5 or pin 6. 
Please see the images bellow. 
http://arm.mini-box.com/images/J9-connector.jpg 
 
'''J9''' connector schematic: 
http://arm.mini-box.com/images/pico-SAM9G45-J9-schematic.jpg

Template:MicroUSB-OTG-port

2020-10-20T07:55:20Z

Admin: Created page with "<h1>Using microUSB OTG port and SAM-BA</h1> To check if the first stage loader from CPU ROM starts, connect pico-SAM9G45 board to your computer through the microUSB OTG port a..."

<h1>Using microUSB OTG port and SAM-BA</h1>
To check if the first stage loader from CPU ROM starts, connect pico-SAM9G45 board to your computer through the microUSB OTG port and run [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883 SAM-BA]. 
In this case the board should not have a bootable microSD card inserted into the microSD slot. 
If everything is ok, SAM-BA should be able to connect and display DDRAM memory contents if you are using the SAM-BA GUI interface.

OpenUPS2

2020-10-20T07:53:06Z

Admin: Created page with "Content moved [https://wiki.mini-box.com/index.php?title=OpenUPS2 here]"

Content moved [https://wiki.mini-box.com/index.php?title=OpenUPS2 here]

Releases

2020-10-20T07:50:59Z

Template:News

2020-10-20T07:25:15Z

Admin:

* ''' new release of Android OS "Gingerbread" 2.3 stable - kernel version 3.1: - [[Releases|[1]]]'''
* ''' new release of Android OS "Ice Cream Sandwich" 4.0.3 beta 1 - kernel version 3.1: - [[Releases|[2]]'''

* please join '''pico-SAM9G45 Google discussions group''': [http://groups.google.com/group/pico-SAM9G45 http://groups.google.com/group/pico-SAM9G45]

* '''3.1 kernel source code''' for pico-SAM9G45 board released: - [https://gitorious.org/picopc-kernel/kernel/commits/minibox-picopc-3.1 base] & [https://gitorious.org/picopc-kernel/kernel/commits/minibox-picopc-3.1 android]
* working with SPI interface small guide - [[Kernel_changes_for_custom_hardware#Working_with_SPI|[3]]
* new release of Angstrom OS (console and graphical version) for pico-SAM9G45 board - [[Releases|[4]]
* Angstrom OS for pico-SAM9G45 board - compiling steps - [[Compiling_Angstrom_for_pico-SAM9G45|[5]]
* compiling Android 2.3 Gingerbread OS from sources - [[Compiling_Android_from_sources|[6]]

Template:News

2020-10-20T07:24:57Z

Admin: Changed the links to internal links

* ''' new release of Android OS "Gingerbread" 2.3 stable - kernel version 3.1: - [[Releases|[1]]]'''
* ''' new release of Android OS "Ice Cream Sandwich" 4.0.3 beta 1 - kernel version 3.1: - [[Releases|[2]]'''

* please join '''pico-SAM9G45 Google discussions group''': [http://groups.google.com/group/pico-SAM9G45 http://groups.google.com/group/pico-SAM9G45]

* '''3.1 kernel source code''' for pico-SAM9G45 board released: - [https://gitorious.org/picopc-kernel/kernel/commits/minibox-picopc-3.1 base] & [https://gitorious.org/picopc-kernel/kernel/commits/minibox-picopc-3.1 android]
* working with SPI interface small guide - [[Kernel_changes_for_custom_hardware#Working_with_SPI|[3]]
* new release of Angstrom OS (console and graphical version) for pico-SAM9G45 board - [[Releases|[4]]
* Angstrom OS for pico-SAM9G45 board - compiling steps - [[Compiling_Angstrom_for_pico-SAM9G45|[5]]
* compiling Android 2.3 Gingerbread OS from sources - [Compiling_Android_from_sources|[6]]

Template:Pico WIKI Description

2020-10-20T07:22:02Z

Admin: Removed the tooltip info message

'''pico-SAM9G45 highly extensible low cost, low power, pico-ITX compatible board designed and manufactured by [http://www.mini-box.com mini-box.com].''' 
This system board is at the core of a series of small, 
low cost systems with touch screen displays, oriented towards modular hardware I/O configurations. 
[[File:pico-SAM9G45-dev-board.jpg]] [[File:Pico-SAM9G45-back-view.jpg]]
<div style="clear:both;"></div>
[http://www.mini-box.com/pico-SAM9G45-X pico-SAM9G45 board] front and back view
<div style="clear:both;"></div>

Template:Bootstrap-screen

2020-10-20T07:06:06Z

Admin: Created page with "<h2>Using a TTL to RS232 converter</h2> After you connected the board to the serial port on your computer using the above steps and you setup the booting microSD card, open..."

<h2>Using a TTL to RS232 converter</h2>
After you connected the board to the serial port on your computer using the above steps and you setup the booting microSD card, open [http://en.wikipedia.org/wiki/Minicom minicom terminal] (UNIX OS) or [http://www.hilgraeve.com/hyperterminal.html HyperTerminal] (Windows OS) and you should get something like this screen:
<pre style="font-size: medium">
-- pico-SAM9G45 Bootstrap 3.0.1 --
-- AT91SAM9G45-EK
-- Compiled: Sep 9 2011 09:50:06 --
Uncompressing Linux..........................................
Linux version 2.6.32.9 (root@droids) (gcc version 4.2.1) #180 PREEMPT Mon Jul 11 11:52:11 EEST 2011
</pre>

Template:ADB-over-usb

2020-10-20T07:05:20Z

Admin: Created page with "=Using Android ADB interface= ==on Windows PC host== 1. Download latest Google Android SDK version from here: http://developer.android.com/sdk/index.html - If you chose to..."

=Using Android ADB interface=
==on Windows PC host==
1. Download latest Google Android SDK version from here: http://developer.android.com/sdk/index.html 
- If you chose to download the zip archive, then you have to unzip the content in a folder on your PC (i.e. c:\android_sdk) 
- If you chose to download the exe file, after download, double click it to launch the installation wizard and follow the installation steps. 
In both situation you must have installed on your system the latest Java SE Development Kit available for download [http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html here] 
For detailed information about how to install the Google Android SDK on your PC, please read http://developer.android.com/sdk/installing.html
 
2. The '''picoSAM9G45 board''' needs a driver to be recognized by the Windows PC host as an '''android ADB peripheral'''. 
This driver (the latest one) can be downloaded: 
- with the SDK Manager selecting Google repositories and after successful download and install you can find the ''usb_driver'' folder in i.e. ''c:\android_sdk\extras\google'' 
- or directly from https://dl-ssl.google.com/android/repository/usb_driver_r04-windows.zip Unzip the content in the ''extras\google'' folder from your Android SDK installation location (i.e. c:\android_sdk)
 
3. In the ''usb_driver'' folder you will find the '''android_winusb.inf''' file - open it in your favorite text editor (i.e. Notepad)
 
4. Under the section noted as: '''[Google.NTx86]''' (if you are on a x86 Windows version) or '''[Google.NTamd64]''' (if you are on a x64 Windows version) 
'''copy & paste''' the following lines:
; picoSAM9G45 by Mini-Box.com for kernel version up to 2.6.32
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9018
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9018&MI_01
; picoSAM9G45 by Mini-Box.com for kernel version 3.1
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0001&MI_01

where 'USB\VID_18D1&PID_XXXX' it's the 'Hardware Ids' of picoSAM9G45 board that you can find it following: 
Right click on 'My computer', select 'Properties' then 'Hardware', then select 'Device Manager' - here look on the list for '''picopc adb''' or '''Android''' right click on it and select 'Properties' and then go to 'Details' and then select from the list: 'Hardware Ids'
 
5. Save the '''android_winusb.inf''' file and close it.
 
6. Connect picoSAM9G45 board to your USB port using the microUSB cable. If it's not already opened it should start to boot up. 
Go back to 'Device Manager' right click on '''picopc adb''', chose 'Update Driver', do not use Windows Update solution to find the driver, then chose to install from a specific location on your hard drive and point the driver location to the '''usb_driver''' folder where the '''android_winusb.inf''' file is located and then click 'Next' - let the installation complete and after that you have to restart your Windows system.
 
7. After restart the '''Android Debug Bridge''' should be enabled. Look in 'Device Manager'. You should have 'Android Phone' - 'Android ADB Interface'
 
8. Using '''adb''': follow information provided by Google, here: http://developer.android.com/guide/developing/tools/adb.html
 
==on Linux PC host==
1. Download latest Google Android SDK version from here: http://developer.android.com/sdk/index.html 
2. Follow the instruction on how to install the SDK from [http://developer.android.com/sdk/installing.html this page] and also read the [http://developer.android.com/sdk/installing.html#troubleshooting troubleshooting] paragraphs regarding Linux OS 
3. Use this [http://en.wikipedia.org/wiki/Udev udev] rule (thanks to [http://arm.mini-box.com/index.php?title=Talk:Main_Page#Re:_Using_ADB_USB_on_Linux_--_95.115.230.174_06:02.2C_23_October_2011_.28MDT.29 Steffen Elste] contribution)
# pico-SAM9G45 Programmer rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="9018", MODE="0666"
4. Power up the pico-SAM9G45 board using micro-USB cable

Connecting With Sam-BA

2020-10-20T06:55:13Z

Admin:

{{MicroUSB-OTG-port}}
 
Download a suitable version of Sam-BA from [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883 here] and install it. 

==Sam-BA on Windows ==

Plug in the pico-SAM9G45 board and it should appear as "atm6124.Sys AMTEL AT91xxxxx Test Board" 

https://resources.mini-box.com/online/pico-SAM9G45/images/picture1.jpg

Start SAM-BA GUI Application. 
Choose the USB Connection /usb/ARM0. 
Select the the at91sam9g45-ek board in the drop-down menu and press connect. 

https://resources.mini-box.com/online/pico-SAM9G45/images/picture2.jpg

In the main SAM-BA window you will have:

https://resources.mini-box.com/online/pico-SAM9G45/images/picture3.jpg

==Sam-BA on Linux ==
Unload usbserial module if it is already running by issuing:
sudo rmmod usbserial
Load usbserial kernel module:
sudo modprobe usbserial vendor=0x03eb product=0x6124
Verify that the USB connection is established:
lsusb -d 03eb:6124

Bus 004 Device 006: ID 03eb:6124 Atmel Corp

Know which USB connection is established:
dmesg
...
kernel: usb 4-2: new full speed USB device using uhci_hcd and address 5
kernel: usb 4-2: configuration #1 chosen from 1 choice
kernel: usbserial_generic 4-2:1.0: generic converter detected
kernel: usbserial_generic: probe of 4-2:1.0 failed with error -5
kernel: usbserial_generic 4-2:1.1: generic converter detected
kernel: usb 4-2: generic converter now attached to ttyUSBx

=> you will have to use /dev/ttyUSBx instead of \usb\ARM0 to connect to your board

NOTE: On some Linux systems, instead of /dev/ttyUSB0, the device that is created may be /dev/ttyACM0 (the dmesg command will show the device). The sam-ba utility will not look for or find this device. The workaround is to create a symbolic link called /dev/ttyUSB0 before running the utility:

<pre>sudo ln -sf /dev/ttyACM0 /dev/ttyS0</pre>

sam-ba will then work correctly. Remember to remove the symbolic link when you are finished using the the utility, so that the system can create a real /dev/ttyUSB0 if needed.

Connecting With Sam-BA

2020-10-20T06:54:37Z

Admin: Created page with "{{MicroUSB-OTG-port}} Download a suitable version of Sam-BA from [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883 here] and install it. ==Sam-BA on Wi..."

{{MicroUSB-OTG-port}}
 
Download a suitable version of Sam-BA from [http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883 here] and install it. 

==Sam-BA on Windows ==

Plug in the pico-SAM9G45 board and it should appear as "atm6124.Sys AMTEL AT91xxxxx Test Board" 

http://resources.mini-box.com/online/pico-SAM9G45/images/picture1.jpg

Start SAM-BA GUI Application. 
Choose the USB Connection /usb/ARM0. 
Select the the at91sam9g45-ek board in the drop-down menu and press connect. 

http://resources.mini-box.com/online/pico-SAM9G45/images/picture2.jpg

In the main SAM-BA window you will have:

http://resources.mini-box.com/online/pico-SAM9G45/images/picture3.jpg

==Sam-BA on Linux ==
Unload usbserial module if it is already running by issuing:
sudo rmmod usbserial
Load usbserial kernel module:
sudo modprobe usbserial vendor=0x03eb product=0x6124
Verify that the USB connection is established:
lsusb -d 03eb:6124

Bus 004 Device 006: ID 03eb:6124 Atmel Corp

Know which USB connection is established:
dmesg
...
kernel: usb 4-2: new full speed USB device using uhci_hcd and address 5
kernel: usb 4-2: configuration #1 chosen from 1 choice
kernel: usbserial_generic 4-2:1.0: generic converter detected
kernel: usbserial_generic: probe of 4-2:1.0 failed with error -5
kernel: usbserial_generic 4-2:1.1: generic converter detected
kernel: usb 4-2: generic converter now attached to ttyUSBx

=> you will have to use /dev/ttyUSBx instead of \usb\ARM0 to connect to your board

NOTE: On some Linux systems, instead of /dev/ttyUSB0, the device that is created may be /dev/ttyACM0 (the dmesg command will show the device). The sam-ba utility will not look for or find this device. The workaround is to create a symbolic link called /dev/ttyUSB0 before running the utility:

<pre>sudo ln -sf /dev/ttyACM0 /dev/ttyS0</pre>

sam-ba will then work correctly. Remember to remove the symbolic link when you are finished using the the utility, so that the system can create a real /dev/ttyUSB0 if needed.