You can use some tools to merge the generated APP and BOOTLOADER files together, and then burn them into the MCU through the tools. This is the method I often use.
for example, use j-flash, after merge the file, you can download it to the MCU directly.
You can see that BOOTLOADER is stored in FLEXNVM.
The default size we set for it is only 4KB. This storage address is not suitable for storing APP.
I don’t understand why you want to make such a modification.
In fact, the routine we provide ,the allocated space is very reasonable and you don't need to make any
other modifications at all.
please let me know if you still have question regarding this.
we're taking about S32K146 not S32K148 here. I have two suggestions for you.
1.According to your idea, this is the linker file I modified
Application:
m_interrupts (RX) : ORIGIN = 0x00000000, LENGTH = 0x00000400
m_flash_config (RX) : ORIGIN = 0x00000400, LENGTH = 0x00000010
m_text (RX) : ORIGIN = 0x00000820, LENGTH = 0x000FF7DF
Bootloader:
m_interrupts (RX) : ORIGIN = 0x00000410, LENGTH = 0x00000400
m_flash_config (RX) : ORIGIN = 0x00000810, LENGTH = 0x00000010
m_text (RX) : ORIGIN = 0x10000000, LENGTH = 0x00001000 1. Reset and enter the APP first
2. Receive requests from some commanders to enter the Bootloader
3. Enter the Bootloader to receive the new APP file. After the APP is successfully updated, it will jump to the APP again.
There are some issues you must consider here. You must burn both the APP and BOOTLOADER into the MCU using the debugger.
2.you don't have to change AN12218's linker file.
My suggestion is that if you want to shorten the time for the Bootloader to enter the App, you can do it through some shared variables, for example:
1. Enter Bootloader after reset
2.Bootloader checks the variable, which indicates that the APP update is not currently requested.
3. If APP already exists in the current MCU, jump to APP
4. If you receive a request to update the APP, modified the variable then jump into the Bootloader
