Problem of chip boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem of chip boot

960 Views
jhp
Contributor II

I produced 90 pieces of boards in batch, of which 87 had problems and 3 were normal. The problematic CPU is :MCIMX6D5EYM10AD   Notice this:QAM1535   but 3 pieces of good CPU MARK :QAM1646.

87 pieces can be downloaded normally, but can't start。 There is no data in the serial port。The appendage is the normal boot and the abnormal boot information。3 pieces of good board are normal 。Is there a difference in the curing of the guide ROM?Can you tell me how to deal with it?The boot mode of the board is eMMC, and the peripheral CFG bits are all normal。

0 Kudos
7 Replies

821 Views
jhp
Contributor II

Thank you for your reply. I and my team have been working hard to find the problem, and finally found that the 87 CPU BT_FUSE_SEL Value bits that have a problem have been set 1,ONLY BOOT FROM eFUSEs SETTING, such as Figure 1. Figure 2 is what we tried to modify, but it was not successful. Looking for similar information on the Internet, people give the conclusion that they can only burn and write once and can't be modified. The actual test is true. Can you tell me a clear statement? Is there a way to unlock the status?

bit_fuse.pngBIT2.png

0 Kudos

821 Views
Yuri
NXP Employee
NXP Employee

Hello,

  The fuses are really once programmed. 

Regards,

Yuri.

821 Views
jhp
Contributor II

One thing that does not understand is why the purchase of CPU has such a problem, is it a custom version of a new product that has been used or a custom version of a NXP original large customer? I don't know if there is any of the latter. At present, the positioning is the problem of CPU incoming material.

0 Kudos

821 Views
Yuri
NXP Employee
NXP Employee

Hello,

   Generally, violation of  i.MX6 specs, provided in Datasheet(s), may cause improper

fuse burning, but I never heard about it before. Perhaps it makes sense to check the issue

with distributor.    

Regards,

Yuri.

821 Views
jhp
Contributor II

Ok,I see.Thanks a lot.

0 Kudos

821 Views
jhp
Contributor II

Thank you for your reply. We have changed the new batch of CPU to solve this problem. Thank you very much!

0 Kudos

821 Views
Yuri
NXP Employee
NXP Employee

Hello,

 

  Have You tried the DDR Stress test ?

 

https://community.nxp.com/docs/DOC-105652 

 

  Also, You may run the Stress test just after boot crash in order

to check boot options, shown in test log as SRC_SBMR1 and

SRC_SBMR2 registers).

Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos