MK24F replaces MK64F problem

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

MK24F replaces MK64F problem

ソリューションへジャンプ
1,058件の閲覧回数
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 件の賞賛
返信
1 解決策
1,041件の閲覧回数
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 件の賞賛
返信
1 返信
1,042件の閲覧回数
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 件の賞賛
返信