Hai,
We have designed custom board as a refernce by sabre sd dual lite.
I am using MFG tool for loading images.
The buit customized images U boot,U Image and rootfs loaded successfully into EMMC card usinf MFG tool when I configured board name in cfg.ini file with i.MX6DL-SABRESD_eMMC
But no UART messages while booting from EMMC.
We have used EMMC as SDIN7DU2-8G,instaed of sabre MTFC8GLCDM emmc.
I have set BT_CFG pins properly.
IS there any changed need to made form booting and read images from EMMC card?
Please let me know anyone know this problem.and kindly reply with some suggestions ASAP.
Maybe you need to enable the boot partition.
Please check how I did this on a imx6sl-warp board:
Hi ss
MTFC8GLCDM is eMMC 4.51, but it should boot well without additional
changes. Note, board layout and drive strength may affect signal quality,
which causes boot failures. For example one can look at below link
eMMC 8GB to 4GB - crash on linux (yocto) boot
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
hi,
Thanks for immediate response.
The pin configuration and io mux pins connections signal strength all are matching,there is no changes in hardware wise.
Please let me know what are other things i need to observe...
thanks
you can test signals with oscilloscope and data analyzer
to check where emmc communication stops and check
boot configuration in SBMR1,2 register connecting to processor
with jtag.
~igor
hai,
Actually I can able to write the images and able to read images also .
But runtime env variables also not loading to EMMC failing error: no MMC present.
And board not able to boot automatically when i switch to internal boot.
yes you can be able to write the images and able to read images
in mfg tools and linux, because they use different pad settings then when
device boots. Please read once more time suggested link in first reply.
Also you can start to debug it with testing signals with oscilloscope and data analyzer
to check where emmc communication stops and check
boot configuration in SBMR1,2 register connecting to processor
with jtag.
~igor
ok fine,I will check it once again.
Thank you
hi,
In that its mentioned solution for Linux boot,but for my board its not at all booting uboot also.....
when board stops please connect jtag debugger
and check boot configuration in SBMR1,2 registers.
Had you checked emmc signals with oscilloscope, are they OK ?