MCU bootloader for MK02FN64

[scottm]

I'm trying to find the MCU bootloader code for the MK02FN64 and I'm so confused. First, whose brilliant idea was it to rename KBOOT to MCUBOOT when the mcu-tools MCUboot project already existed? It certainly doesn't make it easy to google anything.

The MBOOTDEMOUG user's guide says where to find demo applications, but they don't exist in any of the SDK packages I've got. I went back to the SDK builder to rebuild the MK02FN64 SDK since it said there was an update available - and got a warning because "MCU Boot" has apparently been removed from the update.

So before I chase my tail any more or spend a lot of time reinventing the wheel, can someone give me a straight answer on where to find bootloader examples for the MK02FN64, or at least the FRDMK22F, since the MK02 doesn't seem to have any development board of its own?

Thanks,

Scott

[Joey_z]

Hi,scottm

Sorry for the late reply.

The KBOOT for Kinetis was renamed to MCUboot. You can refor to this link: MCU Bootloader | NXP Semiconductors , and the following attached picture to find the MCU Bootloader for NXP Microcontrollers.

BR

Joey

[scottm]

Hi Joey,

The download link appears to be broken. See the attached screenshot.

Thanks,

Scott

[Joey_z]

hi，scottm

Are you logged into the NXP website? Please log in and try again.

https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools...

BR

Joey

[scottm]

That time, your link just sent my browser into an endless refresh cycle. I had to close it and start over, log out of everything and log back in, and it works now. I already had that file, though. The problem is that the bootloader example doesn't seem to exist as described in the user's guide, even after building the FRDMK64F SDK from scratch. Please see the attached screenshots.

Thanks,

Scott

[Joey_z]

hi，scottm

Thank you for your reply.

Which version of the SDK are you using? I have different content compared to yours as shown in the following picture. In addition, could you use the bootloader in the targets folder from the link to download file?

BR

Joey

[scottm]

That's version 2.11.0. The package was built 2/21/2025.

As for what's in the download, can you tell me which target applies to the MK02FN128? The target names are things like "MK02F12810" and I've never been able to find a master list that maps those part numbers to the orderable part numbers. We're apparently supposed to know them but I'm not sure where we're supposed to get that information from.

Also it only seems to have projects for IAR, KDS, and MDK - no MCUX.

Scott

[Joey_z]

hi,scottm

Thank you for your reply.

According to download,  it only have projects for IAR, KDS, and MDK - no MCUX, I think the reason is the time. The "MK02F12810" should be used in your case, You can try it using the IDE be supported.

BR

Joey

[scottm]

The "MK02F12810" should be used in your case

Where do I find the list of what datasheet part number goes with what orderable part? How do I know which parts are "MK02F12810"? This comes up frequently and it's frustrating to not be able to find these part numbers.

You can try it using the IDE be supported.

That didn't quite make sense grammatically. Can you explain what you mean? Are you saying to use one of the supported IDEs? Because I thought KDS was no longer supported, and buying a $4500 IDE license just for the sake of a demo isn't really an option.

I just want to know how to get to the SDK example as shown in the manual. Also, why is MCU Boot no longer an option in the MK02FN64 SDK when it was previously? Is the bootloader deprecated?

Thanks,

Scott

[Joey_z]

hi,scottm

Thank you for your reply.
I'm sorry I didn't consider your IDE license problem, we have no K02 chip development board, but FRDM K22F support K22 and K02, release of bootloader support FRDM - K22F is pointed out in the note, here you can find accessories in the picture . You can download the SDK of FRDM-K22F to support K02. Attached is a picture of its bootloader.

Hope it can help you.

BR

Joey

[scottm]

Hi Joey,

Let's break this down into separate questions to make things more clear.

1. Where do I find the list of part number mappings, for example to see which part numbers are covered by "MK02F12810", or to find out what the number would be for an MK22FN1M0?

2. Is MCU Boot no longer supported for the K02 in the MCUX SDK? It was an option in previous versions but no longer shows up.

3. Where can I find ANY example of MCU Boot, for any Kinetis device or dev board, using MCUX?

4. If you're recommending the "Freedom Bootloader" and it's not the same thing as MCU Boot, can you direct me to the documentation for the Freedom Bootloader?

Thanks,

Scott

[Joey_z]

hi，scottm

Thank you for your reply.

1. You can download the following documents, which have a part number related to the K series. Document download link:

Product Numbering Information

Kinetis K22F 120 MHz Family Mask Sets and Revision Numbers

2. You can refer to the SDK package for K22, which is recommended.

3-4. You can refer to the links below to find some information.

Getting Started with the MCU Bootloader for NXP microcontrollers | NXP Semiconductors

MCU Bootloader Demo Applications User's Guide

BR

Joey

[scottm]

Hi Joey,

1. You can download the following documents, which have a part number related to the K series. Document download link:

None of those part numbers matches any of the ones in the bootloader targets. The targets listed include MK02F12810, MK22F12810, MK22F25612, MK24F25612, MK64F12, and so on. Where do those particular numbers appear in NXP documentation? If I search for MK22F12810, for example, I get exactly two results, both of them decade-old MQX release notes that refer to it as a device family and show the associated dev boards but there's no mapping of those numbers to actual part numbers.

2. You can refer to the SDK package for K22, which is recommended.

MCU Boot is showing up as removed from the SDK package for the MK22FN512xxx12, hence my question.

3-4. You can refer to the links below to find some information.

What is the relationship between the "freedom_bootloader" described in MBOOTDEMOUG and MCU Boot? They look like they're different versions of the same thing. The most recent version of MCU Boot available for download is 2.0.0, with a date of Dec 18, 2014.

There is a manual (MCUBOOTRM) dated 05/2018 for "MCU Bootlaoder v2.5.0". The "freedom_bootloader" demo has no version information but has a copyright date of 2018 and bl_version.h gives its version as K280.

If I want the latest version of MCU Boot for the K22F family, where do I find that and its matching documentation?

Scott

[Joey_z]

hi，scottm

Thank you for your reply.

1. Check the Part Number content, such as MK22F12810 you mentioned, whose naming form I marked in the figure, this represents a series of chips. As the MK22FN128VLL10 method named in the following figure in K22P121M100SF9RM is a more specific chip name.

2. You can download SDK Version: 2.16.000 and select MCU Boot as the following figure.

In addition, we are sorry for the inconvenience caused to you, we did not provide the updated document.

Hope it can help you.

BR

Joey

[scottm]

1. Check the Part Number content, such as MK22F12810 you mentioned, whose naming form I marked in the figure, this represents a series of chips. As the MK22FN128VLL10 method named in the following figure in K22P121M100SF9RM is a more specific chip name.

How did you get the number K22P121M100SF9RM from MK22FN128VLL10? The chart you provided does not list any "P". I believe these part numbers are referencing the datasheet part number but I still can't find any comprehensive list.

To give another example, the MK22FN512 and MK22FN1M0 apparently correspond to datasheets K22P121M120SF7 and K22P121M120SF5, respectively, according to EB811. This doesn't seem to match with the explanation you've given - EB811 shows both the MK22FN512 and MK22FN256 under K22P121M120 numbers despite not having 1M flash. The MK22FN1M0 is more closely related to the MK22FX512 - I discovered this when moving from the MK22FN512 to the MK22FN1M0 to get more code space and finding out too late that the 1M0 part is an older device that doesn't support HSRUN and has other subtle differences. This is why I don't trust the table breakdown of part numbering alone. But the datasheet numbers differ in the "SF7" and "SF5" parts only, and these numbers aren't explained.

Maybe for a first step you can tell me what name you call this style of part number: MK02F12810, MK64F12, MKV11Z7, MK80F25615, etc. Are these family names? What terminology do you use to refer to this style so we can get on the same page?

2. You can download SDK Version: 2.16.000 and select MCU Boot as the following figure.

I will do that, but can you explain why it was removed in the latest version? Is it deprecated now? Has it been renamed?

Thanks,

Scott

[Joey_z]

hi,scottm

K22P121M100SF9RM is the name of our reference manual, which you can download from this link: Kinetis K22: 100MHz Cortex-M4F 128KB Flash (64-121 pin)     you can use the chip of MK22FN128VLL10 by referring to the K22P121M100SF9RM manual, the naming method of MK22FN128VLL10 can refer to the Part Number I provided to you before. I marked the name of MK22FN128VLL10 in the attached picture, I hope it will be useful to you.

For the naming method of MK02F12810 and MK64F12M, you can refer to the Part Number content, which represents a series of naming, indicating that all T (temperature range) and PP apply this name.
In addition, why there is no MCU Boot in the new version, I will try to help you consult the internal team.
Hope to help you!

BR

Joey

[scottm]

Hi Joey,

Here's the full list of targets for the Kinetis bootloader v2.0:

MK02F12810
MK22F12810
MK22F25612
MK22F51212
MK24F25612
MK64F12
MK65F18
MK66F18
MK80F25615
MK82F25615
MKL25Z4
MKL28Z7
MKL82Z7
MKS22F25612
MKV11Z7
MKV30F12810
MKV31F12810
MKV31F25612
MKV31F51212
MKV46F16
MKV58F22

To take one example, the MKV58F22 does not decode using the K series MCU part number chart you provided. Aside from the bootloader release notes, only one other document (KSDK120MKV5XRN) contains that number.

Searching for "KV58" doesn't bring up a product family. Searching for "KV5x" does take you to the product family, and you can see that there are KV58 and KV56 parts. None of the part numbers end in 22 - they're all 24. So which of those parts are "MKV58F22"?

I've found it's very unwise to assume that a device falls into one family just because of the part number. The MK22FN1M0 is a good example. The only board that supports it is the TWR-K21F120MA. The MK22FN512, on the other hand, is supported by the TWR-K22F120.

Surely NXP must have a complete list of all of their MCUs and which families they belong to. Where would one find this?

Scott

[Joey_z]

hi,scottm

For your problem, refer to part numbers in the data-sheet. 22 indicates CPU frequency220MHz. You can check the attached content.
Download link is as follows: https://www.nxp.com.cn/docs/en/data-sheet/KV5XP144M220.pdf.

BR

Joey

[scottm]

Hi Joey,

I think you are misunderstanding my problem. I don't care about the KV5x series at all. I'm using that as an example of the larger problem with the lack of documentation on the part numbers.

To go back to an earlier question, what do you CALL that style of part number, like "MK80F25615" and "MKV31F12810"? Are those family part numbers? Are they datasheet part numbers? What is the terminology used for that part number style within NXP?

Or are they simply a mistake by whoever created the bootloader targets? Did they create numbers of their own that don't follow an accepted convention?

I brought up the "MKV58F22" example in particular to highlight that it's seemingly impossible to connect that to part numbers if you don't already know them. If you see MKV58F22 and think to yourself "I wonder which parts that includes", without some list to refer to, the obvious answer is to browse NXP's site for the relevant family and see what's listed there. Except as you can see from the attached screenshot, there are only 8 parts listed under the KV58 family and they are all 240 MHz parts.

What I'm asking you is not for an answer on a single particular part number. I want to know the GENERAL solution for this - how to unequivocally map a part number like "MKV58F22" to its actual part numbers, without already knowing specific datasheets to search for.

Thanks,

Scott

[Joey_z]

hi,scottm

Thank you for your reply.

Like "MK80F25615", "MKV31F12810", "MKV58F22", these names indicate the name of a series. How to find the specific part numbers, you need to check the datesheet. I put the screenshot picture in the attachment. The search methods in the attachment are examples, and other search methods of chip series can be referred to. If other information about the chip is difficult to find, you can also contact us.

BR

Joey

[scottm]

Where is this documented? What piece of documentation says "to get the series number, take these pieces and only these pieces of the part number from the datasheet"? NXP's an ISO 9001 certified company - this has to be written down somewhere.

Trying to just guess at it is frustrating as heck. In your searches you found it under MKV58, but if you search instead of KV58 you don't find those parts.

How would you work the other direction, starting with "MKV58F22" and finding all of the parts that fall under that series? How would I find something like a family brochure for the KV5x family? There is a family at https://www.nxp.com/products/KV5x but it does not list any of the 200 or 220 MHz parts. 

Getting back to the more immediate issue, there is no "MK22F1M12" series. So to which series does the MK22FN1M0AVLH12 belong? And how would I know that? I know for a fact that not all code written for the MK22F51212 series will work with the MK22FN1M0 because the latter does not support the HSRUN mode and it does not support crystal-less USB operation.

Scott