MSPM0L1306: Could not connect to target

Daniele Nardi

Part Number: MSPM0L1306
Other Parts Discussed in Thread: SEGGER

I can't connect to device for programming anymore.

Using the Segger j-link-Ozone suite, I downloaded a firmware just once, i stepped-over the initialization function, then device stopped communicating with debugger and new connections became impossible.

Debugger console output is:

Device "MSPM0L1306" selected.
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Attach to CPU failed. Executing connect under reset.
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map has been reached
Iterating through AP map to find AHB-AP to use
Could not find core in Coresight setup
Connection failed.

Project created with CCS and syscfg, details attached.

Ozone v3.30b

J-Link v7.92c

Debugger: J-Link PLUS V12.00 (2023 Aug 2 10:34)

ccs_conf.txt

myProject.syscfg.txt

/**
 * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
 * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
 * @cliArgs --device "MSPM0L130X" --package "VSSOP-20(DGS20)" --part "Default" --product "mspm0_sdk@1.10.00.05"
 * @versions {"tool":"1.17.0+3128"}
 */

/**
 * Import the modules used in this configuration.
 */
const ADC12   = scripting.addModule("/ti/driverlib/ADC12", {}, false);
const ADC121  = ADC12.addInstance();
const Board   = scripting.addModule("/ti/driverlib/Board");
const GPIO    = scripting.addModule("/ti/driverlib/GPIO", {}, false);
const GPIO1   = GPIO.addInstance();
const PWM     = scripting.addModule("/ti/driverlib/PWM", {}, false);
const PWM1    = PWM.addInstance();
const SYSCTL  = scripting.addModule("/ti/driverlib/SYSCTL");
const SYSTICK = scripting.addModule("/ti/driverlib/SYSTICK");
const TIMER   = scripting.addModule("/ti/driverlib/TIMER", {}, false);
const TIMER1  = TIMER.addInstance();
const UART    = scripting.addModule("/ti/driverlib/UART", {}, false);
const UART1   = UART.addInstance();

/**
 * Write custom configuration values to the imported modules.
 */
const gate6  = system.clockTree["MFCLKGATE"];
gate6.enable = true;

ADC121.$name                      = "ADC12_0";
ADC121.samplingOperationMode      = "sequence";
ADC121.endAdd                     = 3;
ADC121.repeatMode                 = true;
ADC121.adcMem1chansel             = "DL_ADC12_INPUT_CHAN_1";
ADC121.adcMem2chansel             = "DL_ADC12_INPUT_CHAN_2";
ADC121.adcMem3chansel             = "DL_ADC12_INPUT_CHAN_3";
ADC121.adcMem0_name               = "AI_VBAT_MON";
ADC121.adcMem1_name               = "AI_MOTOR_P";
ADC121.adcMem2_name               = "AI_MOTOR_N";
ADC121.adcMem3_name               = "AI_MOTOR_I";
ADC121.sampClkSrc                 = "DL_ADC12_CLOCK_ULPCLK";
ADC121.peripheral.$assign         = "ADC0";
ADC121.peripheral.adcPin0.$assign = "PA27";
ADC121.peripheral.adcPin1.$assign = "PA26";
ADC121.peripheral.adcPin2.$assign = "PA25";
ADC121.peripheral.adcPin3.$assign = "PA24/OPA0.IN0-";
ADC121.adcPin0Config.$name        = "ti_driverlib_gpio_GPIOPinGeneric0";
ADC121.adcPin1Config.$name        = "ti_driverlib_gpio_GPIOPinGeneric5";
ADC121.adcPin2Config.$name        = "ti_driverlib_gpio_GPIOPinGeneric6";
ADC121.adcPin3Config.$name        = "ti_driverlib_gpio_GPIOPinGeneric7";

Board.genPeriphPinFile            = true;
Board.configureUnused             = true;
Board.peripheral.$assign          = "DEBUGSS";
Board.peripheral.swclkPin.$assign = "PA20";
Board.peripheral.swdioPin.$assign = "PA19";
Board.genFileMod.$name            = "ti_driverlib_BoardPins0";

GPIO1.$name                         = "GPIO_GRP_0";
GPIO1.associatedPins.create(6);
GPIO1.associatedPins[0].$name       = "DO_MOTOR_DIR";
GPIO1.associatedPins[0].pin.$assign = "PA6";
GPIO1.associatedPins[1].$name       = "DO_MOTOR_EN";
GPIO1.associatedPins[1].pin.$assign = "PA22";
GPIO1.associatedPins[2].$name       = "DI_ST_MOTOR";
GPIO1.associatedPins[2].direction   = "INPUT";
GPIO1.associatedPins[2].pin.$assign = "PA2";
GPIO1.associatedPins[3].$name       = "DI_SW_BWD";
GPIO1.associatedPins[3].direction   = "INPUT";
GPIO1.associatedPins[3].pin.$assign = "PA0";
GPIO1.associatedPins[4].$name       = "VBAT_SW_EN";
GPIO1.associatedPins[4].pin.$assign = "PA4";
GPIO1.associatedPins[5].$name       = "VBAT_MON_EN";
GPIO1.associatedPins[5].pin.$assign = "PA23";

PWM1.ccIndex                            = [0];
PWM1.$name                              = "DO_PWM_MOTOR";
PWM1.clockDivider                       = 4;
PWM1.timerCount                         = 400;
PWM1.peripheral.ccp0Pin.$assign         = "PA16";
PWM1.PWM_CHANNEL_0.$name                = "ti_driverlib_pwm_PWMTimerCC0";
PWM1.ccp0PinConfig.direction            = scripting.forceWrite("OUTPUT");
PWM1.ccp0PinConfig.hideOutputInversion  = scripting.forceWrite(false);
PWM1.ccp0PinConfig.onlyInternalResistor = scripting.forceWrite(false);
PWM1.ccp0PinConfig.passedPeripheralType = scripting.forceWrite("Digital");
PWM1.ccp0PinConfig.$name                = "ti_driverlib_gpio_GPIOPinGeneric3";

SYSCTL.powerPolicy = "STANDBY1";
SYSCTL.clockTreeEn = true;

SYSTICK.periodEnable  = true;
SYSTICK.period        = 32000;
SYSTICK.systickEnable = true;

TIMER1.interrupts  = ["ZERO"];
TIMER1.timerClkSrc = "LFCLK";
TIMER1.timerPeriod = "10 ms";
TIMER1.$name       = "TIMER_WU";

UART1.$name                    = "UART_0";
UART1.targetBaudRate           = 115200;
UART1.peripheral.$assign       = "UART0";
UART1.peripheral.rxPin.$assign = "PA18";
UART1.peripheral.txPin.$assign = "PA17/OPA1.IN0-";
UART1.txPinConfig.$name        = "ti_driverlib_gpio_GPIOPinGeneric1";
UART1.rxPinConfig.$name        = "ti_driverlib_gpio_GPIOPinGeneric2";

/**
 * Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
 * version of the tool will not impact the pinmux you originally saw.  These lines can be completely deleted in order to
 * re-solve from scratch.
 */
PWM1.peripheral.$suggestSolution   = "TIMG0";
TIMER1.peripheral.$suggestSolution = "TIMG1";

11 months ago

0 Daniele Nardi 11 months ago

Prodigy 70 points

Addendum: from the reset PIN the following signal is coming out:

0 Johnson He 11 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Daniele,

Have you checked RTSET pin connection? this pin is connect to debugger? or floating?

Thanks!

Best Regards

Johnson

0 Daniele Nardi 11 months ago in reply to Johnson He

Prodigy 70 points

Hello Johnson,

if you mean the NRESET pin, yes, it is connected to debugger and to a 47k pullup resistor

0 Johnson He 11 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Daniele,

I guess this reset signal should from debugger, thus MCU can not run normally.

Maybe you can try to disconnect reset pin to see if MCU can run.

But I am not clear why debugger generate this waveform for RESET pin.

Thanks!

Best Regards

Johnson

0 Daniele Nardi 11 months ago in reply to Johnson He

Prodigy 70 points

It isn't from debugger, it's there also when debugger is disconnected

0 Daniele Nardi 11 months ago in reply to Johnson He

Prodigy 70 points

acquisition.zip

This zip file contains the acquisition of SWDIO and SWDCLK pins, get with Saleae Logic Pro 8

0 Johnson He 11 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Daniele,

You means that the reset pin will be toggle when power even don't connect this debugger?

Have you download some code into this MCU? Like WDT code maybe?

And only one device? Or all device keep same phenonmenon?

What I'm more confused about is why the MCU RST pin keeps toggle. If you don't connect any debugger, this phenomenon is very strange.

For the waveform, this is captrue in Debuggwe download time?

Thanks!

Best Regards

Johnson

0 Daniele Nardi 11 months ago in reply to Johnson He

Prodigy 70 points

Hi Johnson,

yes, the pin toggles even when debugger is fully disconnected.

I downloaded some code, just the initialization procedure made by syscfg, pins read and pwm activation/deactivation.

The capture is in debugger download time, yes

0 Johnson He 11 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Daniele,

Do you have another MSPM0 to see if the reset pin is normal?

I think maybe the code issue cause MCU reset, for this device, you can try to keep PA18 High when MCU power on. This action will push MCU enter BSL mode rathan than run app code. This can avoid the app code issue maybe. Then try to download new code.

Does this issue occur in our paunchpad? or the borad design your side?

Thanks!

Best Regards

Johnson

0 Daniele Nardi 11 months ago in reply to Johnson He

Prodigy 70 points

Hi,

the issue occurs on a board design on our side, I didn't try on a launchpad.

Thank you for the suggestion, I'll provide feedback as soon as possible.

Regards,

Daniele

0 Johnson He 11 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Daniele,

Please let me know if any test result from your side.

Thanks!

Best Regards

Johnson

0 Daniele Nardi 10 months ago in reply to Johnson He

Prodigy 70 points

Hello Johnson,

sorry for delayed responde, but I've been on sick leave.

Unfortunately, the affected board is no longer available. I created a new configuration with a new one, this one is working properly. Checking the differences between the old the new configuration, the only difference I spot is the "configure unused pins" flag, which I did'nt assert on the new configuration: could it have been that? The reset pin left availablke on the Syscfg tool, then configued as output pin?

0 Daniel Waleniak 10 months ago in reply to Daniele Nardi

TI__Expert 4435 points

Hi Daniele,

After you try Johnson's suggestion, I also suggest trying the MSPM0_Factory_Reset_Tool (ti.com) if you have not tried it already.

Best regards,

Daniel

0 Daniele Nardi 10 months ago in reply to Daniel Waleniak

Prodigy 70 points

Hello,

the solution to power up with PA18 high is not working.

MSPM0 factory reset tool is not usable at this moment, because I'm not using XDS, I'm using J-LINK debugger

0 Johnson He 10 months ago in reply to Daniele Nardi

TI__Mastermind 28426 points

Hi Danriele,

Do you have any MSPM0 Launchpad in your side? There will include a XDS110-ET can run Factory Reset Command.

Thanks!

Best Regards

Johnson

+1 Daniele Nardi 10 months ago in reply to Johnson He

Prodigy 70 points

Hi!

I made it using the the XDS110-RT into my Launchpad and through CCS.

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0L1306: Could not connect to target