User:Vpv/Booting Qtopia
From Openmoko
m (→Setting up u-boot) |
m (→Setting up u-boot) |
||
(One intermediate revision by one user not shown) | |||
Line 9: | Line 9: | ||
* When the menu hopefully comes up in neocon do: | * When the menu hopefully comes up in neocon do: | ||
setenv menu_1 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 | setenv menu_1 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 | ||
+ | (Thanks to [http://lists.openmoko.org/pipermail/community/2008-July/021524.html Thomas B.] for this fix) | ||
* Then save the environment by doing: | * Then save the environment by doing: | ||
saveenv | saveenv | ||
Line 20: | Line 21: | ||
== Actually booting Qtopia on the phone == | == Actually booting Qtopia on the phone == | ||
Insert the SD card into the phone, boot to NAND u-boot (again, '''not''' to NOR), choose <tt>Boot from microSD (FAT+ext3)</tt> and the phone should start booting Qtopia. | Insert the SD card into the phone, boot to NAND u-boot (again, '''not''' to NOR), choose <tt>Boot from microSD (FAT+ext3)</tt> and the phone should start booting Qtopia. | ||
+ | |||
+ | == Other stuff == | ||
+ | * To make it clear, you boot into NAND by first pressing the Power button for a second or two and then pressing the AUX button while still holding down the Power button. If you do it "the other way around", it'll boot into NOR. | ||
+ | * Neocon seems to sometimes "lock" the tty device completely to itself and the only thing I've come up with then is to reboot the host system. |
Latest revision as of 21:33, 15 July 2008
Contents |
[edit] How to boot Qtopia from the SD card
This howto is probably incomplete. I also suggest not to directly copy paste anything from here, because I've written this after doing all the work. In case it's important, I used Fedora to do all this stuff.
[edit] Setting up u-boot
- Get NeoCon and run it as follows:
sudo ./neocon -t 30 /dev/ttyACM0
- Boot into NAND u-boot (not NOR) with the USB cable connected between the phone and your computer, see Getting_Started_with_your_Neo_FreeRunner#Log_into_U-Boot_in_the_NAND_Flash
- NAND is usually the one without the nice Openmoko logo ;)
- When the menu hopefully comes up in neocon do:
setenv menu_1 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
(Thanks to Thomas B. for this fix)
- Then save the environment by doing:
saveenv
This should make the Neo boot from an ext3 partition on the SD card. The kernel can't boot from an ext2 partition currently even though it was the default setting for the bootloader.
[edit] Getting Qtopia and extracting the jffs2 image
- Get the jffs2 image from http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6
- The image needs to be extracted so that the files can be copied to the SD card. Follow the instructions in Userspace_root_image#Mounting_the_JFFS2_image_on_a_loop_back_device_.28Kernel_Memory_MTD_Emulation.29
- Follow the instructions in Boot_from_sd_card, but remember to make the second partition ext3, not ext2. You should have a uImage.bin file for the kernel partition and a bunch of directories extracted from the jffs2 image for the root file system partition.
[edit] Actually booting Qtopia on the phone
Insert the SD card into the phone, boot to NAND u-boot (again, not to NOR), choose Boot from microSD (FAT+ext3) and the phone should start booting Qtopia.
[edit] Other stuff
- To make it clear, you boot into NAND by first pressing the Power button for a second or two and then pressing the AUX button while still holding down the Power button. If you do it "the other way around", it'll boot into NOR.
- Neocon seems to sometimes "lock" the tty device completely to itself and the only thing I've come up with then is to reboot the host system.