Developing a S32K116 Bootloader Application

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

Developing a S32K116 Bootloader Application

Jump to solution
1,344 Views
FurkanSenol
Contributor II

Hello,

    I am trying to develop a bootloader for an application that runs on S32K116. I've managed to find an example project of S32K148 bootloader and I read that this can be modified to be used on S32K116. But the problem is I do not know how and what to modify. I could not find any documents or information about the modifying process. I have not worked on bootloader project before hence my bootloader knowledge is limited to what I can find on the internet.

Edit: Firmware update will be performed via UART interface.

    Are there any documents of NXP that explains how to modify and use the S32K148 bootloader example for other MCUs?

    If you could simply point out the topics that I should be aware of about developing a bootloader project for S32K116 that would be great!

 Thanks in advance!

Best regards,

Furkan

Tags (2)
0 Kudos
1 Solution
1,336 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi Furkan,

We provide some bootloaders which are supposed to be a starting point for customers to develop own solution. It’s not production code. And most of customers have usually specific requirements, so they need to modify the projects anyway.

 

https://www.nxp.com/docs/en/application-note/AN12218.pdf

https://www.nxp.com/docs/en/application-note-software/AN12218SW.zip

 

https://www.nxp.com/docs/en/application-note/AN12323.pdf

https://www.nxp.com/docs/en/application-note-software/AN12323SW.zip

 

Generally, when porting any project, the best way is to create new empty project for your derivative. Next step is to update the linker file. This is necessary for both bootloader and application. You can use original linker files from the application notes as a guidance. If some help with linker file is needed, search for “ld.pdf” documentation in S32 Design Studio.

Then you can copy the source files to your new project and update them as necessary (S32K116 has less flash, so you need to update the code for erase, then you need to check which UART instance will be used etc.). Before doing this, try to get familiar with the original bootloader project as much as possible, so you know what’s going on.

When going from S32K14x to S32K11x, this application note should be helpful:

https://www.nxp.com/docs/en/application-note/AN11997.pdf

Regards,

Lukas

View solution in original post

0 Kudos
2 Replies
1,337 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi Furkan,

We provide some bootloaders which are supposed to be a starting point for customers to develop own solution. It’s not production code. And most of customers have usually specific requirements, so they need to modify the projects anyway.

 

https://www.nxp.com/docs/en/application-note/AN12218.pdf

https://www.nxp.com/docs/en/application-note-software/AN12218SW.zip

 

https://www.nxp.com/docs/en/application-note/AN12323.pdf

https://www.nxp.com/docs/en/application-note-software/AN12323SW.zip

 

Generally, when porting any project, the best way is to create new empty project for your derivative. Next step is to update the linker file. This is necessary for both bootloader and application. You can use original linker files from the application notes as a guidance. If some help with linker file is needed, search for “ld.pdf” documentation in S32 Design Studio.

Then you can copy the source files to your new project and update them as necessary (S32K116 has less flash, so you need to update the code for erase, then you need to check which UART instance will be used etc.). Before doing this, try to get familiar with the original bootloader project as much as possible, so you know what’s going on.

When going from S32K14x to S32K11x, this application note should be helpful:

https://www.nxp.com/docs/en/application-note/AN11997.pdf

Regards,

Lukas

0 Kudos
1,320 Views
FurkanSenol
Contributor II

Hi Lukas,

Thank you for all the information and documents! I will get started with the original bootloader project to get more insight about the process.

Best regards,

Furkan

0 Kudos