• State
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 38 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM0G3507: chip not detecting, mentioning "DAP error. device in low power state

Vijayasarathy N
Prodigy 120 points

Part Number: MSPM0G3507
Other Parts Discussed in Thread: UNIFLASH, MSPM0L1105, MSPM0C1103

Hi TI Tech team,

 

We are doing board bringup of our industrial motor board based on MSPM0G3507, getting below

error when I use uniflash to read the memory of the chip

I am connecting it to the launchpad SWD pins, the same connections work for our other designs on MSPM0C1103 and MSPM0L1105 boards.

Below is the full error message

 

"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"

 

SWD pins vis R18 and R21 are shorted or connected during the testing.

Appreciate your support.

 

Thanks in advance.

 

VijayIPM_MCU_INVERTER.pdf 

  • 0
    TI__Expert 7065 points

    Hi, thanks for the question. The DAP error is common when bringing up the MSPM0G3507. It usually means the microcontroller has entered a deep sleep or fault state, blocking the SWD port. You can typically bypass this by forcing the MCU into BSL (Bootloader) mode and triggering a Factory Reset. On your target board, tie the BSL Invoke Pin (PA18) to VCC. By default, pulling this pin high during power-up or reset puts the chip into BSL mode. Hold the NRST pin low (or press the reset button) for at least 1 second. While NRST is low, power cycle your board (or release NRST while keeping PA18 tied to VCC).

    Also unlike smaller MSPM0 designs, the MSPM0G3507's high-speed debug interface is more sensitive to signal integrity. Verify that you have a pull-up resistor on the SWDIO line and a pull-down resistor on the SWCLK line (your 4.7 kΩ work well, but both are pull-up which is an issue) if your Launchpad debug signal is weak or run through a long cable.

    For a bit more digging, can you check the internal power rails on the MSPM0G3507 to ensure it is not brown-out resetting? VDD should be steady at 3.3 V and if you measure VCore, (1.2 V or 1.35 V output) and it it is fluctuating, there might be a short or insufficient capacitance on your VCAP pin.