Please help us understand the purpose of the message box that says "Please restart Evaluation Board to move processor to BAM mode and press OK", see attached screenshot. This message box is displayed when we build code in the Matlab/Simulink MBDT examples.
Is a reset sufficient? Is it really necessary to power cycle the board? And why?
Thanks
Solved! Go to Solution.
Hello @rsating,
Thank you for your interest in our MBDT Toolbox!
The message that pops up, telling the user to reset the board, asks for a reset from the button, not necessarily power down and power up, in order to set the board in the bootloader. When the MCU boots up, it enters the bootloader (that has to be flashed previously using the S32DS according to the quick start guide). When the processors boot up, it enters bootloader and waits for a five seconds for a new firmware to be delivered over UART. If it receives nothing from the host computer, then the bootloader starts executing the code already stored in the flash memory.
So the mechanism is as follows:
1. Simulink generates and compiles the code, and shows that popup message.
2. The user resets the board and within 5 seconds press the 'OK' button.
3. If everything works fine, the host sends the new firmware to the board and the board boots the new code.
Hope this helps,
Marius
Hello @rsating,
Thank you for your interest in our MBDT Toolbox!
The message that pops up, telling the user to reset the board, asks for a reset from the button, not necessarily power down and power up, in order to set the board in the bootloader. When the MCU boots up, it enters the bootloader (that has to be flashed previously using the S32DS according to the quick start guide). When the processors boot up, it enters bootloader and waits for a five seconds for a new firmware to be delivered over UART. If it receives nothing from the host computer, then the bootloader starts executing the code already stored in the flash memory.
So the mechanism is as follows:
1. Simulink generates and compiles the code, and shows that popup message.
2. The user resets the board and within 5 seconds press the 'OK' button.
3. If everything works fine, the host sends the new firmware to the board and the board boots the new code.
Hope this helps,
Marius