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.

TDA2SX: MMC init failed when I run early boot late attach usecase in VSDK 3.7 Linux

Part Number: TDA2SX

Hi,

As title, I follow https://e2e.ti.com/support/processors-group/processors/f/processors-forum/959989/faq-compiler-tda2e-the-steps-to-enable-the-early-boot-late-attach-use-case-in-vision-sdk-3-7-linux and run the usecase in my custom board, and get error message as following:


U-Boot SPL 2016.05-00008-g1fbee98 (Oct 04 2022 - 10:43:57)
DRA752-GP ES2.0
no pinctrl for hs200_1_8v
no pinctrl for ddr_1_8v
Card did not respond to voltage select!
*** Warning - MMC init failed, using default environment

Trying to boot from MMC1
reading dra7-ipu2-fw.lzop
reading dra7-dsp1-fw.lzop
reading dra7-dsp2-fw.lzop
reading dra7-ipu1-fw.lzop
spl_load_file_fat: error reading file dra7-ipu1-fw.lzop, err - -1
spl: error reading image dra7-ipu1-fw.lzop, err - -1
Error loading remotecore IPU1!,Continuing with boot ...
Card did not respond to voltage select!
*** Warning - MMC init failed, using default environment

reading u-boot.img
spl_load_image_fat: error reading image u-boot.img, err - -1
Card did not respond to voltage select!
*** Warning - MMC init failed, using default environment

Failed to mount ext2 filesystem...
spl_load_image_ext: ext4fs mount err - 0

What's happened?

It is custom board, and it only uses one jump to switch SD/QSPI Boot Mode. I think it may set the wrong mode. Is it possible?

And can I set to SD Boot mode by software?

Thanks.

BR,

Jeff