Hi,
Kernel configuration does not have Curiosity board config 64MB RAM, so I build sdcard image for SAM9X60 EK board 128MB RAM, because CPU configuration are same (hopefully).
SAM9X60-EK board BOOT successfully but when I try booting SAM9X60-Curiosity, process hangs on:
[ 1.266405] NET: Registered PF_PACKET protocol family
[ 1.271527] 8021q: 802.1Q VLAN Support v1.8
[ 1.311405] mmc0: SDHCI controller on 80000000.sdio-host [80000000.sdio-host] using ADMA
[ 1.320507] Waiting for root device /dev/mmcblk0p2...
[ 129.492953] random: crng init done
Full boot log in winmerge report format
Looks like /dev/mmcblk0xxx device detected in both boards, but unable to mount on Curiosity board.
Can this be a RAM size problem?
Can you please point me, where I must dig?
Thank you
(Should be moved to dev section of forum)
You left the crucial clue behind link, next time post full bootlog. The SD card is not detected properly according to boot log. Compare &sdmmc nodes of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/at91-sam9x60_curiosity.dts with https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/at91-sam9x60ek.dts. You'll see that card detection is on different GPIO for &sdmmc0, while 60EK board has eMMC on &sdmmc1, Your board probably exposes those signals as pins.
To go further use proper dts for Curiosity board. The at91 boards seem to have common boot procedure so adding it shouldn't be difficult. Check https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/at91/image/sam9x.mk and https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/at91/image/uboot-env.txt where to add the board, and You'll need to add board dts to https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=target/linux/at91/files/arch/arm/boot/dts directory.
1 Like