Problems due to different device revision numbers of MK60DN512ZVMD10

[K60_TTC]

Hello,

We use the MK60DN512ZVMD10 MCU for one of our projects, with the last device revision number (5N22D). But due to the lack of pieces, some months ago we bought some of them with another revision number (4N22D).

The problem is that the binary of the 5N22D doesn't work in 4N22D and I don't know why. Is it related with the ABI passed to the compiler? How could I compile the sources to get a binary compatible with the 4N22D?

Thanks in advance and best regards,

Bonifacio Romero

[vicentegomez]

The difference is the mask set, but you should be able to load the code from the  5N22D on the  4N22D, maybe some errata are present on the 4N22D and makes the product will fail, but you should be able to program it.

Where did you buy those parts?

[K60_TTC]

Hello Vicente

Thanks for your reply.

Well, I can load the code into the MCU, but the problem is that the binary doesn't work properly. It starts  booting but stops and doesn't continue with the rest of tasks, so maybe there is a HW error. My question is because I know that, on some processors, the silicon revision is a parameter to the compiler, which implements some workarounds for the existing problems in older HW versions, but I don't know if this is the case.

We bought a batch of 300 MCU with 4N22D mask in China because the recent months we haven't found parts in Europe or US and cannot stop manufacturing our equipment.

Best regards,

Bonifacio Romero

[vicentegomez]

you can find the errata on these links

https://www.nxp.com/docs/en/errata/KINETIS_5N22D.pdf

https://www.nxp.com/docs/en/errata/KINETIS_4N22D.pdf

Regards