Hello!
My device is TDM-3730W.
I installed prebuilt filesystem and uImage from DVSDK (dvsdk_dm3730-evm_04_03_00_06_setuplinux) on SD card (2GB Micro Transcend Card).
But Linux doesn't mount. I have got the error
[ 5.358489] VFS: Cannot open root device "b302" or unknown-block(179,2) [ 5.365447] Please append a correct "root=" boot option; here are the available partitions: [ 5.374237] 1f00 512 mtdblock0 (driver?) [ 5.379547] 1f01 1280 mtdblock1 (driver?) [ 5.384826] 1f02 768 mtdblock2 (driver?) [ 5.390136] 1f03 5120 mtdblock3 (driver?) [ 5.395446] 1f04 516608 mtdblock4 (driver?) [ 5.400726] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
Then I recompiled kernel (only kernel, not rootfs) with different defconfig options
sudo make omap3_evm_defconfig ARCH=arm CROSS_COMPILE=$myPATH/arm-none-linux-gnueabi-
Also I tried omap3_beagle_defconfig and davinci_all_defconfig.
Nothing helps! Wouldn't you help me please?
Thank you for attention.
Check 'bootargs' environment variable setting in uboot. You need to pass the filesystem type and location to the kernel using the bootargs variable.
For example, if your rootfs resides on the second partition of your SD card, then you need to tell the kernel about it by adding the following information "root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait" to the bootargs env variable.
I suggest you check the Linux User Guide for your SDK.
Carlos
Thank you, Carlos Hernandez
I already did it but it didn't help.
[ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait omap_vout.vid1_static_vrfb_alloc=y
And I got error
[ 4.189239] Waiting for root device /dev/mmcblk0p2... [ 4.229125] mmc0: new high speed SD card at address e624 [ 4.235809] mmcblk0: mmc0:e624 SU02G 1.84 GiB (ro) [ 4.250549] mmcblk0: p1 p2 [ 4.326934] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2) [ 4.334350] Please append a correct "root=" boot option; here are the available partitions: [ 4.343170] 1f00 512 mtdblock0 (driver?) [ 4.348754] 1f01 1280 mtdblock1 (driver?) [ 4.354064] 1f02 768 mtdblock2 (driver?) [ 4.359375] 1f03 5120 mtdblock3 (driver?) [ 4.364685] 1f04 516608 mtdblock4 (driver?) [ 4.369995] b300 1931264 mmcblk0 driver: mmcblk [ 4.375549] b301 48163 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1 [ 4.383972] b302 1879605 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
I noticed that MLO-dm37x-evm and u-boot-dm37x-evm from DVSDK's (4) prebuilt-images directory are not supported by my board (TDM-3730W)
Why so? I have made bootable SD card, but u-boot doesn't start
May be it is the reason of troubles with mounting?
I saw it in this post:
http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/136589.aspx
try another SD card
Hongfeng Wang,
I worked with three SD cards.
I will be grateful for any useful suggestions (only not "bye another board" :))
Where did you mention you already tried 3 cards in your original post?You are really nice to people who are trying to help you. good luck.
The 2GB size can be a problem with older card readers. Maybe try a 1GB card or 4GB card. The 2GB card requires a MBR with the proper size. You might have erased that MBR by accident.
The boot log shows the cards as "(ro)" or read-only, The file system needs to be writeable. Check the lock switch in the card. Check your board's card socket for the r/w signal.