i.mx6 sometimes goes to serial downloader

[ivan_113]

Custom board.

Normally boot from emmc, but sometimes goes to USB downloader.

Normal boot log:

Normal boot log

Failed boot log:

Failed boot log

Difference in entry #19: Jump to the boot image or Jump to the SDP

upd: this problem appears with boot from eMCC and SD too

Sometimes boot fails with following log:

Failed 2

[ivan_113 · Accepted solution]

Thanks to all.

Reset of MMDC before loading u-boot fixed the problem.

[ivan_113]

Hi. Thank for reply.

We have several versions of HW. On earlier versions it's all right. On current version was changed emmc and ddr. However, in case of load from SD errors occurs, problem may be in ddr. Stress test passing.

Previous ddr is EDB8132B4PM-1D-F-D

Current ddr is AS4C128M32MD2A-18BIN

Configuration in DCD are made

[Harvey021]

This kind of problem that sometimes starts normally and sometimes is not normal needs to be considered when doing ddr calibration first. I forgot to mention it earlier. 

@Mestkim  thanks for bringing up, you are correct.

Best regards

Harvey

[Mestkim]

• If the board hardware is set to use internal ring oscillate as you mentioned, it could not be the ERR009678.

• If you believe it could be ddr issue, you can check if you have finished the mass production  ddr stress test for i.MX6Solox and for this lot of the boards you made. 

  But still suggest to monitor the power ramping up of emmc and sdcard. 

• Several years ago, I followed this document for mass production ddr stress test.  The document is to find a smallest window of ddr configuration to fit all the boards of a lot. 

i.MX6 DDR calibration/stress for Mass Production
https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX6-DDR-calibration-stress-for-Mass-Pr...

[Mestkim]

It could be  ERR009678 ROM: SD/EMMC/NAND prematurely times out during boot. 

And also suggest you to check the power sequence including emmc power on timing. 

[ivan_113]

32kHz crystal is removed and RTC_XTALI connected to GND

[Harvey021]

Hi @ivan_113 

The problem caused can be various.

Does this issue happen same image? 

From ROM log, which seems telling the address in the signature is invalid, you can dump HAB log then share the HAB event.

If not the case above, what BSP you are using, it'd be better to share your schematics to (harvey.yu_1@nxp.com) me for further troubleshooting.

Best regards

Harvey

[Mestkim]

NXP expert,

"The problem caused can be various."  In fact, it cannot be HAB issue in those "various".

The log shows it is an open device.  Dump HAB log and share the HAB event of an open device? For what? 

Here is a description in reference manual. 

If it is an open device, it always gets authenticated error because "All HAB functions are executed as for a closed device." 

On the contrary, what you said "telling the address in the signature is invalid" is a normal ROM log. 

Is there any misunderstanding below?