Hello Jose,
thank you for answer,
well I got some information, but did not get this damned thing started.
I wrote the whole menu-entry, as you described on the device, but its
still impossible to boot. Same error:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown
block (179,2)
Which confuses me allready because major device number 179 is something
like: /dev/xsvc high speed shared mem/ semaphore service?
the new settings are these:
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=0x88
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
boot_menu_timeout=180
the bootargs_base are not quit correct but getting overwritten by the
entries in menu_1? (I suppose)
what is really confusing, I managed to read from the ext2 partition:
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 then:
GTA02v6 # ext2ls mmc 0:2
<DIR> 4096 .
<DIR> 4096 ..
<DIR> 16384 lost+found
79160282 full-om-gta02.tar.gz
<DIR> 4096 sbin
<DIR> 4096 usr
<DIR> 4096 proc
<DIR> 4096 etc
<DIR> 4096 tmp
<DIR> 4096 bin
<DIR> 4096 home
<DIR> 4096 var
<DIR> 4096 mnt
<SYM> 12 linuxrc
<DIR> 4096 dev
<DIR> 4096 sys
<DIR> 4096 lib
<DIR> 4096 media
<DIR> 4096 boot
wow, there is a fs on, defently ;-) But I got this only one time going.
The next time I tried this, the U-Boot dived at periscope depth, it
crashed! And this happens each time I try this.
U-Boot knows ext2, this is for sure, but it is probably not very stable?
The local medicine-man here in my town supposes that there is a evil
daemon on the microSD-card.
GTA02v6 # ext2ls mmc 0:2
data abort
pc : [<33fa1f98>] lr : [<33fa253c>]
sp : 33ed80f4 ip : 00001000 fp : 33ed8190
r10: 33ed8140 r9 : 00000000 r8 : 33edbfdc
r7 : 33f26958 r6 : 00000002 r5 : 067db028 r4 : 340071ac
r3 : 33ed8164 r2 : 00000008 r1 : 00000000 r0 : 00000001
Flags: nZCv IRQs on FIQs off Mode SVC_32
Resetting CPU ...
cu: Got hangup signal
Just for information, the mtdblocks are the partitions of the
NAND-flash? mtdblock0 to mtdblock6 and they are hosting the u-boot and
its enviroment and data?
mmcblk0 is the microSD-card? The mtdblock has the major number 31, and
mmcblk 179? strange!
On 23/05/2011 09:42, wrote Jose Luis Perez Diez:
> A Dissabte 21 Maig 2011 18:09:17, Christian va escriure:
>
>> On 20/05/2011 17:54, wrote Flemming Richter Mikkelsen:
>>
>>> This is as I expect as (as far as I know), uboot does not support
>>> ext2/ext3. Uboot should find a kernel (uImage.bin) on the first
>>> partition (mmcblk0p1) and boot that kernel.
>>>
>> Ahh okay
>>
> Not true. NOR uboot can't read ext2, but most of the 2008 uboots can
>
>
>> ...
>> I tried with:
>>
>> setenv menu_1 Boot from microSD (FAT+ext2): bootcmd=setenv bootargs
>> rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
>> fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
>>
>> after that the device rebootet straightaway. I did not have the chance
>> to call saveenv.
>>
> It booted immediately because incorrect escaping ";" are to be escaped
> or act as command separator ending the variable declaration and the next
> command will run(all ; and $ and linefeed shall be escaped):
>
> setenv menu_1 Boot from microSD (FAT+ext2): bootcmd=setenv bootargs
> rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 \${mtdparts} ro\;
> mmcinit\;fatload mmc 1 0x32000000 \${sd_image_name}\; bootm 0x32000000
>
>
>
>> After the reboot I got the error unable to mount rootfs on unknown-block
>> (179,2)
>>
> Are you sure of the partition table on the SD ( mine has only two partitions
> fat on partition one and ext3 on partition 3) and it boots the following:
>
> bootargs_card=rootfstype=ext3 console=ttySAC2,115200 console=tty0 rootwait
> glamo_mci.sd_max_clk=16373000 g_ether.host_addr=00:1F:11:01:1F:C2
> g_ether.dev_addr=00:1F:11:01:1F:C2 regular_boot
> mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
> level=loglevel=7
> sd_image_name=/boot/uImage-GTA02.bin
> bootcmd=setenv bootargs ${bootargs_card} ${mtdparts} ${level}
> root=/dev/mmcblk0p3 ; mmcinit;ext2load mmc 1:3 0x32000000
> ${sd_image_name};bootm 0x32000000
>
>
> _______________________________________________
> Shr-User mailing list
> [email protected]
> http://lists.shr-project.org/mailman/listinfo/shr-user
>
>
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
