I am looking to find a reson for my kernel (8.02 build) is not to be able to boot. It seems that it is not able to mount the rootfs.
Custom device very similar to bbb.
Here's a part of the console when booting:
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.
I am looking to find a reson for my kernel (8.02 build) is not to be able to boot. It seems that it is not able to mount the rootfs.
Custom device very similar to bbb.
Here's a part of the console when booting:
Hi Thomas,
Do you have SD card on MMC1 and eMMC on MMC2? If so,
[ 3.233934] mmc1: SDHCI controller on 481d8000.mmc [481d8000.mmc] using External DMA
[ 3.360265] mmc1: new high speed MMC card at address 0001[ 3.386622] mmcblk1: mmc1:0001 4FTE4R 3.64 GiB[ 3.391483] mmcblk1boot0: mmc1:0001 4FTE4R partition 1 4.00 MiB[ 3.414987] mmcblk1boot1: mmc1:0001 4FTE4R partition 2 4.00 MiB[ 3.430725] mmcblk1rpmb: mmc1:0001 4FTE4R partition 3 512 KiB, chardev (243:0)
This seems to be the enumeration for the eMMC.
[ 3.532388] mmc0: SDHCI controller on 48060000.mmc [48060000.mmc] using External DMA[ 3.554064] sdhci-omap: sdhci_omap_probe result success 0[ 3.554720] Waiting for root device PARTUUID=3d292a74-02...
and the sdcard is not detected.
You can try to disable eMMC node in kernel device tree first, that probably would make the kernel log cleaner. Then you can enable eMMC later after you got the sdcard working.
I have disabled the emmc in the device tree. Here are the relevant trace with unrelated stuff removed:
[ 2.907375] sdhci: Secure Digital Host Controller Interface driver
[ 2.913634] sdhci: Copyright(c) Pierre Ossman
[ 2.919246] sdhci-pltfm: SDHCI platform and OF driver helper
[ 3.072160] omap_voltage_late_init: Voltage driver support not added
[ 3.083123] sdhci-omap: sdhci_omap_probe result error -517
[ 3.107697] OMAP GPIO hardware version 0.1
For periferials there is the issue of indexing from 0 or 1... Looking at the pinmux, it has 0 indexing and in that case I have:
SD card on the MMC0 (mmc1)
Pinmux
&mmc1 {
eMMC on MMC1 (mmc2)
Pinmux:
On an older revision of the board, I can boot the SD-card. The same sd-card will have the same output except after the
Waiting for root device...
I get (first 3 lines are something I have added):
PROLON: mmc_attach_sd() called
PROLON: mmc_attach_sd() calling mmc_attach_bus
PROLON: mmc_attach_sd() result ocr_avail_sd 3145728
mmc0: new high speed SDHC card at address 0007
mmcblk0: mmc0:0007 SD16G 14.5 GiB
mmcblk0: p1 p2
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 1024K
Run /sbin/init as init process
What could be the reasone that mmc_attach_sd() is not called on my new target. The SD-card device tree and pin connections are the same!
As far as I am aware the difference between the two board revisions is that the new board is mounted with a differend DRAM, could this really be causing the issue?
I have two boards from different productions. The circuit design is compleatly identical but the new boards are not able to boot from sd-card and hangs waiting for root device as described above.
I have a few differences in components. Could this be related to the DRAM?
OLD (OK) | NEW (STOPS) | |
CPU | AM3352-1000 | AM3354-800 |
PMIC | TSP65217C | TSP65217C |
DRAM |
AS4C256M16D3LB-12BCN
|
K4B4G1646E-BYK0
|