• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 112 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0G3519: Software cannot startup after power on

zihui zhao
Prodigy 60 points

Part Number: MSPM0G3519
Other Parts Discussed in Thread: SYSCONFIG

Hi, Team

      We are using MSPM0G3519 as a MCU to control the RF. The chip RF and MSPM0G3519 are assembled in one PCB. Now we can startup the software with XDS110 debugger connected and load program every re connected to XDS110. Once disconnected with XDS110 and power off, power on again,  it cannot find the right startup address to run the code. Do you have any idea for this strange phenomenon ? Could you give us some suggestions to investigate this issue continually?

     After power on and connected sensor, no load program just click reset button, it shows as following, it cannot jump to the reset_handler code.

image.png

The flash memory is as following

image.png

  • 0
    TI__Expert 6115 points

    Hi zihui,

    Need to confirm with you below questions first:

    1. Do you also test some simple demo code in our SDK and to see whether this issue still occur? Just want to make sure whether this issue only occur in your own code and meanwhile exclude some hardware issues.

    2. Do you modify the .cmd file in the project? Is it any bootloader related logic in your code that force the PC jumping to other place?

    Best Regards,
    Peter

  • 0
    Prodigy 60 points

    Hi, Peter

         Thank you for your response, we have investigated that the HW for bsl_invoke pin PA18 is keeping High level, if change it to low level, it seems the sensor can startup successfully. So just want to confirm,

         1. Does the default level for bsl_invoke pin need be low? As the HW may not be changed, we disable the bsl mode in system config, is there any risk to disable the bsl mode?

    ...

        

  • 0 in reply to zihui zhao
    TI__Expert 6115 points

    Hi zihui,

    Yes, the bsl invoke pin must be low, or when power on, it will trigger the device into our ROM BSL by default and wait for the BSL command. Commonly we connect the BSL Invoke pin with a pull-down resistor to the ground to ensure it set to be low.

    If you don't want to make some HW change, you can disable the BSL in the sysconfig, it will no effect to your app code, but please note that reserve the invoke pin can effectively resolve some issues like device cannot make connection with SWD or software running away, at this time, if bsl invoke enabled, we can trigger the device into the BSL first and then do the factory reset to unlock the device.

    Best Regards,
    Peter