This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-MSPM0G3507: MSPM0G3507

Part Number: LP-MSPM0G3507

Hello Team,

In MSPM0G SDK there is example for secondary bootloader, which does the same task as the ROM based bootloader, this secondary bootloader has address mentioned in example as 0x1040, and also given the static write protection(SWP) to the lower two sectors which includes secondary bootloader code. For this example i made change, i toggled a on board LED while its in secondary bootloader code. So according to document MSPM0 Bootloader.pdf  attached here, once i upload this example in controller it will never execute ROM based bootloader.

So my question is above sdk example works only for 1st time when i flash the code into it i can see led toggle.but when i reset the board i didn't see the LED blinking, and also when i try to send bootloader commands by docklight(This is something i tried and it run succesfully i can send bootloader commands via Docklight tools and was able to communicate with ROM based bootloader)tool it doesn't respond, by default when i reset the board ROM based bootloader should invoke the secondary bootloader and LED should be toggling, but it stays off. Now next when i try the BSL key based sequence to invoke bootloader(which should be secondary BSL) ROM based bootloader responds to it.

what am i doing wrong here, why the second bootloader is not invoked every time i reset the board?

  • Hi Avinash,

    The BSL doesn't get invoked just through a board reset, there needs to be another invoke cause, which is accepted after a POR. For the default it is through the BSL invoke pin (PA18). So when you do a reset and toggle the BSL pin you will run through the bootloader.

    Regards,

    Luke