This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM3730 with eMMC boot issue

Other Parts Discussed in Thread: DM3730

Hi,

We have our hardware platform losely based on Beagle XM but massively cutdown, its has a Toshiba eMMC device (2GB) on MMC1, this is intened to act as the boot device.

We are doing a sector wise copy from an micro SD card to the eMMC, the SD card image is built using the DVSDK 4.02.00.06 and is tested on a Beagle XM and the same hardware with a SD card socket hardwired in place of the eMMC device, in both cases a successfully boot it achieved up to the linux prompt.

When we boot from the eMMC xload and uboot do the right thing and the kernel starts, when it gets to mount the file system from the second partition the device recognised as an MMC and the size is reported correctly. However thats it, it hangs at this point and never recovers.

We are currently adding printks to all the affected drivers but the methdo we have to use to clone the image onto the eMMC is very slow, so any help offered gratefully recieved.

Anyone else succesfully using eMMC to boot a DM3730?

David

  • We have now tested this further using a standalone MMC card and Begale card, we get exactly the same issue, the MMC card will not mount as a file system and the kernel hangs at that point. 

    As we have the issue with both our hardware and the Beagle hardware we assuem the problem is either the devic eor the driver, the beagle has a OM3530 so its a different chip suggetsign a basic drive issue.

    Can anyone at TI confirm whether the MMC has been tested with the 4.x series of DVSDK releases?

  • Meant to post  the snippet from the boot log, as follows

    [   25.657836] List of all partitions:
    [ 25.661437] b300 1966080 mmcblk0 driver: mmcblk
    [ 25.666717] b301 40131 mmcblk0p1
    [ 25.671081] b302 1919767 mmcblk0p2
    [ 25.675415] No filesystem could mount root, tried: ext3 ext2 ext4 squashfs vfat msdos
    [ 25.683502] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)