topic Re: What could be a problem with bootloader in MKW01Z128? in Kinetis Microcontrollers

What could be a problem with bootloader in MKW01Z128?

sergiiparadiuk — Thu, 17 May 2018 13:59:31 GMT

Hello,

I am working on custom bootloader over RF mcu MKW01Z128. Now the bootloader puts all bin file (work application) in the address 0x8E00. After start the app, and program jumps to the address 0x8E00 and after I debuged in disasembler and it calls Hardware hendler.

I checked, the bin file was copied in correct address and the Linker file is correct too for the app.

define symbol __region_ROM_start__ = 0x0000E800;
define symbol __region_ROM_end__ = 0x0001FFFF;

Maybe I messed some thing..

Re: What could be a problem with bootloader in MKW01Z128?

gerardo_rodriguez — Tue, 22 May 2018 21:09:14 GMT

Hello Sergii Paradiuk,

I suggest basing your custom bootloader in either the Developer’s Serial Bootloader AN2295 (SW) or the MCU Bootloader for Kinetis microcontrollers.

Before jumping to your application, you should return the MCU to its reset state, set the application vector table offset (VTOR) and application stack pointer. You could take as reference the jump_to_application() function of the "C:\NXP\NXP_Kinetis_Bootloader_2_0_0\src\bootloader\src\bl_main.c" file from the MCU bootloader for Kinetis MCUs package.

Regards,

Gerardo