• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 447 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSPM0G3107: Mass erase procedure using Segger J-Link w/ Ozone debugger.. BSL Invocation..

Newman
Expert 5845 points
Part Number: MSPM0G3107
Other Parts Discussed in Thread: SEGGER

My customer has the following questions..

Currently I have a concern regarding restoring microcontroller after lockup.

For me, the lockup happens often, after each exception leading to hard fault. After that default reflasing with SWD does not work and I keep getting (Error -614 @ 0x0)

I know about mass erase procedure from the presentation: /cfs-file/__key/communityserver-discussions-components-files/908/Unlock-MSPM0.pptx

I know how to invoke BSL as described in https://www.ti.com/lit/pdf/slau319

 

My questions are:

  1. How can the mass erase procedure above be invoked using Segger J-Link and Ozone debugger (or any other standard JTAG probe/environment outside CCS)?
  2. Alternatively, for development purposes: can BSL be invoked without using PA18?

Thx, Merril

  • 0
    TI__Genius 13905 points

    Hi Merril,

    For Q1:

    At the moment, support for DSSM commands is implemented using CCS or the DSSM Unlock GUI tool with XDS110 (Mass erase need completed by DSSM).

    For Q2；

    It can invoke without PA18, and have two workarounds:

    1. Using other hardware pin, it can be modified in NONMAIN.

    2.disable hardware invoke pin via NONMAIN, then it can run into bsl with a software invoke, which means that you need do some modficiations in application code.

    B.R.

    Sal