KL27Z Migration to KL28Z

[benwang]

NXP support,

     Our company has a product line used MKL27Z as the system platform. Recently we find the MCU memories are almost used up, so we plan to replace the KL27Z with KL28Z. Though the "naming" of two chips are very similar, but after our investigation, we find they are not pin-to-pin compatible. And there are also many IP levels changes. E.g. SPI->LPSPI, I2C->LPI2C, MCGlite-> SCG, etc.

1) Do we have a migration guide or Application note about how to migrate from KL27Z to KL28Z. We want to know every details of the silicon IP levels changes.

2) Regarding the software SDK version built for KL2x. We used the NXP web tool SDK builder to get the latest SDK packages on TWR orFRDM. We find the latest for KL27Z is SDK_2.7.0, but the latest for KL28Z is SDK_2.5.0, so SDK 2.7.0 for KL28Z is still under development? If so, when will it be released public? 

Thanks!

[benwang]

Thanks a lot for Mark's reply about the IP comparison between KL27Z and KL28Z.

According to my 2nd question, currently our product are using the SDK 2.7 version for KL27. But on the SDK builder, I can only download the latest package of SDK 2.5 for KL28Z. Why? It it still under development? When we migrate the project, we also want to make the software package on the same page. Thanks!

[Alexis_A]

Hello Ben,

For the KL28 there were not new revisions of this software until now, in case there's a new software you will be notified if you previously download some version of the same software.

Best Regards,

Alexis Andalon

[benwang]

Thanks Alexis .Do you know the SDK release plan/date for KL28Z SDK 2.7.0 ? We are going to do product migration from KL27Z to KL28Z?

[Alexis_A]

Hello ben,

Unfortunately, until now there's not any news about a new version of this SDK so the latest one is the V 2.5.

Sorry for the inconvenience this may cause you.

Best Regards,

Alexis

[bobpaddock]

Look at the K32L2A4S for bigger memory in a compatible footprint to the KL27.

[mjbcswitzerland]

Hi

I haven't included "additional" features in the KL28 over the KL27 but here is a general list of the changes to peripherals that need to be respected:
- peripheral clock control is using a new module called PCC (rather than the SIM)
- WDOG32 instead of COP
- Clock module is SCG rather than MCG_LITE
- INTMUX module - this may or may not be needed, depending on which interrupts are presently used
- All UARTs are LPUARTs
- I2c -> LPI2C
- PIT -> LPIT
- SPI - > LPSPI
- DMA -> eDMA

In case of migration difficulties you can also consider the following strategy:

Use the uTasker project (it is also available as open source if no support is needed) to put your original project into - it also allows simulating the KL27 for accurate testing.
Then you can change KL27 to KL28 in its project setting and it will then automatically run on a KL28 (you will need to also redefine which pins your I/O are on since it is not pin-compatible).

This will then future proof your product since you can change it to almost any other Kinetis needed without re-design work by selecting the appropriate processor.

In addition this includes being able to run your original application on faster iMX RT parts by selecting an i.MX RT part (and defining where the I/Os are to be placed there). The i.MX RT capabilities are presently not available in the open source version but this may be added later. For professional work it is available already.

Regards

Mark
[uTasker project developer for Kinetis and i.MX RT]

KL27->KL28 migration training or consulting is also available if urgent requirements exist

[bobpaddock]

Mark, did NXP ever address your KL28 I2C questions? 

Never saw an answer in that thread from them.
More or less broken than the KL27 I2C?

Done anything with the K32L2A4S to know how broken it is in any ways?
I'm just moving it now. 

Some of the things in the erratas don't give me the warm fuzzies.

[mjbcswitzerland]

Bob

I have no new information on this - same stand as yourself.

I haven't used the K32L range (yet) - I may do so (the FRDM-K32L2B3 and FRDM-K32L3A6 are on my 'to order' list for when I am next buying parts) but my main focus is now on i.MX RT work seeing that the Kinetis range is stagnating and coming to end of design-in life.

The i.MX RT parts use the same LPI2C module as used by the KL28 - its workarounds seem to be stable since I know of no issues in user's products at the moment.

Regards

Mark

[uTasker project developer for Kinetis and i.MX RT]

[bobpaddock]

Mark Butcher wrote:

I have no new information on this - same stand as yourself.

I haven't used the K32L range (yet) - I may do so (the FRDM-K32L2B3 and FRDM-K32L3A6 are on my 'to order' list for when I am next buying parts) but my main focus is now on i.MX RT work seeing that the Kinetis range is stagnating and coming to end of design-in life.

The i.MX RT parts use the same LPI2C module as used by the KL28 - its workarounds seem to be stable since I know of no issues in user's products at the moment.

Other than maintaining my existing product line I will NEVER use any Kinetis part.
Been nothing other than a nightmare experience for me; and I've been doing this work for  LONG time...
So I certainly understand wanting to flee for any other family.

I'm even questioning the wisdom of moving to some LPC parts from the support I've seen here.

Take the other messages in this thread for example.  KL28 has been around for a couple of years

and it is still unsupported by the latest tool set and no one knows if it ever will be. 

As well as the question of the KL28 I2C issue being unaddressed after months of waiting for a response.

Then part problems like the broken I2C of the KL27 are never fixed or even officially acknowledged in a errata, just in some obscure migration guide that few know exist.

I don't like the alphabet soup issues with the K32L either.  Different pin-outs, different feature sets another confusing mess...
The 2A family is pin compatible with at least some,  if not all of the KL27 family, with double the memory, and hopefully working I2C (the erratas don't give me the warm fuzzies for that).

This place has issues.  :-(