Openmoko - User contributions [en]

Supported microSD cards

2008-12-05T20:22:01Z

Deichkind: Added Jörgs sticky tape trick

{{todo|Maybe reformat table, see discussion page}}

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a post-september 4th kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you want to exchange your SD card more often: [http://people.openmoko.org/joerg/sdcard-handle/ Jörg] has a nice sticky tape trick to do this with no hassle.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel || Status
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || || ||
|-
| Apacer || microSDHC-4GB || 4GB (SDHC) || class 6? || || {{no}} || || || {{no}} || {{no}} || I/O errors
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}} ||
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || || ||
|-
| Kingston || [[Supported_microSD_cards/SD-C02G|SD-C02G]] || 2GB || ? || ? || {{yes}} || || {{yes}} || {{no}} || {{no}} (see [[Supported_microSD_cards/SD-C02G|SD-C02G]] )
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || || ||
|-
| Kingston || SDC4/8GB || 8GB SDHC || ? || {{yes}} || || || || {{yes}} || {{yes}}
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB (SDHC)|| Class 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-2048-E11MK || 2GB || || || || || detects size incorrectly with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) : see http://docs.openmoko.org/trac/ticket/1815#comment:6 || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || [http://www.sandisk.com/Products/Item(2630)-SDSDQY-8192-A11M-SanDisk_Mobile_Ultra_microSDHC_8GBCard.aspx SDSDQY-8192-E11M/A11M] || 8GB (SDHC) || 6 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 2 || || || || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || || ||
|-
| SanDisk || [http://uk.sandisk.com/Products/ProductInfo.aspx?ID=2702 SDSDQ-016G-E11M] || 16GB (SDHC) || Class 2 || untested || untested || untested || {{yes}}, [[SanDisk/SDSDQ-016G-E11M|see details]] || {{yes}} kernel 2.6.24mw, [[SanDisk/SDSDQ-016G-E11M|see details]] || untested, but should work.|| [[SanDisk/SDSDQ-016G-E11M|WiP]]
|-
| Silicon Power || SP004GBSTH006V10 || 4GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| [http://www.transcendusa.com/ Transcend] || [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD] '''(shipped with FreeRunner)''' || 512MB || || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}}
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ? ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || || || {{no}}, see [http://docs.openmoko.org/trac/ticket/2025 bug #2025]
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || {{yes}} since kernel of 30-Sep-2008 ||
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Verbatim || 47206 || 4GB (SDHC) || Class 6|| || {{yes}} (surely) || {{yes}} (surely) || {{yes}} || {{yes}} || {{yes}} (surely)
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743])
|-
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

User:Deichkind

2008-11-09T11:31:27Z

Deichkind: New page: Because you asked for it. A few information about me: Hello, my name is Marian Flor. I am fiddling with computers and hardware since the mid-eighties. During my studies I worked with the ...

Because you asked for it. A few information about me:

Hello, my name is Marian Flor. I am fiddling with computers and hardware since the mid-eighties. During my studies I worked with the Ultra-VAX and the sleak pizza boxes from Sun Microsystems. Linux affected me since I first heard from it in 1993. On my first own PC (1996) I ran SuSE. But they had an horrible package management and updating was a nightmare, so I switched to Debian in 1999 and got stuck to it. Nowadays I run Linux (preferrable Debian) on almost every device that I own: A Synology NAS ([http://www.nslu2-linux.org/wiki/Optware NSLU2-Linux]), a Linksys WiFi-AP ([http://www.openwrt.org OpenWrt]). And of course on my laptop (Debian amd64) and my new and shiny GTA02. :-D

I was born in nothern germany (hence my nick Deichkind) near the danish border. Later on the [http://en.wikipedia.org/wiki/The_Trials_of_Life "trials of life"] ;-) led me to switzerland, to be more precise to the marvellous city of Zurich where I now live.

If you want to contact me use: deichkind dot 08 at <NOSPAM>schweiz dot eu

SanDisk/SDSDQ-016G-E11M

2008-11-08T19:38:37Z

Deichkind: /* SanDisk SDSDQ-016G-E11M */

__NOTOC__
Tested with an Freerunner (GTA02v6).
Other software setups may work too. Important in any case is to have a recent [[Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND|u-boot in your NAND]].

== Setup ==
* QtExtend 4.4.2 on flash, Debian on microSD
* Kernel 2.6.24 from [http://moko.mwester.net/dl.html#kernels here]
* The card was formatted with ext2 filesystems during Debian installation:
<pre>
root@om-gta02:~# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 245 7832 83 Linux
/dev/mmcblk0p2 246 486192 15550304 83 Linux
</pre>
* '''Most important''': Add extra settle time for sd card, see posting (section references) for a how to.

== Pending Issues ==
* mmcinit reports false card size [https://docs.openmoko.org/trac/ticket/1815 1815]. But works fine once booted.
* [[Booting_from_SD#Booting_from_SDHC_.2F_suspend_problems|Suspend]] may mangle your filesystem. Workaround: Disable suspend or, once mangled: Boot from flash and then issue:

<pre>fsck.ext2 -y /dev/mmcblk0p2</pre>
* Running halt after booted from sd card may mangle your filesystem too. Workaround: add extra sync:
<pre>
sync; halt
</pre>
== References ==
* [http://lists.openmoko.org/pipermail/community/2008-November/035412.html Original posting]

SanDisk/SDSDQ-016G-E11M

2008-11-08T19:38:09Z

Deichkind: Initial description of SDSDQ-016G-E11M status

__NOTOC__
= SanDisk SDSDQ-016G-E11M =

Tested with an Freerunner (GTA02v6).
Other software setups may work too. Important in any case is to have a recent [[Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND|u-boot in your NAND]].

== Setup ==
* QtExtend 4.4.2 on flash, Debian on microSD
* Kernel 2.6.24 from [http://moko.mwester.net/dl.html#kernels here]
* The card was formatted with ext2 filesystems during Debian installation:
<pre>
root@om-gta02:~# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 245 7832 83 Linux
/dev/mmcblk0p2 246 486192 15550304 83 Linux
</pre>
* '''Most important''': Add extra settle time for sd card, see posting (section references) for a how to.

== Pending Issues ==
* mmcinit reports false card size [https://docs.openmoko.org/trac/ticket/1815 1815]. But works fine once booted.
* [[Booting_from_SD#Booting_from_SDHC_.2F_suspend_problems|Suspend]] may mangle your filesystem. Workaround: Disable suspend or, once mangled: Boot from flash and then issue:

<pre>fsck.ext2 -y /dev/mmcblk0p2</pre>
* Running halt after booted from sd card may mangle your filesystem too. Workaround: add extra sync:
<pre>
sync; halt
</pre>
== References ==
* [http://lists.openmoko.org/pipermail/community/2008-November/035412.html Original posting]

Supported microSD cards

2008-11-08T19:10:03Z

Deichkind: /* Cards by Vendor */

{{todo|Maybe reformat table, see discussion page}}

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a post-september 4th kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel || Status
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || || ||
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}} ||
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || || ||
|-
| Kingston || [[Supported_microSD_cards/SD-C02G|SD-C02G]] || 2GB || ? || ? || {{yes}} || || {{yes}} || {{no}} || {{no}} (see [[Supported_microSD_cards/SD-C02G|SD-C02G]] )
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || || ||
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB (SDHC)|| Class 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-2048-E11MK || 2GB || || || || || detects size incorrectly with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) : see http://docs.openmoko.org/trac/ticket/1815#comment:6 || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || [http://www.sandisk.com/Products/Item(2630)-SDSDQY-8192-A11M-SanDisk_Mobile_Ultra_microSDHC_8GBCard.aspx SDSDQY-8192-E11M/A11M] || 8GB (SDHC) || 6 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 2 || || || || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || || ||
|-
| SanDisk || [http://uk.sandisk.com/Products/ProductInfo.aspx?ID=2702 SDSDQ-016G-E11M] || 16GB (SDHC) || Class 2 || untested || untested || untested || {{yes}}, [[SanDisk/SDSDQ-016G-E11M|see details]] || {{yes}} kernel 2.6.24mw, [[SanDisk/SDSDQ-016G-E11M|see details]] || untested, but should work.|| [[SanDisk/SDSDQ-016G-E11M|WiP]]
|-
| Silicon Power || SP004GBSTH006V10 || 4GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| [http://www.transcendusa.com/ Transcend] || [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD] '''(shipped with FreeRunner)''' || 512MB || || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}}
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ? ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || || || {{no}}, see [http://docs.openmoko.org/trac/ticket/2025 bug #2025]
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || {{yes}} since kernel of 30-Sep-2008 ||
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Verbatim || 47206 || 4GB (SDHC) || Class 6|| || {{yes}} (surely) || {{yes}} (surely) || {{yes}} || {{yes}} || {{yes}} (surely)
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743])
|-
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

Talk:Supported microSD cards

2008-11-07T19:58:39Z

Deichkind: /* Reformatting the page */

Let it be known that 4Gb microSDHC cards have been announced by more than one company. Apparently these will not be supported by default in microSD devices. Does anyone know if the Neo will support these in theory? [[User:Wasp|Wasp]] 00:06, 16 February 2007 (CET)

: Also 8GB MicroSD cards have now been announced. Would be really nice to know if it's just a driver issue or something more.

: Anyone tried 16GB microSDHC cards (Sandisk)? - the are now available here in Germany --[[User:Nodge|Nodge]] 08:52, 30 October 2008 (UTC)
: * Yes, I have a SDSDQ-016G-E11M (16GB, Class2) in a Neo-FR in use with Debian (ext2) on it (Qtopia on flash). It can only be boot with manually from NAND. Suspending still causes I/O error on the SD. The rest seems stable. Right now, I don't know how to supply this info in the table. -- Greetings from Switzerland, [[User:Deichkind|Deichkind]] 23:03, 2 November 2008 (CET)

== How to test ==

Can we please define repeatable tests?
atm I just copy stuff there and back - there is probably more to it.
Tested the Sandisk 512 and 1024 cards [[User:Johan|Johan]] 22:27, 4 August 2007 (CEST)

== Use newer kernel/uboot for testing ==

As the 2.6.17 kernel is pretty outdated and openmoko uses 2.6.22 for a long time now, we maybe should use this kernel version for testing, shouldn't we? --[[User:Thomasg|Thomasg]] 16:23, 23 September 2007 (CEST)

i strongly second that.
please do not test with ancient and totally outdated software. this will only generate bogus bugreports which hold everybody from seeing the real problems.
with recent i mean 2.6.22.5-moko11 or newer. please also add the exact release (including svnr if possible) when filing a bug.

same goes for uboot.
currently we are at svnr 2943 or higher. please do not file bugs against uboots which are totally outdated.
if you want to update your uboot for tests, please contact me and i'll try to supply you with a tested uboot for your device. --[[User:Roh|Roh]] 22:03, 23 September 2007 (CEST)

== Beginners need more information ==

Uboot "?" or Linux "Yes" don't mean much to a beginner.
My guess is
# "?" means the test has not been performed?
# uboot "yes" means that you can boot directly from an image on the Micro SD device?
# Linux = "yes" means that once booted with the specified kernel that I can put a filesystem on the device and use it for general purpose storage?
Could someone clarify this by adding a legend to this page? Thanks -- [[User:Brian H Wilson|Brian H Wilson]] 18:04, 3 July 2008 (UTC)

== Reformatting the page ==

I suggest to reformat the page so the table is broken up.
Instead of the table, it would be more modular to have each card listed and described there, since what kernel/uboot the card will work. Additional notes could be supplied more easily than in the table.

I do support this vote. For example: The [http://wiki.openwrt.org/TableOfHardware table of supported hardware] from [http://www.openwrt.org OpenWrt] is very well structured. [[User:Deichkind|Deichkind]] 20:56, 7 Nov 2008 (CET)

== How to obtain the "Model number" ==

Say how to obtain the "Model number" from the card if one no longer has the box it came in. [[User:Jidanni|Jidanni]] 08:43, 28 October 2008 (UTC)

U-Boot

2008-11-06T22:27:40Z

Deichkind: /* Using usbtty from Linux */ Added note for USB-ID of GTA02

{{Languages|Bootloader}}

[[Image:GTA01-U-Boot.JPG|thumb|300px|u-boot menu on Neo1973]] [[Image:Neo1973 uboot splash closeup.jpg|thumb|300px|u-boot splash screen on Neo1973]]

The bootloader used on the smartphones is called '''U-Boot'''. It takes care of device functionality until Openmoko is booted. This includes [[USB DFU]] for [[Flashing the Neo FreeRunner]], a splash screen, a boot menu, a console for [[bootloader commands]], configuration via [[bootloader environment]], and loading a [[kernel]].

There are various [[bootloader versions]] available.

== Booting into U-boot ==

* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.
* Hold in the AUX button on power-up to access the boot menu.
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.
* Set the console to USB.
* Connect to /dev/ttyACM0 with a terminal program on the Linux host (you might need to chown uucp.uucp /dev/ttyACM0 )
* Note that the cdc_acm /dev/ttyACM0 access disappears as soon as the Neo boots, and is replaced by the cdc_ether usb0 network access.
* You're now at the bootloader prompt.
* Set the bootdelay uboot environment variable to -1 if you want it to always halt at the bootloader on power-up.

== General ==

All versions of the OM smartphone use the [http://u-boot.sourceforge.net/ u-boot] bootloader.

More information on u-boot can be found at
* http://www.denx.de/wiki/DULG
* http://www.gumstix.org/tikiwiki/tiki-index.php?page=U-Boot
* http://linuxdevices.com/articles/AT5085702347.html

Additions to the vanilla u-boot already implemented include:
* Support for boot from NAND flash using [[S3C2410 Steppingstone]]
* Support for S3C2410 NAND flash
* Support for downloading programs via S3C2410 USB Device Controller
* Support to display bootup logo / status on S3C2410 Framebuffer

However, u-boot still doesn't support many of the features that GTA01 needs, such as
* Support for reading kernel/initrd from SD/Transflash

[[User:HaraldWelte|HaraldWelte]] is working on those issues, and in fact most of them have already been implemented.

== Bootloader source code ==

The current bootloader source can be found at http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=stable .

To get u-boot by git:

git clone git://git.openmoko.org/git/u-boot.git openmoko/u-boot

To build u-boot:
* Clone the git tree and check out the stable branch
* Set the CROSS_COMPILE environment variable to specify the prefix to your toolchain binaries
* Run "make gta02v5_config" (or gta01bv4_config, or whatever hardware revision you have)
* Run "make u-boot.udfu". This will give you an image which you can install with dfu-util, or which you can upload into memory via JTAG (with a debug board)

== Bootloader binary ==

The latest bootloader binary builds can be found under http://downloads.openmoko.org/daily/ .

All versions of the GTA02 (Neo FreeRunner) that have been sold to the public are version 5 hardware, so look for a file with "gta02" and "v5" in the name, for example:
uboot-gta02v5-latest.bin

The file should be written to the NAND flash address 0x00000000 (size 0x30000) (the first [[Partitions|partition]]).

== Bootloader development ==

=== QT2410 ===
If you want to do bootloader development on the QT2410, it's easier to work with a bootloader image that can be downloaded via USB into RAM instead of flashing.

To do so, you need to edit the u-boot/include/configs/qt2410.h file, and change the "if 0" in Line 32 into a "if 1", then recompile with "make".

The resulting "u-boot.bin" is _NOT SUITABLE_ for NAND flash, but only for direct execution from within ram, e.g. by using the [[s3c2410_boot_usb]] program.

=== Neo 1973 ===

Doing bootloader development on the [[Neo 1973]] is a bit more tricky. First, we don't have any NOR flash. Second, there is no other way to boot _but_ from NAND. Therefore, we also don't have a USB downloader like the QT2410.

The main problem is: The [[S3C2410 Steppingstone]] unconditionally copies the first 4k of flash into its internal SRAM. That SRAM segment stays unconditionally mapped at physical address zero. How do we get around this

=== Neo FreeRunner ===
{{main|Neo_FreeRunner_Memory_Mapping}}

==== Using JTAG to boot from RAM ====

So how can we boot from RAM? We use JTAG / OpenOCD to:

* Reset and halt the cpu at PC=0
<pre>
> reset halt
target halted in ARM state due to debug request, current mode: Supervisor
cpsr: 0x400000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
</pre>

* Download a small piece of code for low-level SDRAM timing initialization (overwrite 4k SRAM of steppingstone)
<pre>
> load_binary /space/misc/gta01/u-boot.git/board/gta01/lowlevel_foo.bin 0
downloaded 332 byte in 0s 21899us
</pre>

* Assert a break point at address 0x33f80000 (which indicates that the low-level code has finished)
<pre>
> bp 0x33f80000 4 hw
breakpoint added at address 0x33f80000
</pre>

* Run the code up to the break point
<pre>
> resume
Target 0 resumed
> Target 0 halted
target halted in ARM state due to breakpoint, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x33f80000
MMU: disabled, D-Cache: disabled, I-Cache: enabled
</pre>

* Download the u-boot RAM image to 0x33f80000
<pre>
> load_binary /space/misc/gta01/u-boot.git/u-boot.bin 0x33f80000
downloaded 135692 byte in 6s 567264us
</pre>

* Resume processing
<pre>
> resume
Target 0 resumed
</pre>

At this point, the display backlight gets bright and we see the following familiar prompt on the serial console:
<pre>
U-Boot 1.1.6 (Jan 13 2007 - 23:44:23)

DRAM: 128 MB
NAND: 64 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv2 #
</pre>

== Creating bootable images ==

U-boot needs bootable images (such as kernels, but also initrd and others) in form of a so-called ''uImage''. In order to create a ''uImage'' from e.g. a ''vmlinux'' kernel image, you can proceed as follows:

<pre>
objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
gzip -9 linux.bin
u-boot/tools/mkimage -A arm -O linux -T kernel -C gzip -a 30008000 -e 30008000 -n "Kernel Image QT2410" -d linux.bin.gz uImage
</pre>

== Boot menu ==
[[Image:Neo1973 uboot menu.jpg|thumb|400px|u-boot boot menu on Neo1973]]

As of the Phase-0 release, our u-boot version now features an on-screen boot menu. The items are defined by [[bootloader environment#menu|menu entries in the environment]].

=== Accessing the boot menu ===

You can access the boot menu by pressing and holding the [[Neo1973 AUX Button]] together with the power button while switching the phone on.

=== Using the boot menu ===

By pressing the [[Neo1973 AUX Button]] you can cycle through the menu items. Use the ''POWER'' button to select one item.

== Bootloader prompt ==

=== Accessing the bootloader prompt ===
The bootloader prompt is available either on the serial console (via [[Debug Board]]), or as virtual USB Serial device (USB CDC_ACM).
Whether the serial port or usb is used depends on the u-boot environment variables '''stdin''', '''stdout''' and '''stderr'''.

Whether or not you use usbtty, the first couple of messages will always be displayed on the serial console.

The bootloader is currently configured to wait for three seconds. If a key press on the '''stdin''' is received within those three seconds, auto-boot is aborted.

==== Using usbtty from Linux ====

Just by connecting the phone in u-boot mode to your Linux pc should make it detect a [[CDC ACM]] device, and you should get a new tty device called /dev/ttyACM0. If not, enable the CONFIG_USB_ACM (Device Drivers -> USB support -> USB Modem (CDC ACM) support). (Instructions for MacOS users are [[MacOS_X#USB_Serial|here]])

Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port.
You can adapt the instructions for USB-serial from the [[MacOS_X#USB_Serial|Mac OS]] page.
If you don't have a favorite, try just: (cu is in the taylor-uucp package, use "apt-get install cu" if it is not yet installed)
cu -l /dev/ttyACM0

You might need to
chown uucp.uucp /dev/ttyACM0

to get the necessary rights (even as root).

A nice alternative for cu is Werner Almesberger's [[NeoCon|neocon]].

First, you should try to check whether the USB device shows up in 'lsusb' while you're running in u-boot mode:

<pre>
# lsusb -d 1457:5119
Bus 005 Device 079: ID 1457:5119
</pre>
'''Note''': The Neo Freerunner (GTA02) has the ID 1d50:5119

Second, let's see some more details about the available endpoints and configurations:

<pre>
# lsusb -v -d 1457:5119
Bus 005 Device 079: ID 1457:5119
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x1457
idProduct 0x5119
bcdDevice 0.00
iManufacturer 1 Openmoko, Inc
iProduct 2 Neo1973 Bootloader U-Boot 1.2.0-g6c7cac8c-dirty-moko3
iSerial 3 0000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 TTY via USB
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 6 Control Interface
CDC Header:
bcdCDC 0.6e
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x00
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 5 Bulk Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 7 USB Device Firmware Upgrade
Device Status: 0x0001
Self Powered
</pre>

Next, you can access it using your favourite terminal program.

Then, if the environment is not set correctly, you will need to use the current console (e.g. serial console) to change the [[bootloader environment#console|console entries in the environment]]:
<pre>
GTA01Bv2 # setenv stderr usbtty
GTA01Bv2 # setenv stdout usbtty
GTA01Bv2 # setenv stdin usbtty
</pre>

==== Typical u-boot prompt ====

<pre>
U-Boot 1.2.0-moko1 (Feb 16 2007 - 00:36:13)

DRAM: 128 MB
NAND: 64 MiB
Found Environment offset in OOB..
Video: 640x480x8 31kHz 59Hz
USB: S3C2410 USB Deviced
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv3 #
</pre>

=== Commands on the bootloader prompt ===

:''See [[bootloader commands]].''

=== What if I borked my bootloader environment and don't get a prompt anymore? ===
{{Note|This solution applies to a changed u-boot environment which prevents NAND u-boot to successfully boot. The Debian u-boot configuration script may be a cause of this issue.}}
Found a solution here:
[[http://markmail.org/message/gqypwiohdet6x4am?q=almesberger+partition&page=1&refer=xbamkzwwsaobv7wa]]

It works the following way:
* Get the devirginator:
svn co http://svn.openmoko.org/trunk/src/host/devirginator
cd devirginator
* Read the u-boot environment from the device:
dfu-util -a u-boot_env -R -U env.in
* Create a file that contains everything you want to change in your u-boot environment or get it by issuing the following command:
wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in
* Now let devirginator generate a new u-boot_env partition for us, - that contains the partition table from our u-boot_env, - and all changes we wanted to make; Note that the -D GTA02 is needed for the neo FreeRunner only, and has to come before the other options.
./envedit.pl -D GTA02 -i env.in -f environment.in -o env.out
* On my box the partition layout didn't seem to match the idea of envedit.pl, so it issued 2 warnings:
warning: environment is 262144 bytes, expected 16384
CRC error: expected 0xc33e35fc, got 0x93097bfb
* In this case jut add an additional argument to the command line - that has to be the 1st argument, though, and that contains the size information we got from the warning:
./envedit.pl -s 262144 -D GTA02 -i env.in -f environment.in -o env.out
* Now the perl script should produce no more output anything but write a new u-boot_env partition that we can upload to the device by:
dfu-util -a u-boot_env -R -D env.out

== Device Firmware Upgrade ==

Our version of u-boot also implements [[USB DFU]]. This can be useful to
load files and kernel for quick testing.

To find out whether your version of u-boot supports this, use the output of
$ lsusb -v -d 1457:5119
while the phone is in u-boot mode.

If it supports DFU, you should see the following snippet towards the end of the output:
<pre>
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
</pre>

For information on how to do firmware upgrades, please see [[dfu-util]]. For neo 1973 you may see [[Flashing the Neo 1973#Actually_flashing_things_into_the_device]], and for the FreeRunner : [[Flashing the Neo FreeRunner]].

=== Booting files over DFU ===

To load a file at memory address 0x32000000:
<pre>
dfu-util -a 0 -D fileToLoad -R
</pre>

After that, send 'bootm 0x32000000' to u-boot or 'bootelf 0x32000000' if
its an elf file.

Simple python script that can boot an ELF image - avoiding a ACM bug that breaks on large packets.

<pre>
#!/usr/bin/python
import sys
import os
import time

cmd1 = "neo backlight off\n"
cmd2 = "bootelf 0x32000000\n"

def output(tty, str):
for x in str:
tty.write(x)
tty.flush()

if len(sys.argv) == 2:
print "Loading %s..." % sys.argv[1]

loadfile = "dfu-util -a 0 -D %s -R" % sys.argv[1]

os.system(loadfile)

time.sleep(3)

tty = open("/dev/ttyACM0", "a")

output(tty, cmd1)
output(tty, cmd2)

tty.close()
else:
print "Usage: %s elffile" % sys.argv[0]
print ""
sys.exit(2)
</pre>

== Troubleshooting ==

=== USB connectivity problems ===

I once got errors like this (in dmesg or /var/log/messages) on the host side while connecting the neo in u-boot:

usb 2-1: device descriptor read/64, error -110
usb usb2: Controller not stopped yet!

or

hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 4-1: USB disconnect, address 2

A possible solution is given below. Please note that if you have a usb keyboard or mouse then the command might cause trouble.

rmmod uhci_hcd ; modprobe uhci_hcd

Another option is to plug the FR into a different USB port on the host, preferably one on the Motherboard not the hub.

Disconnecting the Neo's USB while powering up may prevent this problem in the future.

== Related pages ==

See [[Flashing the Neo 1973]] and [[Flashing the Neo FreeRunner]] for instructions on using dfu-util to install a new bootloader in your phone.

[[Category:System Developers]]
[[Category:Flashing Openmoko]]

U-Boot

2008-11-06T22:23:25Z

Deichkind: /* Using usbtty from Linux */

{{Languages|Bootloader}}

[[Image:GTA01-U-Boot.JPG|thumb|300px|u-boot menu on Neo1973]] [[Image:Neo1973 uboot splash closeup.jpg|thumb|300px|u-boot splash screen on Neo1973]]

The bootloader used on the smartphones is called '''U-Boot'''. It takes care of device functionality until Openmoko is booted. This includes [[USB DFU]] for [[Flashing the Neo FreeRunner]], a splash screen, a boot menu, a console for [[bootloader commands]], configuration via [[bootloader environment]], and loading a [[kernel]].

There are various [[bootloader versions]] available.

== Booting into U-boot ==

* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.
* Hold in the AUX button on power-up to access the boot menu.
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.
* Set the console to USB.
* Connect to /dev/ttyACM0 with a terminal program on the Linux host (you might need to chown uucp.uucp /dev/ttyACM0 )
* Note that the cdc_acm /dev/ttyACM0 access disappears as soon as the Neo boots, and is replaced by the cdc_ether usb0 network access.
* You're now at the bootloader prompt.
* Set the bootdelay uboot environment variable to -1 if you want it to always halt at the bootloader on power-up.

== General ==

All versions of the OM smartphone use the [http://u-boot.sourceforge.net/ u-boot] bootloader.

More information on u-boot can be found at
* http://www.denx.de/wiki/DULG
* http://www.gumstix.org/tikiwiki/tiki-index.php?page=U-Boot
* http://linuxdevices.com/articles/AT5085702347.html

Additions to the vanilla u-boot already implemented include:
* Support for boot from NAND flash using [[S3C2410 Steppingstone]]
* Support for S3C2410 NAND flash
* Support for downloading programs via S3C2410 USB Device Controller
* Support to display bootup logo / status on S3C2410 Framebuffer

However, u-boot still doesn't support many of the features that GTA01 needs, such as
* Support for reading kernel/initrd from SD/Transflash

[[User:HaraldWelte|HaraldWelte]] is working on those issues, and in fact most of them have already been implemented.

== Bootloader source code ==

The current bootloader source can be found at http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=stable .

To get u-boot by git:

git clone git://git.openmoko.org/git/u-boot.git openmoko/u-boot

To build u-boot:
* Clone the git tree and check out the stable branch
* Set the CROSS_COMPILE environment variable to specify the prefix to your toolchain binaries
* Run "make gta02v5_config" (or gta01bv4_config, or whatever hardware revision you have)
* Run "make u-boot.udfu". This will give you an image which you can install with dfu-util, or which you can upload into memory via JTAG (with a debug board)

== Bootloader binary ==

The latest bootloader binary builds can be found under http://downloads.openmoko.org/daily/ .

All versions of the GTA02 (Neo FreeRunner) that have been sold to the public are version 5 hardware, so look for a file with "gta02" and "v5" in the name, for example:
uboot-gta02v5-latest.bin

The file should be written to the NAND flash address 0x00000000 (size 0x30000) (the first [[Partitions|partition]]).

== Bootloader development ==

=== QT2410 ===
If you want to do bootloader development on the QT2410, it's easier to work with a bootloader image that can be downloaded via USB into RAM instead of flashing.

To do so, you need to edit the u-boot/include/configs/qt2410.h file, and change the "if 0" in Line 32 into a "if 1", then recompile with "make".

The resulting "u-boot.bin" is _NOT SUITABLE_ for NAND flash, but only for direct execution from within ram, e.g. by using the [[s3c2410_boot_usb]] program.

=== Neo 1973 ===

Doing bootloader development on the [[Neo 1973]] is a bit more tricky. First, we don't have any NOR flash. Second, there is no other way to boot _but_ from NAND. Therefore, we also don't have a USB downloader like the QT2410.

The main problem is: The [[S3C2410 Steppingstone]] unconditionally copies the first 4k of flash into its internal SRAM. That SRAM segment stays unconditionally mapped at physical address zero. How do we get around this

=== Neo FreeRunner ===
{{main|Neo_FreeRunner_Memory_Mapping}}

==== Using JTAG to boot from RAM ====

So how can we boot from RAM? We use JTAG / OpenOCD to:

* Reset and halt the cpu at PC=0
<pre>
> reset halt
target halted in ARM state due to debug request, current mode: Supervisor
cpsr: 0x400000d3 pc: 0x00000000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
</pre>

* Download a small piece of code for low-level SDRAM timing initialization (overwrite 4k SRAM of steppingstone)
<pre>
> load_binary /space/misc/gta01/u-boot.git/board/gta01/lowlevel_foo.bin 0
downloaded 332 byte in 0s 21899us
</pre>

* Assert a break point at address 0x33f80000 (which indicates that the low-level code has finished)
<pre>
> bp 0x33f80000 4 hw
breakpoint added at address 0x33f80000
</pre>

* Run the code up to the break point
<pre>
> resume
Target 0 resumed
> Target 0 halted
target halted in ARM state due to breakpoint, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x33f80000
MMU: disabled, D-Cache: disabled, I-Cache: enabled
</pre>

* Download the u-boot RAM image to 0x33f80000
<pre>
> load_binary /space/misc/gta01/u-boot.git/u-boot.bin 0x33f80000
downloaded 135692 byte in 6s 567264us
</pre>

* Resume processing
<pre>
> resume
Target 0 resumed
</pre>

At this point, the display backlight gets bright and we see the following familiar prompt on the serial console:
<pre>
U-Boot 1.1.6 (Jan 13 2007 - 23:44:23)

DRAM: 128 MB
NAND: 64 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv2 #
</pre>

== Creating bootable images ==

U-boot needs bootable images (such as kernels, but also initrd and others) in form of a so-called ''uImage''. In order to create a ''uImage'' from e.g. a ''vmlinux'' kernel image, you can proceed as follows:

<pre>
objcopy -O binary -R .note -R .comment -S vmlinux linux.bin
gzip -9 linux.bin
u-boot/tools/mkimage -A arm -O linux -T kernel -C gzip -a 30008000 -e 30008000 -n "Kernel Image QT2410" -d linux.bin.gz uImage
</pre>

== Boot menu ==
[[Image:Neo1973 uboot menu.jpg|thumb|400px|u-boot boot menu on Neo1973]]

As of the Phase-0 release, our u-boot version now features an on-screen boot menu. The items are defined by [[bootloader environment#menu|menu entries in the environment]].

=== Accessing the boot menu ===

You can access the boot menu by pressing and holding the [[Neo1973 AUX Button]] together with the power button while switching the phone on.

=== Using the boot menu ===

By pressing the [[Neo1973 AUX Button]] you can cycle through the menu items. Use the ''POWER'' button to select one item.

== Bootloader prompt ==

=== Accessing the bootloader prompt ===
The bootloader prompt is available either on the serial console (via [[Debug Board]]), or as virtual USB Serial device (USB CDC_ACM).
Whether the serial port or usb is used depends on the u-boot environment variables '''stdin''', '''stdout''' and '''stderr'''.

Whether or not you use usbtty, the first couple of messages will always be displayed on the serial console.

The bootloader is currently configured to wait for three seconds. If a key press on the '''stdin''' is received within those three seconds, auto-boot is aborted.

==== Using usbtty from Linux ====

Just by connecting the phone in u-boot mode to your Linux pc should make it detect a [[CDC ACM]] device, and you should get a new tty device called /dev/ttyACM0. If not, enable the CONFIG_USB_ACM (Device Drivers -> USB support -> USB Modem (CDC ACM) support). (Instructions for MacOS users are [[MacOS_X#USB_Serial|here]])

Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port.
You can adapt the instructions for USB-serial from the [[MacOS_X#USB_Serial|Mac OS]] page.
If you don't have a favorite, try just: (cu is in the taylor-uucp package, use "apt-get install cu" if it is not yet installed)
cu -l /dev/ttyACM0

You might need to
chown uucp.uucp /dev/ttyACM0

to get the necessary rights (even as root).

A nice alternative for cu is Werner Almesberger's [[NeoCon|neocon]].

First, you should try to check whether the USB device shows up in 'lsusb' while you're running in u-boot mode:

# lsusb -d 1457:5119
Bus 005 Device 079: ID 1457:5119

Second, let's see some more details about the available endpoints and configurations:

<pre>
# lsusb -v -d 1457:5119
Bus 005 Device 079: ID 1457:5119
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x1457
idProduct 0x5119
bcdDevice 0.00
iManufacturer 1 Openmoko, Inc
iProduct 2 Neo1973 Bootloader U-Boot 1.2.0-g6c7cac8c-dirty-moko3
iSerial 3 0000000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 TTY via USB
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 6 Control Interface
CDC Header:
bcdCDC 0.6e
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x00
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 5 Bulk Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 7 USB Device Firmware Upgrade
Device Status: 0x0001
Self Powered
</pre>

Next, you can access it using your favourite terminal program.

Then, if the environment is not set correctly, you will need to use the current console (e.g. serial console) to change the [[bootloader environment#console|console entries in the environment]]:
<pre>
GTA01Bv2 # setenv stderr usbtty
GTA01Bv2 # setenv stdout usbtty
GTA01Bv2 # setenv stdin usbtty
</pre>

==== Typical u-boot prompt ====

<pre>
U-Boot 1.2.0-moko1 (Feb 16 2007 - 00:36:13)

DRAM: 128 MB
NAND: 64 MiB
Found Environment offset in OOB..
Video: 640x480x8 31kHz 59Hz
USB: S3C2410 USB Deviced
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
GTA01Bv3 #
</pre>

=== Commands on the bootloader prompt ===

:''See [[bootloader commands]].''

=== What if I borked my bootloader environment and don't get a prompt anymore? ===
{{Note|This solution applies to a changed u-boot environment which prevents NAND u-boot to successfully boot. The Debian u-boot configuration script may be a cause of this issue.}}
Found a solution here:
[[http://markmail.org/message/gqypwiohdet6x4am?q=almesberger+partition&page=1&refer=xbamkzwwsaobv7wa]]

It works the following way:
* Get the devirginator:
svn co http://svn.openmoko.org/trunk/src/host/devirginator
cd devirginator
* Read the u-boot environment from the device:
dfu-util -a u-boot_env -R -U env.in
* Create a file that contains everything you want to change in your u-boot environment or get it by issuing the following command:
wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in
* Now let devirginator generate a new u-boot_env partition for us, - that contains the partition table from our u-boot_env, - and all changes we wanted to make; Note that the -D GTA02 is needed for the neo FreeRunner only, and has to come before the other options.
./envedit.pl -D GTA02 -i env.in -f environment.in -o env.out
* On my box the partition layout didn't seem to match the idea of envedit.pl, so it issued 2 warnings:
warning: environment is 262144 bytes, expected 16384
CRC error: expected 0xc33e35fc, got 0x93097bfb
* In this case jut add an additional argument to the command line - that has to be the 1st argument, though, and that contains the size information we got from the warning:
./envedit.pl -s 262144 -D GTA02 -i env.in -f environment.in -o env.out
* Now the perl script should produce no more output anything but write a new u-boot_env partition that we can upload to the device by:
dfu-util -a u-boot_env -R -D env.out

== Device Firmware Upgrade ==

Our version of u-boot also implements [[USB DFU]]. This can be useful to
load files and kernel for quick testing.

To find out whether your version of u-boot supports this, use the output of
$ lsusb -v -d 1457:5119
while the phone is in u-boot mode.

If it supports DFU, you should see the following snippet towards the end of the output:
<pre>
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
</pre>

For information on how to do firmware upgrades, please see [[dfu-util]]. For neo 1973 you may see [[Flashing the Neo 1973#Actually_flashing_things_into_the_device]], and for the FreeRunner : [[Flashing the Neo FreeRunner]].

=== Booting files over DFU ===

To load a file at memory address 0x32000000:
<pre>
dfu-util -a 0 -D fileToLoad -R
</pre>

After that, send 'bootm 0x32000000' to u-boot or 'bootelf 0x32000000' if
its an elf file.

Simple python script that can boot an ELF image - avoiding a ACM bug that breaks on large packets.

<pre>
#!/usr/bin/python
import sys
import os
import time

cmd1 = "neo backlight off\n"
cmd2 = "bootelf 0x32000000\n"

def output(tty, str):
for x in str:
tty.write(x)
tty.flush()

if len(sys.argv) == 2:
print "Loading %s..." % sys.argv[1]

loadfile = "dfu-util -a 0 -D %s -R" % sys.argv[1]

os.system(loadfile)

time.sleep(3)

tty = open("/dev/ttyACM0", "a")

output(tty, cmd1)
output(tty, cmd2)

tty.close()
else:
print "Usage: %s elffile" % sys.argv[0]
print ""
sys.exit(2)
</pre>

== Troubleshooting ==

=== USB connectivity problems ===

I once got errors like this (in dmesg or /var/log/messages) on the host side while connecting the neo in u-boot:

usb 2-1: device descriptor read/64, error -110
usb usb2: Controller not stopped yet!

or

hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 4-1: USB disconnect, address 2

A possible solution is given below. Please note that if you have a usb keyboard or mouse then the command might cause trouble.

rmmod uhci_hcd ; modprobe uhci_hcd

Another option is to plug the FR into a different USB port on the host, preferably one on the Motherboard not the hub.

Disconnecting the Neo's USB while powering up may prevent this problem in the future.

== Related pages ==

See [[Flashing the Neo 1973]] and [[Flashing the Neo FreeRunner]] for instructions on using dfu-util to install a new bootloader in your phone.

[[Category:System Developers]]
[[Category:Flashing Openmoko]]

Openmoko Local Groups: Zurich

2008-11-04T22:47:53Z

Deichkind:

{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
!Has Device
!Has Debug Board
|-
|[[User:AudriusA|Audrius Meškauskas]]
|Developer
|Learns to program this device and port programs to it. Expert in java which is no in great use here, but things may change (plans to help porting).
|Dubendorf
|Has Neo1973 Phase 1 with debug board
|[[Image: Moko.jpg|center]]
|[[Image: MokoBox.jpg|center]]
|-
|[[User:Deichkind|Marian]]
|Linux (since 1996), Qt, C, C++. Java to pay the rent ;-)
|Mobile Linux (Debian Distribution), GPS
|Zürich
|Other info
|[[Image: Moko.jpg|center]]GTA02
|No
|-
|[[User:You|Your name here]]
|Anything
|Put your interests here
|Location
|Other info
|
|
|}

[[Category:Openmoko Local Groups]]

Openmoko Local Groups: Switzerland

2008-11-04T22:30:59Z

Deichkind:

__NOTOC__
== Upcoming Events ==
=== OpenExpo'09 Bern ===
1/2 april 2009

some ideas:

* community meeting (grill, party?)
* ...

== Past Activities ==
* [http://www.openexpo.ch/openexpo-2008-zuerich OpenExpo'08 Winterthur]
* [http://www.openexpo.ch/openexpo-2008-bern OpenExpo'08 Bern]
* [http://lug.zhaw.ch/wiki/Distro-Bash_2007 Distro-Bash Winterthur]
* Openmoko booth at the OpenExpo'07 Zurich

== Buying Openmoko Neo FreeRunner in Switzerland ==
=== Group Sales ===
[[GroupSales#Switzerland]]
=== Distributors ===
see http://openmoko.com/distributors-europe-switzerland.html

== Users in Switzerland ==
*[[User:C7|C7]]
*[[User:Obri|Obri]]
*[[User:yvanxxx|yvanxxx]]
*[[User:Megalomaniac|Megalomaniac]]
*[[User:toldap|toldap]]
*[[User:Gr33b|Gr33b]]
*[[User:AudriusA|AudriusA]]
*[[User:cgjusten|cgjusten]]
*[[User:DarkAngel|DarkAngel]]
*[[User:Agh|Agh]]
*[[User:Anakron|Anakron]]
*[[User:Nowic|Nowic]]
*[[User:Magbeat|Magbeat]]
*[[User:darktim|darktim]]
*[[User:nickik|nickik]]
*[[User:Skarhand|Skarhand]]
*[[User:mat|mat]]
*[[User:psal|psal]]
*[[User:Tuxfux.ch|Tuxfux.ch]]
*[[User:claude-elrond740|claude-elrond740]]
*[[User:DrYak|DrYak]]
*[[User:bernulli|bernulli]]
*[[User:jecuendet|jecuendet]]
*[[User:fbianco|fbianco]] (Geneva & Valais)
*[[User:dontinelli|dontinelli]]
*[[User:Deichkind|Deichkind]]

[[Category:Openmoko Local Groups]]

Talk:Supported microSD cards

2008-11-02T22:06:36Z

Deichkind:

Let it be known that 4Gb microSDHC cards have been announced by more than one company. Apparently these will not be supported by default in microSD devices. Does anyone know if the Neo will support these in theory? [[User:Wasp|Wasp]] 00:06, 16 February 2007 (CET)

: Also 8GB MicroSD cards have now been announced. Would be really nice to know if it's just a driver issue or something more.

: Anyone tried 16GB microSDHC cards (Sandisk)? - the are now available here in Germany --[[User:Nodge|Nodge]] 08:52, 30 October 2008 (UTC)
: * Yes, I have a SDSDQ-016G-E11M (16GB, Class2) in a Neo-FR in use with Debian (ext2) on it (Qtopia on flash). It can only be boot with manually from NAND. Suspending still causes I/O error on the SD. The rest seems stable. Right now, I don't know how to supply this info in the table. -- Greetings from Switzerland, [[User:Deichkind|Deichkind]] 23:03, 2 November 2008 (CET)

== How to test ==

Can we please define repeatable tests?
atm I just copy stuff there and back - there is probably more to it.
Tested the Sandisk 512 and 1024 cards [[User:Johan|Johan]] 22:27, 4 August 2007 (CEST)

== Use newer kernel/uboot for testing ==

As the 2.6.17 kernel is pretty outdated and openmoko uses 2.6.22 for a long time now, we maybe should use this kernel version for testing, shouldn't we? --[[User:Thomasg|Thomasg]] 16:23, 23 September 2007 (CEST)

i strongly second that.
please do not test with ancient and totally outdated software. this will only generate bogus bugreports which hold everybody from seeing the real problems.
with recent i mean 2.6.22.5-moko11 or newer. please also add the exact release (including svnr if possible) when filing a bug.

same goes for uboot.
currently we are at svnr 2943 or higher. please do not file bugs against uboots which are totally outdated.
if you want to update your uboot for tests, please contact me and i'll try to supply you with a tested uboot for your device. --[[User:Roh|Roh]] 22:03, 23 September 2007 (CEST)

== Beginners need more information ==

Uboot "?" or Linux "Yes" don't mean much to a beginner.
My guess is
# "?" means the test has not been performed?
# uboot "yes" means that you can boot directly from an image on the Micro SD device?
# Linux = "yes" means that once booted with the specified kernel that I can put a filesystem on the device and use it for general purpose storage?
Could someone clarify this by adding a legend to this page? Thanks -- [[User:Brian H Wilson|Brian H Wilson]] 18:04, 3 July 2008 (UTC)

== Reformatting the page ==

I suggest to reformat the page so the table is broken up.
Instead of the table, it would be more modular to have each card listed and described there, since what kernel/uboot the card will work. Additional notes could be supplied more easily than in the table.

== How to obtain the "Model number" ==

Say how to obtain the "Model number" from the card if one no longer has the box it came in. [[User:Jidanni|Jidanni]] 08:43, 28 October 2008 (UTC)