I am using ROM blhost for flashing over USB K32L2A31 device, and it is working fine. When reset button is pressed program is started, when NMI button is pressed device enter to bootloader mode. I just don't like every time 5 seconds delay after firmware is updated. In
I know that changing original boot configuration can lock device, so I am asking here what should I change in default SDK setup just to disable 5 seconds delay after bootloader reset command, and leave everything as it is. In Kinetis Bootloader Reference Manual pdf there is 5 second in reset command description but not how and if this can be changed.
The reset command can also be used to switch boot from flash after successful flash
image provisioning via ROM bootloader. After issuing the reset command, allow 5
seconds for the user application to start running from Flash.
/* Flash Configuration */
.section .FlashConfig, "a"
.long 0xFFFFFFFF
.long 0xFFFFFFFF
.long 0xFFFFFFFF
.long 0xFFFF3DFE
Reards,
Josip
Solved! Go to Solution.
Hi jh0,
No, the 5's peripheral waiting time can't change. It is defined in ROM code, not in address 0x400. If you refer to. for example, K64's flashloader demo, you can see BL_DEFAULT_PERIPHERAL_DETECT_TIMEOUT in bootloader_config.h. K32L2A's ROM bootloader has similar code.
Regards,
Jing
Hi jh0,
No, the 5's peripheral waiting time can't change. It is defined in ROM code, not in address 0x400. If you refer to. for example, K64's flashloader demo, you can see BL_DEFAULT_PERIPHERAL_DETECT_TIMEOUT in bootloader_config.h. K32L2A's ROM bootloader has similar code.
Regards,
Jing