[meta-freescale] Loading kernel - can't see partition

[Paweł Krzyżanowski]

Hello,
I would like to ask about some hints/solutions to my problem.

I have custom i.MX6 board based on MX6SL/RIoTBoard (with several changes).
I can load U-boot successfully to my board (through USB since I don't have
proper boot selection).
Linux:
git://github.com/embest-tech/linux-imx.git -b embest_imx_3.0.35_4.0.0
Which has imx6s_defconfig and have support to imx6sl processors
(support.png)

I put SD card to slot 1. Card have two partitions:
1st. fat (for u-boot)
2nd. ext3 (with root folder)

And I can list 2nd (ext3) in boot:

   1. MX6Sl EVK U-Boot > mmc dev 0
   2. mmc0 is current device
   3. MX6Sl EVK U-Boot > ext2ls mmc 0:2
   4. <DIR>       4096 .
   5. <DIR>       4096 ..
   6. <DIR>      16384 lost+found
   7. <DIR>       4096 mnt
   8. <DIR>       4096 var
   9. <DIR>       4096 etc
   10. <DIR>       4096 lib
   11. <DIR>       4096 usr
   12. <DIR>       4096 opt
   13. <DIR>       4096 home
   14. <DIR>       4096 boot
   15. <DIR>       4096 sys
   16. <DIR>       4096 bin
   17. <DIR>       4096 proc
   18. <DIR>       4096 run
   19. <DIR>       4096 dev
   20. <DIR>       4096 unit_tests
   21. <DIR>       4096 sbin
   22. <DIR>       4096 tmp
   23. <DIR>       4096 media


To load kernel I use:

   1. MX6Sl EVK U-Boot > ext2load mmc 0:2 0x80800000 /boot/uImage
   2. Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
   3. 3330308 bytes read
   4. MX6Sl EVK U-Boot > bootm 0x80800000
   5. ## Booting kernel from Legacy Image at 80800000 ...
   6.    Image Name:   Linux-3.0.35-02887-g731b440-dirt
   7.    Image Type:   ARM Linux Kernel Image (uncompressed)
   8.    Data Size:    3330244 Bytes =  3.2 MB
   9.    Load Address: 80008000
   10.    Entry Point:  80008000
   11.    Verifying Checksum ...


Everything goes quite nice untill it try to mount filesystem (I try
mtdblock2 since I expect there will be filesystem)

   1. VFS: Cannot open root device "mtdblock2" or unknown-block(0,0)
   2.
   Please append a correct "root=" boot option; here are the available
partitions:
   3. 1f00              64 mtdblock0
   4. (driver?)
   5.
   Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)

And when I try to mount only one visible mtdblock0 (size 64 -> definitely
sth is wrong here)

   1. jffs2: Too few erase blocks (2)
   2. List of all partitions:
   3. 1f00              64 mtdblock0  (driver?)
   4. No filesystem could mount root, tried:  jffs2

Of course jffs2/ext3 no difference.



My idea was that there were missing drivers for ext3, but they are build in
kernel (*file.png).

I attach whole log (close.txt) if some more info is needed, can provide
more accurate answers.

In log there is line:

*Kernel command line: noinitrd console=ttymxc0,115200 root=/dev/mtdblock0
rw rootfstype=jffs2 ip=off*

but changing for:
*Kernel command line: noinitrd
console=ttymxc0,115200 root=/dev/mmcblk0p2 rw rootfstype=ext3 ip=off*

Give same resoult as posted above: "Kernel panic - not syncing: VFS: Unable
to mount root fs on unknown-block(0,0)"


Any ideas? Hint? Any help will be great

Pozdrawiam,
Paweł Krzyżanowski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20151127/a26438dd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: close.txt.zip
Type: application/zip
Size: 4868 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20151127/a26438dd/attachment.zip>