All, I'm working with MX6Q for one project, now what I encountered is MX6Q can't boot from SD card directly, does anyone has success experience and share with us? thx
If you configure the hardware boot mode pins / fuses correctly, you should be able to boot directly from SD card.
I guess you're on a Boundary Devices Sabrelite board? In that case take a look here:
Not sure if fuses can be permanently blown on this device? Haven't come to those details yet...
To my understanding, on a SabreLite the fuses can't be blown any more because they are already blown to boot from SPI NOR. Therefore the workaround in the above link.
Thomas and Dirk are right (of course).
There are some other notes in this blog post about running Linaro on Sabre Lite and Nitrogen6X.
Thanks for Eric and Drik comment.
Now the system can read card information, and run Uboot on SD card, but it seem system can't recognize SD card, so that I can't configure system ENV, detail as below:
Could anyone help indicate where happened wrong with it? thanks
About above message, when I insert SD card into SD card socket, system will indicate it hasn't found SD card in the corresponding socket, I wonder maybe somewhere I make the logic by mistake, does anyone have the experience and share with me please? thx
We met this issue too when I tried to boot directly from sd card. What we did is change is chaning all mmcblk0 into mmcblk1 in device/fsl/imx/sabresd/init.rd, and change u-boot bootcmd into 'booti mmc2' instead of 'booti mmc3'
Good job! One thing you should know is that the boot param in u-boot is only for FSL reference board . If board hardware design change , of course, you should modify the boot param in u-boot. Firstly, you should choose the wright boot mode pins to boot from the device what you want. Secondly, you should make sure what boot param is the right one. You can type "mmc dev x" and "mmcinfo" in u-boot to get more information ,then use "mmc read" from the SD device and use "md" to look the content in the SD device whether is the right one which contain the kernel image. Now you can know which device you should choose. At last, you should modify the boot param in u-boot to make kernel can mount the right rootfs on mmcblk*.
Retrieving data ...