Openmoko - User contributions [en]

User:Kevin

2010-05-27T07:56:50Z

Kevin: New page: Kontact me: http://wiki.openmoko.org/wiki/Special:Emailuser/Kevin

Kontact me: http://wiki.openmoko.org/wiki/Special:Emailuser/Kevin

Talk:Flashing the GSM Firmware

2008-11-20T15:18:31Z

Kevin: /* Works now with new gsm firmware moko10beta2 with O2 in Germany */ new section

i recive instead of

"Program: (34 sectors, 267*8k=2136k) (*******************) ok"

this

"Program: (0 sectors, 0*8k=0k) () ok"

iam currently reflashing the old firmware, that seems to work.

iam using an non-us gsm-freerunner (recived yesterday so most likely the latest hardwar)

thakoman

[2008-11-19 04:46:39] <Wonka> DocScrutinizer: flashing to moko10-beta2 went though cleanly, i already had working ppp connects with the previously non-working SIM.

[2008-11-19 04:48:24] <Wonka> DocScrutinizer: but there are still problems... more often than not, the GSM chip does not answer. pppd opens the device, gets "AT command interpreter ready", utters "AT\n" and gets nothing. power off, power on, reset on, reset off, try gain... sometimes it works, but mostly not.

O2 UK prepay 3G SIM works with moko10-beta2, was previously not
detected. T-mobile UK prepay SIM and old Orange UK contract SIM work
with both old and new. Testing so far is cursory at best, but looks good.
[quote: Alastair Johnson on devel-ML]

== Works now with new gsm firmware moko10beta2 with O2 in Germany ==

Very great, I can make calls now after waiting for 5 month, big surprise :).
Thanks a lot!
--[[User:Kevin|Kevin]] 15:18, 20 November 2008 (UTC)

FreeRunner unable to work with 3G SIM cards

2008-11-20T15:13:56Z

Kevin: Works now with new gsm firmware moko10beta2 with O2 in Germany

== FreeRunner SIM compatibility ==

See also: [[FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|FreeRunner Hardware Issues]]

[[GSM/Flashing]]

=== Carrier ===

There is carrier page documented carriers compatibility [[Carriers]]

=== TRAC Ticket 666 ===
TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and to GTA02 (Neo FreeRunner).

== Compatibility table (FreeRunner/GTA02)==

Please fill out following table .

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
!Carrier Name!! Error Message !! SIM Card Type!! Country !!Link to picture of SIM card!!Your name!!Did new SIM card solve problem?||Notes
|-
| TDC || Not working || 64K43 || Denmark || no pics || KB || Yes. They sent me a 64K23 card for free and that worked. || The chip on the new card is bigger. It has 4 contact points on each of the 2 columns, instead of 3 on each.
|-
| CHT || Unable to use GSM ||Dont' know|| R.O.C Taiwan || no pics ||王孟蒂 Brenda Wang|| ||When I put it on my Neo, it can't dial out
|-
| AT&T || WORKS || 71234 G || US || [http://wiki.openmoko.org/wiki/Image:Dave_att_working_sim.jpg image] || Dave || || Calls worked, though it was not used much for calling. SMS worked great. Tested with 2007.2, Qtopia, Qtopia-extended.
|-
| AT&T || Unable to use GSM || 71234 G || US || no pics || || || 71234 G SIM not working, 71234 O somebody in discuss thread say it could work
|-
| AT&T || Failed to register || 71234 D|| US || see below || [[Special:Emailuser/Safire|Safire]] || Switched to T-Mobile || Got strong Signal Bars with 2007.2 image despite "Registering...". Actually managed to dial and remote phone showed number, but never completed a full call. Dialer kept crashing. Pre-paid brand new sim, purchased July 2008
|-
| Vodafone || cme 13, 32 || some 3G capable|| DE || no pics || [[Special:Emailuser/Fsp|Fsp]] || no || most up-to-date Plan debitel
|-
| T-Mobile || No Error || 2G SIM || US || no pics || Community List || || Pre-paid SIM
|-
| e-plus || not working || 3G SIM || DE || no pics || Community List || || Plan SIM
|-
| e-plus (SIMYO) || 2G seems working/3G not || 2G/3G SIM || DE || no pics || Community List || || Pre-Paid SIM https://www.simyo.de/de/informieren/umts.html SIMYO has 2 voltage 1.8/3.3v 72K 1.8V #569 J276/2K 3V #568 H276
|-
| e-plus || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| O2 || Not certain/Not working || 3G SIM || DE || no pics || Community List || || Plan SIM, CME: 32, (1001710251761MC working)
|-
| O2 || not working || 3G sim || DE || [http://kev.knet.eu/bugs/openmoko/sim-card/not_working_O2.png link] || [[Special:Emailuser/Kevin|Kevin]] || Did not solve. Both simcards (7 month old one and new one) are looking identical. || I would like to help on testing/whatever, feel free to contact me. WORKS NOW with new [http://wiki.openmoko.org/wiki/GSM/Flashing gsm firmware moko10beta2] :)!
|-
| vodafone(D2 Mannesmann) || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| Blau SIM || some working || 2G/3G SIM || DE || no pics || Community List || || 16K 3V #343 H73 (not work)
|-
| Orange || working || 2G model J2R || FR || no pics || [[Special:Emailuser/pierrebrua|pierrebrua]] || || None
|-
| Orange || working || 2G/3G some wokring || DE || no pics || Community List || || None
|-
| Bouygues || working || 08 series || FR || no pics || [[Special:Emailuser/pierrebrua|pierrebrua]] || || Bad sound
|-
| T-Mobile || Not certain/Not working || unknown || DE || no pics || Community List || || None
|-
| o2 || cme error: 100 
cme error: 313
|| 2G possibly 3g? || UK || no pics.. YET. || [[Special:Emailuser/tdobson|tdobson]] || other SIMs work - MTS(RU) Orange(UK) Vodafone(UK) || Prepaid. Feel free to contact me.
|-
| Orange || working || 3G "USIM" || FR || (see below) || KewlCat || Om2008.8-update (20080827) solved it || Pre-paid SIM
|-
| Proximus Belgacom Mobile || not working || 2G model 3V || BE || no pics || [[Special:Emailuser/pierrebrua|pierrebrua]] || || None
|-
| SFR || partially working || 2G model AF and BC || FR || no pics || [[Special:Emailuser/pierrebrua|pierrebrua]] || || 50% incoming calls are missed due to lost carrier
|-
| SFR || not working || 3G model BK || FR || no pics || [[Special:Emailuser/pierrebrua|pierrebrua]] || || not detected by the phone
|-
| SFR || not working || 3G model BC and BK || FR || no pics || [[Special:Emailuser/Drizzt|Drizzt]] || || not detected by the phone
|-
| SFR || not working || 3G model BE and BK || FR || no pics || [[Special:Emailuser/Yoann|Yoann]] || BC model seems working || not detected by the phone
|-
| IT VODAFONE || not working || 64K || IT || no pics || Six-Blade Knife || Yes || not detected by the phone, changed with 128K and worked
|-
|}

== User Provided tested SIM pictures ==

[[Image:ATT_3G_71234D_SIM.JPG|left|thumb|200px|AT&T 3G 71234 D]]

Base on community post:

The 71324 is the SKU for the AT&T latest UICC.
The 2022 is the Vendor and Version number.

Some cards the vendor numbers are
2 - G&D
3 - Gemalto
4 - Oberthur

Usually user will get CME ERROR 13 (sim failure), rather than CME ERROR 10 (sim not inserted) when 3G SIM not working.

CME ERROR: 32 is Network not allowed, emergency calls only, might because the card not activated.

== The Error ==
<pre>
Here is the AT command:

root@om-gta02:~# libgsmd-tool -m atcmd
libgsm-tool - (C) 2006-2007 by Harald Welte and Openmoko, Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT
STR=`AT'
RSTR=`OK'
AT+CFUN=1
STR=`AT+CFUN=1'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CPIN="MyPIN"
STR=`AT+CPIN="MyPIN"'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CREG=1
STR=`AT+CREG=1'
RSTR=`OK'
AT+COPS=0
STR=`AT+COPS=0'
EVENT: Netreg searching for network
EVENT: Netreg registration denied
cme error: 32
RSTR=`+CME ERROR: 32'
EVENT: Signal Quality: 31
EVENT: Signal Quality: 31
</pre>

== Working and not working AT&T card ==

* Some AT&T cards have same vendor/ID number, but different contacts (Josh posted at 2008/8/24), following image shows that card that working (right) and not working (left) one.

[[Image:ATT_simcards_small.jpg]]

== Working SIM pics ==

[[Image:Adam_20080713_working_back.JPG]]

[[Image:KewlCat_20080829_Working_front.png]][[Image:Usim2.png]]
[[Image:Working-orange-usim.jpg]]

[[Image:Dave_att_working_sim_small.jpg]]

== Not Working SIM pics ==
* AT&T

[[Image:Adam_20080713_back_notworking.JPG]]

* Orange France

[[Image:Jean_20080715_orange_back_notworking.JPG.gif]]

* O2 Germany

[[Image:O2-sim-nonworking-tesa.jpg]]

[[Category:Neo FreeRunner Hardware]]

[[Category:Neo FreeRunner Hardware]]

FreeRunner unable to work with 3G SIM cards

2008-09-11T10:25:05Z

Kevin: /* TRAC Ticket 666 */ removed comments because nobody complains, still readable in discussions.

== FreeRunner SIM compatibility ==

See also: [[FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|FreeRunner Hardware Issues]]

=== Carrier ===

There is carrier page documented carriers compatibility [[Carriers]]

=== TRAC Ticket 666 ===
TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and to GTA02 (Neo FreeRunner).

== Compatibility table (FreeRunner/GTA02)==

Please fill out following table .

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
!Carrier Name!! Error Message !! SIM Card Type!! Country !!Link to picture of SIM card!!Your name!!Did new SIM card solve problem?||Notes
|-
| TDC || Not working || 64K43 || Denmark || no pics || KB || Yes. They sent me a 64K23 card for free and that worked. || The chip on the new card is bigger. It has 4 contact points on each of the 2 columns, instead of 3 on each.
|-
| CHT || Unable to use GSM ||Dont' know|| R.O.C Taiwan || no pics ||王孟蒂 Brenda Wang|| ||When I put it on my Neo, it can't dial out
|-
| AT&T || Unable to use GSM || 71234 G || US || no pics || || || 71234 G SIM not working, 71234 O somebody in discuss thread say it could work
|-
| AT&T || Failed to register || 71234 D|| US || see below || [[Special:Emailuser/Safire|Safire]] || Switched to T-Mobile || Got strong Signal Bars with 2007.2 image despite "Registering...". Actually managed to dial and remote phone showed number, but never completed a full call. Dialer kept crashing. Pre-paid brand new sim, purchased July 2008
|-
| Vodafone || cme 13, 32 || some 3G capable|| DE || no pics || [[Special:Emailuser/Fsp|Fsp]] || no || most up-to-date Plan debitel
|-
| T-Mobile || No Error || 2G SIM || US || no pics || Community List || || Pre-paid SIM
|-
| e-plus || not working || 3G SIM || DE || no pics || Community List || || Plan SIM
|-
| e-plus (SIMYO) || 2G seems working/3G not || 2G/3G SIM || DE || no pics || Community List || || Pre-Paid SIM https://www.simyo.de/de/informieren/umts.html SIMYO has 2 voltage 1.8/3.3v 72K 1.8V #569 J276/2K 3V #568 H276
|-
| e-plus || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| O2 || Not certain/Not working || 3G SIM || DE || no pics || Community List || || Plan SIM, CME: 32, (1001710251761MC working)
|-
| O2 || not working || 3G sim || DE || [http://kev.knet.eu/bugs/openmoko/sim-card/not_working_O2.png link] || [[Special:Emailuser/Kevin|Kevin]] || Did not solve. Both simcards (7 month old one and new one) are looking identical. || I would like to help on testing/whatever, feel free to contact me.
|-
| vodafone(D2 Mannesmann) || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| Blau SIM || some working || 2G/3G SIM || DE || no pics || Community List || || 16K 3V #343 H73 (not work)
|-
| Orange || working || 2G/3G some wokring || DE || no pics || Community List || || None
|-
| T-Mobile || Not certain/Not working || unknown || DE || no pics || Community List || || None
|-
| o2 || cme error: 100 
cme error: 313
|| 2G possibly 3g? || UK || no pics.. YET. || [[Special:Emailuser/tdobson|tdobson]] || other SIMs work - MTS(RU) Orange(UK) Vodafone(UK) || Prepaid. Feel free to contact me.
|-
| Orange || working || 3G "USIM" || FR || (see below) || KewlCat || Om2008.8-update (20080827) solved it || Pre-paid SIM
|-
|}

== User Provided tested SIM pictures ==

[[Image:ATT_3G_71234D_SIM.JPG|left|thumb|200px|AT&T 3G 71234 D]]

Base on community post:

The 71324 is the SKU for the AT&T latest UICC.
The 2022 is the Vendor and Version number.

Some cards the vendor numbers are
2 - G&D
3 - Gemalto
4 - Oberthur

Usually user will get CME ERROR 13 (sim failure), rather than CME ERROR 10 (sim not inserted) when 3G SIM not working.

CME ERROR: 32 is Network not allowed, emergency calls only, might because the card not activated.

== The Error ==
<pre>
Here is the AT command:

root@om-gta02:~# libgsmd-tool -m atcmd
libgsm-tool - (C) 2006-2007 by Harald Welte and Openmoko, Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT
STR=`AT'
RSTR=`OK'
AT+CFUN=1
STR=`AT+CFUN=1'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CPIN="MyPIN"
STR=`AT+CPIN="MyPIN"'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CREG=1
STR=`AT+CREG=1'
RSTR=`OK'
AT+COPS=0
STR=`AT+COPS=0'
EVENT: Netreg searching for network
EVENT: Netreg registration denied
cme error: 32
RSTR=`+CME ERROR: 32'
EVENT: Signal Quality: 31
EVENT: Signal Quality: 31
</pre>

== Working and not working AT&T card ==

* Some AT&T cards have same vendor/ID number, but different contacts (Josh posted at 2008/8/24), following image shows that card that working (right) and not working (left) one.

[[Image:ATT_simcards_small.jpg]]

== Working SIM pics ==

[[Image:Adam_20080713_working_back.JPG]]

[[Image:KewlCat_20080829_Working_front.png]][[Image:Usim2.png]]
[[Image:Working-orange-usim.jpg]]

== Not Working SIM pics ==
* AT&T

[[Image:Adam_20080713_back_notworking.JPG]]

* Orange France

[[Image:Jean_20080715_orange_back_notworking.JPG.gif]]

* O2 Germany

[[Image:O2-sim-nonworking-tesa.jpg]]

[[Category:Neo FreeRunner Hardware]]

Booting the Neo FreeRunner from SD via U-Boot

2008-08-20T11:47:50Z

Kevin: /* Add uboot boot entry */ example for rootfs and kernel on same partition

This page explains how to boot a Freerunner from the (micro-)SD card rather than from the built-in NAND flash memory. The SD card shares a bus with the GPU, so it may not perform as well, but it is another option.

{{Warning | Booting from SDHC may cause problems at this time. }}
See [http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/19154/focus=19281| this thread.]

== How it Works ==

On the Neo, [[u-boot]] performs a similar role to the 'grub' bootloader on a PC. U-boot loads a kernel image into memory and then passes a list of parameters to the kernel. These parameters specify, among other things, the device on which the root filesystem is located.

As the kernel boots, it initializes the hardware and then mounts the root filesystem. The kernel then runs "/sbin/init", which handles the rest of the boot-up sequence (such as displaying the splash screen and progress bar).

This sequence is the same whether the device is booting from built-in Flash or from the SD card. The differences are how the kernel is loaded, and which device is mounted as the root filesystem.

The following sections provide additional details.

=== Menu Entries ===

U-boot menu entries are defined by environment variables named "menu_X" (where X is a number). The value of the environment variable is a string "<label>:<commands>", where <label> is the text shown on the screen, and <commands> is a sequence of u-boot commands (delimited by ';' characters) to be executed when the menu item is selected. When entering a string of commands, the ';' and '$' characters must be backslash-escaped ("\;" and "\$").

=== Loading the Kernel ===

A pair of u-boot commands must be used to load the kernel from SD. First is "mmcinit", which will cause u-boot to detect the card. Next is a command to load a file into memory - either "fatload" or "ext2load" depending on whether the kernel is on a FAT filesytem or an ext2/ext3 filesystem.

The command syntax is:

fatload mmc 1: 0x32000000 <filepath>
ext2load mmc 1: 0x32000000 <filepath>

where is the partition number, and <filepath> is the path to the file that is to be loaded.

{{Note| The "ext2load" command is broken on u-boot binary earlier than "20080723", including the one shipped with the first batch of Freerunners, are affected by bug [http://docs.openmoko.org/trac/ticket/799 #799]. If you update your U-Boot and kernel packages you can use direct ext2 / 3 boot all in one partition.}}

{{Warning | Be careful when updating u-boot on a Neo1973 as there is a risk of bricking the device (unless you have a debug board). This is not an issue for the Freerunner as it has a protected copy of u-boot in the NOR flash }}

{{Note| U-Boot supports SDHC protocol on the Freerunner only: on the Neo1973, u-boot is unable to access SDHC cards (4G or larger). The kernel does have SDHC support on Neo1973, so it is possible to have the root filesystem on SDHC and the kernel on NAND flash to work around it. }}

=== Root Filesystem Parameters ===

The contents of the "bootargs" environment variable are passed to the kernel. Bootargs is a space-delimited list of "name=value" definitions. The items relevant to SD-booting are "root", "rootfstype", and "rootdelay".

For example, the following parameters would tell the kernel to mount the third partition of the SD-card as an ext3 filesystem:

root=/dev/mmcblk0p3 rootfstype=ext3 rootdelay=5

The "rootdelay" parameter allows time for the card to be properly initialized before it is accessed.

Note that the kernel must have built-in support (i.e. not a module) for the filesystem specified in "rootfstype". The default Openmoko kernel configs as of [http://git.openmoko.org/?p=kernel.git;a=commit;h=642cbda5f3b7e7a61512426e1d30a41ab4691123| 2008-07-17] have built-in support for both ext2 and ext3. You can check the available filesystems with the Linux command

less /proc/filesystems

It is not possible to use VFAT for the root filesystem.

==== ext2 vs. ext3 ====

Opinion is divided on whether it is better to use ext2 or ext3 for the root filesystem. Ext3 in general is a superior choice, because it is a journalled filesystem and so does not require a long 'fsck' (file system check) after an unclean shutdown. However, if used on a flash device that does not support wear-leveling then ext3 may cause premature wear on the blocks of the card where the journal is stored. SD cards are supposed to support wear leveling, but this can not be guaranteed for all vendors.

== Acquiring a tarfile rootfs ==

There are two ways of acquiring an rootfs image as a tar archive. You can either build it on your own using the OpenEmbedded Distribution. Or download it from the openmoko buildhost.

=== Possibility 1: Downloading the rootfs/kernel tar from the Openmoko buildhost ===

Choose and find the rootfs/kernel combo you would like to install at [[Latest Images]].

=== Possibility 2: Building a tarfile distribution using OpenEmbedded ===

Another possibility to get a tar archive of your rootfs is to build it on your own with the OpenEmbedded environment.

To build OM-2007.2 you need to add "tar" to the image types in your ''local.conf'':

IMAGE_FSTYPES = "jffs2 tar"

After that build a new image by issuing:

bitbake openmoko-devel-image

or if you are using the MokoMakefile:

make openmoko-devel-image

After the process finished there will be a ''OpenMoko-....tar'' in the deploy directory, which is your newly created rootfs archive

=== Possibility 3 : Convert a jff2 image to a tarfile ===

See [[Userspace root image]] for more details on how to access contents of a jffs2 image.

== Prepare the SD card ==

=== Partioning the SD card ===

u-boot pre-2008-07-23 can only boot from FAT filesystems; if you update u-boot, you can boot from FAT or ext2.
This example shows how to do an example partition using the fdisk utility. Feel free to use the partitioning utility of your liking for this task.

fdisk /dev/mmcblk0

'''''Note:''''' The device file might differ on your system. If you are not sure about it, you may check your kernel message log by calling ''dmesg'' to find the correct device.

We will now create a 8 mb partition for our kernel and another one for the rootfs which will take up all the remaining space.

Command (m for help): d
Selected partition 1
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-983, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-983, default 983): +8M
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (18-983, default 18):
Using default value 18
Last cylinder or +size or +sizeM or +sizeK (18-983, default 983):
Using default value 983
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.

''Should probably need to change type of first partition to FAT 16 too ?''

=== Formatting the SD card ===

Just issue the following command to create at FAT filesystem:

mkfs.vfat /dev/mmcblk0p1

Note: if you do not have mkfs.vfat you must find and install the "dosfstools" package. This package does not seem to be in the official feeds, but an unofficial build may be downloaded from http://members.shaw.ca/mmontour/neo/dosfstools_2.11-r0_armv4t.ipk

The second partition is about to be formatted with ext3 (for ext2 to work you need to make sure you compiled the kernel with the correct configuration):

mkfs.ext3 /dev/mmcblk0p2

== Populate SD card ==

Your sd card is now ready to be filled up with the rootfs and the needed kernel to boot.

Mount the second partition of your SD card somewhere and put the image on it:

mount /dev/mmcblk0p2 /mnt/moko
tar -C /mnt/moko/ -xzvf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz

'''''Note:''''' As always in this guide the device name as well as the rootfs name needs to be adjusted to your device and filename structure

'''''Note:''''' There's a nice gotcha to take care about if you use your host OS automount. Some hosts mount these removable devices with "nodev" option by default for security. If the image you are unpacking has a populated /dev directory, the nodes will fail to create as devices then. If auomounting the SD on your host, confirm there are no unexpected mount options by using "mount" command alone to list the mounts.

The next step is to mount the first partition of the sd card and install the kernel on it.

mount /dev/mmcblk0p1 /mnt/mokokernel
cp uImage-fic-gta01-latest.bin /mnt/mokokernel/uImage.bin

Make sure your kernel is called ''uImage.bin'' after copying it to the card. If the u-boot doesn't find the kernel image during boot, log into the bootloader with ''cu'', mount the partition with mmcinit and check the presence and the name of the kernel image with ''fatls mmc 1:1''.

Unmount both the rootfs partition and the kernel partition and make sure all remaining buffers are written to it:

umount /mnt/moko
umount /mnt/mokokernel
sync

== Add uboot boot entry ==
Depending on the revision of the phone and the partition type (ext2/ext3) you are using, it might be necessary to add an entry to the bootmenu to be able to boot the system off your SD card.
If you are using a Freerunner and have created an FAT kernel/ext2 rootfs partition you should be able to boot from the card right out of the box, because a boot menu entry for this should already exist in the NOR/NAND boot menu.
In any other case you should at least make sure the needed entry exists in your menu before proceeding.
You will need to enter the uboot shell of the NAND boot menu for this. A description on how to connect to the uboot loader shell can be found in this article: [[Uboot#Bootloader_prompt]]. Details on howto get into the NAND boot menu can be found [[Booting#Log_into_U-Boot_in_the_NAND_Flash|here]].

After you read these two references you should be connected to your NAND uboot shell right now. The first thing to do is to set the boot menu timeout to a really high value. Unfortunately if you don't do this, the boot loader will continue booting after the default timeout (60 seconds) even if you are connected to the uboot shell. Just enter the following command to the menu prompt:

setenv boot_menu_timeout 99999

This will set the timeout to 99999 seconds which should definitely enough time for us finish whatever work we want accomplish in the boot loader shell.

Now we will make sure a appropriate menu item for booting from sd exists, or create it otherwise. You can print the defined boot loader environment by issuing the command:

printenv

If it shows a line beginning with ''menu_'' followed by the commands which are just to follow in this guide, you do not need to create a new menu entry. In any other case please proceed with the following.

Please make sure you are using the correct configuration based on the decisions you made earlier. For more information on the uboot prompt, see
help
help <command>
and [[Bootloader]] and [[Bootloader commands]].

{{Note| The backslashes (\) are important for uboot to set the command as new environment variable (menu_9) instead of just executing them as soon as enter is pressed.}}

{{Note| Copy and paste may not work depending on your terminal emulator. Commi just works or you can use [[NeoCon|neocon]] terminal emulator and add a per-character delay. Otherwise, you will have to type in the commandline manually.}}

It is important to distinguish between FAT or ext2 kernel partitions and ext2 or ext3 root partitions at this point.

Please watch partition numbers in the following commands. In particular, you may need to change root=/dev/mmcblk0p'''#''' and fatload mmc '''#''' or ext2load mmc '''#''' depending on which partition number your root and kernel, respectively, are located. Number starts from unity.

'''Boot entry for FAT kernel+ext3 rootfs partitions:'''

setenv menu_9 Boot from microSD (FAT+ext3): setenv bootargs \${bootargs_base} rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for FAT kernel+ext2 rootfs partitions:'''

setenv menu_9 Boot from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

or : with additional 'init=/sbin/init' kernel parameter (may be needed for some images) :
setenv menu_9 Boot 200808 from microSD (FAT+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} init=/sbin/init ro\; mmcinit\; fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for ext2 kernel+ext2 rootfs partitions: (requires newer u-boot)'''

setenv menu_2 Boot from microSD part2 (ext2+ext2): setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000

'''Boot entry for kernel and rootfs on same ext2 partition (tested with Qtopia/requires newer u-boot)'''
setenv menu_3 QTopia: setenv bootargs \${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p1 rootdelay=5 \${mtdparts} ro\; mmcinit\; ext2load mmc 1:1 0x32000000 \${sd_image_name}\; bootm 0x32000000
You are nearly done. Just issue a

printenv

and verify that your newly created entry is correctly displayed (This time the backslashes are not displayed anyone).

If everything looks fine enter

saveenv

into the prompt and press enter. The new configuration should now be saved to the NAND.

Shutdown your neo with the following command:

neo1973 power-off

After you restarted the Neo and got back to the NAND boot menu you should be able to select your newly created menu entry and successfully boot into the rootfs from your SD card.

----

See also [[Moving current system from flash to SD]] which shows how to move the running system currently running in flash to an SD card, in order to keep a backup system on SD on which to boot from.

----

== Appendix ==

=== Boot from SDHC ===

{{Note|the following text was written for the Neo1973. SDHC and SD should both work in a Freerunner if you have u-boot from 2008-07-23 or later.}}

As SDHC is not supported in older u-boot versions you can't use the Booting from SD guide.
But there's a kind of workaround that is a good option to have at least your rootfs on the microSDHC:

First you can follow Step 1 to get an kernel-image with mmc- and ext2-support. But instead of copying the image to the rootfs you will have to flash it to the Neo's internal NAND-Flash (using [[Dfu-util]]).
Now you can continue with Step 2 (like mentioned before you do not have to copy your uImage to the rootfs) and follow the instructions to Step 3.
Instead of the setenv commands in Step 3 you have to enter the following:

GTA01Bv4 # setenv menu_5 Boot from SDHC: setenv bootargs root=/dev/mmcblk0p1 console=tty0 rootdelay=5 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

And that's it!
Now you can use the newly created menu option "Boot from SDHC" to boot the internal kernel, using the root-filesystem on the microSDHC.

=== Autoboot from SDHC ===

Maybe you want to Boot automatically from SDHC:
Set a new Bootmenu Entry for booting from NAND first

GTA01Bv4 # setenv menu_6 Boot from NAND: setenv bootargs \${bootargs_base} \${mtdparts}\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

then Power-off, and enter the Bootmenu to test the new Entry.If you can boot from NAND, shutdown, enter Boot menu, connect to bootloader and set the (auto)bootcmd for boot from SDHC:

GTA01Bv4 # setenv bootcmd setenv bootargs root=/dev/mmcblk0p1 rootdelay=10 console=tty0 neo1973-nand:0x00040000(u-boot),0x00004000(u-boot_env),0x00200000(kernel),0x000a0000(splash)\; nand read.e 0x32000000 kernel\; bootm 0x32000000
GTA01Bv4 # saveenv

Now you boot from SDHC everytime you press the Power-Button or reboot and if you like to boot from NAND -just use the bootmenu.

=== Fixing udev automount ===

Udev automatically mounts the SD Card in /media/mmcblk0p1/ you can disable this with

echo /dev/mmcblk >> /etc/udev/mount.blacklist

=== Remarks on Kernel Parameters ===

==== loglevel ====

Some people suggested adding:

loglevel=8

to the kernel command line. IF you also have "console=tty0" on your kernel commandline this makes the boot process extremely slow because the framebuffer (the neo display in text mode) has to print out tons of lines of debug messages like:

s3c2410-sdi s3c2410-sdi: ......
mmc0: ....

{{Languages|Booting_from_SD}}

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

Talk:FreeRunner unable to work with 3G SIM cards

2008-08-13T13:24:04Z

Kevin:

TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and to GTA02 (Neo Freerunner).
I've got a message from Joachim Steiger (roh) who is currently researching this bug and he said he will post everthing new to the ticket in TRAC, the problem concerns also the Freerunner.
He does still not know what the reason for the problem is, but its definitly not a 3G simcard problem, it's a problem with a few simcard models of (some/the same) manufacturer. [[User:Kevin|Kevin]]

Talk:FreeRunner unable to work with 3G SIM cards

2008-08-13T13:23:40Z

Kevin: New page: TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and to GTA02 (Neo Freerunner). I've got a message from Joachim Steiger (roh) who is currently resear...

FreeRunner unable to work with 3G SIM cards

2008-08-13T13:13:13Z

Kevin: Trac Ticket 666 applies also to GTO02

== FreeRunner SIM compatibility ==

See also: [[Freerunner_Hardware_Issues#Some_SIMs_Don.27t_Work|Freerunner Hardware Issues]]

=== Carrier ===

There is carrier page documented carriers compatibility [[Carriers]]

=== TRAC Ticket 666 ===
TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and <strike>NOT</strike> to GTA02 (Neo Freerunner). Bug applies to both, see discussion.

== Compatibility table (FreeRunner/GTA02)==

Please fill out following table .

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
!Carrier Name!! Error Message !! SIM Card Type!! Country !!Link to picture of SIM card!!Your name!!Did new SIM card solve problem?||Notes
|-
| CHT || Unable to use GSM ||Dont' know|| R.O.C Taiwan || no pics ||王孟蒂 Brenda Wang|| ||When I put it on my Neo, it can't dial out
|-
| AT&T || Unable to use GSM || 71234 G || US || no pics || || || 71234 G SIM not working, 71234 O somebody in discuss thread say it could work
|-
| AT&T || Failed to register || 71234 D|| US || see below || [[Special:Emailuser/Safire|Safire]] || Switched to T-Mobile || Got strong Signal Bars with 2007.2 image despite "Registering...". Actually managed to dial and remote phone showed number, but never completed a full call. Dialer kept crashing. Pre-paid brand new sim, purchased July 2008
|-
| Vodafone || cme 13, 32 || some 3G capable|| DE || no pics || [[Special:Emailuser/Fsp|Fsp]] || no || most up-to-date Plan debitel
|-
| T-Mobile || No Error || 2G SIM || US || no pics || Community List || || Pre-paid SIM
|-
| e-plus || not working || 3G SIM || DE || no pics || Community List || || Plan SIM
|-
| e-plus (SIMYO) || 2G seems working/3G not || 2G/3G SIM || DE || no pics || Community List || || Pre-Paid SIM https://www.simyo.de/de/informieren/umts.html SIMYO has 2 voltage 1.8/3.3v 72K 1.8V #569 J276/2K 3V #568 H276
|-
| e-plus || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| O2 || Not certain/Not working || 3G SIM || DE || no pics || Community List || || Plan SIM, CME: 32, (1001710251761MC working)
|-
| O2 || not working || 3G sim || DE || [http://kev.knet.eu/bugs/openmoko/sim-card/not_working_O2.png link] || [[Special:Emailuser/Kevin|Kevin]] || Did not solve. Both simcards (7 month old one and new one) are looking identical. || I would like to help on testing/whatever, feel free to contact me.
|-
| vodafone(D2 Mannesmann) || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| Blau SIM || some working || 2G/3G SIM || DE || no pics || Community List || || 16K 3V #343 H73 (not work)
|-
| Orange || working || 2G/3G some wokring || DE || no pics || Community List || || None
|-
| T-Mobile || Not certain/Not working || unknown || DE || no pics || Community List || || None
|-
| o2 || cme error: 100 
cme error: 313
|| 2G possibly 3g? || UK || no pics.. YET. || [[Special:Emailuser/tdobson|tdobson]] || other SIMs work - MTS(RU) Orange(UK) Vodafone(UK) || Prepaid. Feel free to contact me.
|-
|}

== User Provided tested SIM pictures ==

[[Image:ATT_3G_71234D_SIM.JPG|left|thumb|200px|AT&T 3G 71234 D]]

Base on community post:

The 71324 is the SKU for the AT&T latest UICC.
The 2022 is the Vendor and Version number.

Some cards the vendor numbers are
2 - G&D
3 - Gemalto
4 - Oberthur

Usually user will get CME ERROR 13 (sim failure), rather than CME ERROR 10 (sim not inserted) when 3G SIM not working.

CME ERROR: 32 is Network not allowed, emergency calls only, might because the card not activated.

== The Error ==
<pre>
Here is the AT command:

root@om-gta02:~# libgsmd-tool -m atcmd
libgsm-tool - (C) 2006-2007 by Harald Welte and OpenMoko, Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT
STR=`AT'
RSTR=`OK'
AT+CFUN=1
STR=`AT+CFUN=1'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CPIN="MyPIN"
STR=`AT+CPIN="MyPIN"'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CREG=1
STR=`AT+CREG=1'
RSTR=`OK'
AT+COPS=0
STR=`AT+COPS=0'
EVENT: Netreg searching for network
EVENT: Netreg registration denied
cme error: 32
RSTR=`+CME ERROR: 32'
EVENT: Signal Quality: 31
EVENT: Signal Quality: 31
</pre>

== Working SIM pics ==

[[Image:Adam_20080713_working_back.JPG]]

== Not Working SIM pics ==
* AT&T

[[Image:Adam_20080713_back_notworking.JPG]]

* Orange France

[[Image:Jean_20080715_orange_back_notworking.JPG.gif]]

[[Category:Information]]

FreeRunner unable to work with 3G SIM cards

2008-08-06T12:30:43Z

Kevin: Added new not working O2 simcard in germany

== FreeRunner SIM compatibility ==

See also: [[Freerunner_Hardware_Issues#Some_SIMs_Don.27t_Work|Freerunner Hardware Issues]]

=== Carrier ===

There is carrier page documented carriers compatibility [[Carriers]]

=== TRAC Ticket 666 ===
TRAC ticket [http://docs.openmoko.org/trac/ticket/666 666] applies to GTA01 (Neo 1973) and NOT to GTA02 (Neo Freerunner).

== Compatibility table (FreeRunner/GTA02)==

Please fill out following table .

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="3" border="1"
!Carrier Name!! Error Message !! SIM Card Type!! Country !!Link to picture of SIM card!!Your name!!Did new SIM card solve problem?||Notes
|-
| CHT || Unable to use GSM ||Dont' know|| R.O.C Taiwan || no pics ||王孟蒂 Brenda Wang|| ||When I put it on my Neo, it can't dial out
|-
| AT&T || Unable to use GSM || 71234 G || US || no pics || || || 71234 G SIM not working, 71234 O somebody in discuss thread say it could work
|-
| AT&T || Failed to register || 71234 D|| US || see below || [[Special:Emailuser/Safire|Safire]] || Switched to T-Mobile || Got strong Signal Bars with 2007.2 image despite "Registering...". Actually managed to dial and remote phone showed number, but never completed a full call. Dialer kept crashing. Pre-paid brand new sim, purchased July 2008
|-
| Vodafone || "SIM not inserted" || some 3G capable|| DE || no pics || Felix Mahnke || || card is a a contracted debitel from April 2007
|-
| T-Mobile || No Error || 2G SIM || US || no pics || Community List || || Pre-paid SIM
|-
| e-plus || not working || 3G SIM || DE || no pics || Community List || || Plan SIM
|-
| e-plus (SIMYO) || 2G seems working/3G not || 2G/3G SIM || DE || no pics || Community List || || Pre-Paid SIM https://www.simyo.de/de/informieren/umts.html SIMYO has 2 voltage 1.8/3.3v 72K 1.8V #569 J276/2K 3V #568 H276
|-
| e-plus || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| O2 || Not certain/Not working || 3G SIM || DE || no pics || Community List || || Plan SIM, CME: 32, (1001710251761MC working)
|-
| O2 || not working || 3G sim || DE || http://kev.knet.eu/bugs/openmoko/sim-card/not_working_O2.png || [[Special:Emailuser/Kevin|Kevin]] || Did not solve. Both simcards (7 month old one and new one) are looking identical. || I would like to help on testing/whatever, feel free to contact me.
|-
| vodafone(D2 Mannesmann) || working || 2G SIM || DE || no pics || Community List || || Plan SIM
|-
| Blau SIM || some working || 2G/3G SIM || DE || no pics || Community List || || 16K 3V #343 H73 (not work)
|-
| Orange || working || 2G/3G some wokring || DE || no pics || Community List || || None
|-
| T-Mobile || Not certain/Not working || unknown || DE || no pics || Community List || || None
|-
| o2 || "Dialer Error: No Network" || 2G possibly 3g? || UK || no pics.. YET. || [[tdobson]] || other SIMs work - MTS(RU) Orange(UK) Vodafone(UK) || Prepaid. Freely available. )
|-
|}

== User Provided tested SIM pictures ==

[[Image:ATT_3G_71234D_SIM.JPG|left|thumb|200px|AT&T 3G 71234 D]]

Base on community post:

The 71324 is the SKU for the AT&T latest UICC.
The 2022 is the Vendor and Version number.

Some cards the vendor numbers are
2 - G&D
3 - Gemalto
4 - Oberthur

Usually user will get CME ERROR 13 (sim failure), rather than CME ERROR 10 (sim not inserted) when 3G SIM not working.

CME ERROR: 32 is Network not allowed, emergency calls only, might because the card not activated.

== The Error ==
<pre>
Here is the AT command:

root@om-gta02:~# libgsmd-tool -m atcmd
libgsm-tool - (C) 2006-2007 by Harald Welte and OpenMoko, Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT
STR=`AT'
RSTR=`OK'
AT+CFUN=1
STR=`AT+CFUN=1'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CPIN="MyPIN"
STR=`AT+CPIN="MyPIN"'
RSTR=`OK'
AT+CPIN?
STR=`AT+CPIN?'
RSTR=`+CPIN: SIM PIN'
AT+CREG=1
STR=`AT+CREG=1'
RSTR=`OK'
AT+COPS=0
STR=`AT+COPS=0'
EVENT: Netreg searching for network
EVENT: Netreg registration denied
cme error: 32
RSTR=`+CME ERROR: 32'
EVENT: Signal Quality: 31
EVENT: Signal Quality: 31
</pre>

== Working SIM pics ==

[[Image:Adam_20080713_working_back.JPG]]

== Not Working SIM pics ==
* AT&T

[[Image:Adam_20080713_back_notworking.JPG]]

* Orange France

[[Image:Jean_20080715_orange_back_notworking.JPG.gif]]

[[Category:Information]]