i.MX6ULL eMMC Flash and Boot

[ET_Dev]

We have made a custom board with i.MX6ULL EVK and specifically the CM module of the EVK as reference. On our board we have a QSPI Memory (same MPN as the EVK CM) and a eMMC (THGBMUG6C1LBAIL). 

When we try to flash the Linux Image (LF_v6.6.36-2.1.0_images_IMX6UL7D.zip) using UUU, it looks like the U-Boot is being flashed, but not the Linux Image, and then it goes into a continuous loop. 

On the same board we are able to flash to QSPI using mfgtools and a baremetal sdk example "hello world" and the same is running fine on the QSPI. 

Any pointers on what should be done to resolve this will be great. 

[ET_Dev · Accepted solution]

To anyone following this, or facing similar issues, we found out that our issue was that UBoot was crashing and hence the USB error and connected issues. 

The Uboot crashing in turn was because the EVK DTS was configured for Ethernet PHY addresses in a particular way and we had them wired in a different way on our custom board. Once we resolved the Ethernet PHY address issue and changed as per the EVK, the UBoot crash stopped and we were able to flash the eMMC.

[Chavira]

Hi @ET_Dev!

Thank you for contacting NXP Support!

The LF_v6.6.36-2.1.0_images_IMX6UL7D.zip is only for our boards.

If you want to boot your board you have to customize our BSP according to your board.

You can refer to our PORTING GUIDE to port our BSP to your board.

Best Regards!

Chavira

[ET_Dev]

Hello Chavira

Thanks for looking at this. I understand that the image is for NXP boards, I read the same on other posts as well. 

However, in this case we have followed and replicated the EVK schematic as it is, with the only exception of populating a eMMC which is not populated on the EVK CM.

Do you think even in this case the NXP image will not work?

[Chavira]

Hi @ET_Dev!

Yes, you have to adapt some things like ddr timing, etc.

Maybe you don't have to adapt all the BSP but is necessary to adapt according to your hardware.

Best Regards!

Chavira