MK22FN512VLL12 wafer changes and performance differences

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

MK22FN512VLL12 wafer changes and performance differences

1,458 Views
jiangzz
Contributor II

The new batch of materials cannot accept the boot loader. Their silk screen marking is XE (batch 2019). I took the parts we could accept the boot loader normally (silk screen marking is PK, batch 2021) to compare. X-ray is as the attachment.

Please help me confirm whether they have changed the wafer. If so, what has changed between them? Is the ID the same?

[6FZ2F_MO}62}TL`]_WX(M2.png

picture 1

XIJ`)RAPQQVH2OSAIHKBR`G.png

picture 2 

F]$3A$JVT@@8_ZB[4X(]_}Y.png

 picture 3

_DNG$@)9VBY2T)949(R%(49.png

 picture 4

O_`%2}C76T[%%IDWKQ~19FX.png

picture 5

0 Kudos
Reply
8 Replies

1,442 Views
ErichStyger
Senior Contributor V

Because to me you have a different PCB, I would first check that part. Other than that, I have a list of check points here: https://mcuoneclipse.com/2014/11/03/debugging-failure-check-list-and-hints/

I hope this helps,

Erich

0 Kudos
Reply

1,426 Views
jiangzz
Contributor II

Our problem is that we can't accept the boot loader

XD3)S9`51WG6W}V18J_}WW4.png

`]K$})51K73H2@DV]W2G_[Q.png

The last picture in the second picture is as follows:

K61DK_R%{}{W2IRQJZ0NUXI.png

 As you can see, when accept the boot loader for the faulty chip (the silk screen is AE), his RST is faulty.

  The one in the upper left corner of the figure below.

[KK]E{X)K7T@OVNV6MAYN9U.png

We mainly want to know whether the firmware burned by these two different silk screen printed chips is consistent when they leave the factory, and whether the hardware design around them is consistent. Otherwise, according to our understanding, they will not be unable accept the boot loader.

0 Kudos
Reply

1,408 Views
vicentegomez
NXP TechSupport
NXP TechSupport

Sorry maybe you have a counterfeit part

 

Where did you buy your part?

 

Regards

 

0 Kudos
Reply

1,383 Views
jiangzz
Contributor II

This reply is missing, but he said that the Xe is an engineering sample version. He didn't look at my problem carefully. We cannot accept the boot loader. Its silk screen is AE (xnae1935u). The silk screen of the chip that can accept the boot loader is PK (xnpk2144u). This chip was launched in 2014. Its chip shows that it has a date code, 1935 means 35 weeks in 2019. It will be a mass production version by 2019, Where is the theory of engineering first run samples version?@bobpaddock .

333.png

0 Kudos
Reply

1,375 Views
bobpaddock
Senior Contributor III

Which is why I deleted my reply when I realized my error.
It is part numbers that start with X or have a prefix of X.
Not part numbers that have X in some other place.

1,377 Views
troelsoesteraa
Contributor III

Hi,
I think Bob is incorrect.
NXP doesn't actually want to disclose much of what the last line means, but luckily Mouser still stores an old PCN with some information:

https://www.mouser.com/PCN/Freescale_16780.pdf

Items starting with Q are assembled and tested at site in Kuala Lumpur, Malaysia
Items starting with XN are assembled and tested at Fujitsu-Nantong, China.
Wafer identifiers/lot code is AE or PK.

The first prototype Kinetis processors where pre-fixed by P instead of M. That's why some of the first prototypes were called e.g. PK22FN512VLL12, but they're from 2013/14 and long since gone.

0 Kudos
Reply

1,453 Views
ErichStyger
Senior Contributor V

The new batch of materials cannot accept the boot loader.

I'm not sure what you mean with this. What is the problem? Are you not able to debug it?

As for your pictures: they are interesting, mostly they show a different PCB underneath with different traces/vias. And you see the packaging pins/leads/traces, but not the silicon itself with details.

As for the marking /differences: have you already checked the errata/version/marking information if it is indeed a different silicon revision or just a a different packaging series?

Erich

0 Kudos
Reply

1,449 Views
jiangzz
Contributor II

Yes, we can't debug it.

0 Kudos
Reply