• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 29 subscribers
  • Views 244 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: Unable to program the controller due to shutdown mode

Raj Parab
Prodigy 135 points
Part Number: MSPM0G3107
Other Parts Discussed in Thread: MSPM0G3507

Tool/software:

Hello,

I had recently programmed my MSPM0G3107 controller in shutdown mode. The issue is that I thought we can program the controller using debug and reset pins, Unfortunately I get the following error:

CS_DAP_0: Error connecting to the target: DAP Connection Error. This could be caused by the device having gone to low power mode. Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information.

Now to solve this specific error, I have tried factory reset and mass erase, but it doesn't work and the controller gives the same error i.e. controller gives the above error for trying these procedures. Does anyone have any suggestions on how to sidestep this problem. 

Regards

  • 0
    TI__Expert 3735 points

    Hi Raj, you can also try resetting the XDS110 using the tool included in the ccs folder in your C drive. mine for example is: C:\ti\ccstheia151\ccs\ccs_base\common\uscif\xds110. There is a PDF included in that same folder that shows how to use the xds110reset.exe and xdsdfu.exe. This may fix it, but let me know if the issue persists.

    -Brian

  • 0 in reply to Brian Dempsey
    Prodigy 135 points

    Hey Brian,

    Yes I tried xds110reset.exe using the pdf folder provided and provided the required instructions using Command Line Terminal. Despite following the process, I am unable to program the controller i.e. the issue still persists. 

  • 0 in reply to Raj Parab
    TI__Expert 3735 points

    Ok, just to clarify, are you using a launchpad or a custom board?

  • 0 in reply to Brian Dempsey
    Prodigy 135 points

    I am using custom board. Are there any solutions to this problem ?

  • 0 in reply to Raj Parab
    TI__Expert 3735 points

    Ok, thanks for clarifying. Can you hold the device in reset (NRST) and do a POR? Looking at the reference manual (Section 28.3), a debug connection to the DEBUGSS is not possible while the device is in SHUTDOWN mode, but a debug probe can allow the device to exit SHUTDOWN mode by attempting to communicate with the SWD pins. The device will detect attempted SWD communication even when the device is in SHUTDOWN. If activity is detected, a SHUTDOWN exit is initiated and the device will transition through a BOR state, after which a debug connection can be made to the DEBUGSS through SWD.

    I would recommend trying this to see if it resolves the issue. Let me know if you are still getting the same error.

    -Brian

  • 0 in reply to Brian Dempsey
    Prodigy 135 points

    Hi Brian,


    I am grounding the NRST pin and trying to upload the code via MSPM0G3507 Launchpad and connecting the SWDIO and SWCLK to my custom board controller. After which i try to upload the code using Code Composer Studio, even after which i get the same error as mentioned above. I have few questions regarding that:

    I have grounded the NRST pin throughout the operation of uploading the code. Is this correct ? 
    Secondly i have used only the SWDIO & SWCLK pins for uploading while the NRST pin is being grounded. 

     So, can you let me know if my approach was correct and if not, what changes are to be made. If correct then how to approach this problem ?

    Thanks for your time

  • 0 in reply to Raj Parab
    TI__Expert 3735 points

    Hey Raj, the NRST should have a 47k pull up resistor to VCC. The debug interface should pull this low for communication with the MCU, so aside from the prior mentioned reset process, the debug interface should automatically do this when deploying the firmware to the device. Can you confirm you have the pull up to VCC?

  • 0 in reply to Brian Dempsey
    Prodigy 135 points

    Hey Brian,

    Sorry for replying late.
    Yes i have pulled up the NRST pin using 47k resistor. Also a 0.01 micro-farad capacitor is connected to the NRST pin as well.
    These are the connections to that pin.

    Is there something that I am missing or doing wrong ?

  • 0 in reply to Raj Parab
    Prodigy 135 points

    Hey I found the solution. 

    There is a pdf named unlock MSPM0. Main point in this solution is that the BSL pin (PA18 for MSPM0) need to be pulled up before powering the controller. I was pulling this pin up after the controller turns ON. 

    /cfs-file/__key/communityserver-discussions-components-files/908/1220.Unlock-MSPM0-instructions.pdf

    Thanks a lot for the help, Brian.