K25Z Migration to K32L2B

cancel
Showing results for 
Search instead for 
Did you mean: 

K25Z Migration to K32L2B

Jump to solution
632 Views
pedrobotelho15
Contributor II

Hi folks.

I would like to migrate from FRDM-KL25Z to FRDM-K32L2B3, but I'm not sure what the differences are.

From what I've seen they are very similar, with some specific differences, such as: the K32L is from 2019, while the KL25Z is from 2012, the K32L's I2C driver is a little different (and more problematic), etc...

But what are all the changes? Thanks in advance.

0 Kudos
1 Solution
612 Views
jay_heng
NXP Employee
NXP Employee

From peripheral point of view, KL25 is quiet different from K32L. As most of KL25 peripheral registers are 8bit width while K32L peripheral registers are 32bit.

So the peripheral is different, It is I2C in KL25 while LPI2C in K32L.

K32L is much similar to KL03/KL43/KL27 parts.

 

View solution in original post

4 Replies
563 Views
bobpaddock
Senior Contributor III

App notes for the KL28 will be helpful, as the KL28 is closest to the K32L in function for LPCI2C.

0 Kudos
610 Views
jay_heng
NXP Employee
NXP Employee

If your application is based on MCUXpresso SDK, then migration thing will be easy.

The same type peripheral driver APIs are almost the same, for example the I2C driver API is similar to LPI2C driver API

613 Views
jay_heng
NXP Employee
NXP Employee

From peripheral point of view, KL25 is quiet different from K32L. As most of KL25 peripheral registers are 8bit width while K32L peripheral registers are 32bit.

So the peripheral is different, It is I2C in KL25 while LPI2C in K32L.

K32L is much similar to KL03/KL43/KL27 parts.

 

604 Views
pedrobotelho15
Contributor II

Oh, I get it. I thought all of KL25Z peripheral registers where 32-bits as well.

0 Kudos