Hello, and thank you for your help so far.

I connected my device via USB and read some paramater. Ahh something
strange first: I made an update of U-Boot. I downloaded it from here:
http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20100131/
but the prompt I get is still UBoot 1.3.2-moko12 May 9 2008. I have
allready heared that U-Boot is not so strong supported any longer, but
is this really the newest release?

Anyway: I connected to my device with cu. Then I called a printenv:

GTA02v6 # printenv
boot_menu_timeout=60
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6
console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e
0x32000000 kernel 0x200000; bootm 0x32000000
bootdelay=5
menu_1=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
menu_4=Set console to USB: setenv stdin usbtty; setenv stdout usbtty;
setenv stderr usbtty
menu_5=Set console to serial: setenv stdin serial; setenv stdout serial;
setenv stderr serial
menu_6=Reboot: reset
menu_8=Power off: neo1973 power-off
sd_image_name=uImage.bin
stderr=usbtty
stdin=usbtty
stdout=usbtty
usbtty=cdc_acm
mtdids=nor0=physmap-flash,nand0=neo1973-nand
pcb_rev=0x101
pcf50633_int1=0x80
pcf50633_int2=0x02
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
partition=nor0,0
mtddevnum=0
mtddevname=nor

Environment size: 1093/262140 bytes

Changed the bootdelay to 10. Saved that change and tried again , but the
problem remains.
I tried to initialize the microSD-card:

GTA02v6 # mmcinit
Card Type:          SD 2.0 SDHC
Manufacturer:       0x02, OEM "TM"
Product name:       "SA04G", revision 0.4
Serial number:      2620391846
Manufacturing date: 2/2010
MMC/SD size:        3MiB

and tried to read from it:

GTA02v6 # ext2ls mmc 0
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **

Ahh this is new. I get a new error: 1.8900000] SoftDog: cannot register
miscdev on minor = 130 (err=-16)

I think that my settings are quit normal, the only thing which stands
out is "root=/dev/mtdblock6" instead of mtdblock4. But there is no
information about the meaning:
http://wiki.openmoko.org/wiki/Bootloader_environment.

Anybody who knows where the problem is?

Thanks Christian



Am 15.05.2011 17:33, schrieb Martin Jansa:
> On Sun, May 15, 2011 at 04:26:05PM +0100, Neil Jerram wrote:
>   
>> Christian <[email protected]> writes:
>>
>>     
>>> Hello out there,
>>> I own a GTA02 and want to install SHR on my microSD card. First I
>>> divided the SDcard into two partitions: one vFAT with 100 MB and the
>>> second with rest of that 4GB card. The file system on the second is
>>> ext2. I fetched the full-om-gta92.tar.gz archiv from this side:
>>> http://build.shr-project.org/shr-testing/images/om-gta02/ untared it on
>>> the second partition and fetched the kernel image
>>> uImage-2.6.29-oe11+gitr0+973a41fce60e5f6edfcf0eaf94056a57eee65e16-r8-om-gta02.bin
>>> from the same resource, and wrote it to the first partition. After that
>>> I started my moko and the Uboot-loader was unable to load the kernel. So
>>> I renamed the kernel to plain uImage.bin which enabled the bootloader to
>>> load the kernel, but stalled with a kernel panic: not syncing VFS:
>>> unable to mount root fs on unknown-block(179,2). Later I copied the
>>> kernel of the archiv (in /boot/uImage-2.6.29-rc3) into the first
>>> partition with the same effect. Just after I renamed the kernel to
>>> uImage.bin it was possible for the bootloader to read the kernel-image
>>> but I got the very same kernel panic. What could be the problem here?
>>>       
>> Sounds like the kernel doesn't know that it should be getting its rootfs
>> from your second partition.
>>
>> The fix will probably be somewhere in your u-boot or qi configuration,
>> so you may like to read the Wiki pages on those.
>>     
> As Neil said, this looks like problem of your u-boot env, try with
> longer rootdelay if you have really slow uSD card.
>
> And if you want newer shr-testing then use images from
> http://build.shr-project.org/shr-testing2011.1/
>
> what you've installled is about year old..
>
> Cheers,
>
>   

_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to