MK24F replaces MK64F problem

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

MK24F replaces MK64F problem

Jump to solution
500 Views
chhsu0229
Contributor II

We have worked on MK64F a while and his application has sold a lot of product.

Unfortunately, MK64F is out of stock, My company has a plan that MK24F replaces MK64F.

MK24F is pin compatible with MK64F, therefore, it can be replace on hardware.

Regarding the software, can we program the code (firmware) without any modifying that has developed on MK64F to MK24F directly?

Thanks

0 Kudos
1 Solution
483 Views
victorjimenez
NXP TechSupport
NXP TechSupport

Hello, 

First, it would be important to mention that for the migration to be a drop-in replacement, you need that both MCUs are the same package. 

Regarding the software, you cannot flash the firmware of the K64 into the K24. There are some changes between these two families that won't allow this to work. For starters, the frequency of the clocks. It's more common for customers to migrate from the K20 family to the K60. In your case that you will do the opposite, you have to pay attention to the peripherals that your application is currently using. This is because the K60 family has more peripherals than the K20. Just to put an example, if your application right now is using Ethernet, it won't be possible to migrate to the K20 due to the lack of Ethernet on this family. 

Regards,
Victor 

View solution in original post

0 Kudos
1 Reply
484 Views
victorjimenez
NXP TechSupport
NXP TechSupport

Hello, 

First, it would be important to mention that for the migration to be a drop-in replacement, you need that both MCUs are the same package. 

Regarding the software, you cannot flash the firmware of the K64 into the K24. There are some changes between these two families that won't allow this to work. For starters, the frequency of the clocks. It's more common for customers to migrate from the K20 family to the K60. In your case that you will do the opposite, you have to pay attention to the peripherals that your application is currently using. This is because the K60 family has more peripherals than the K20. Just to put an example, if your application right now is using Ethernet, it won't be possible to migrate to the K20 due to the lack of Ethernet on this family. 

Regards,
Victor 

0 Kudos