• State
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 56 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM0G3519: MSPM0G3519: Error connecting to target when debugging

abhilash k
Prodigy 30 points

Part Number: MSPM0G3519
Other Parts Discussed in Thread: UNIFLASH

Hello , 

I am facing an issue in connecting my target MSPM0G3519 with the debugger (trace 32 )

 

Error Message shown in both debuggers: 

T32:

When connected with T32 debugger  getting this error: 

 

 

CCS STUDIO :

When connected to CCS studio :

Error connecting to the target:  Connection to MSPM0 core failed.  Possible root causes:

1) Debug access within NONMAIN was disabled or enabled with password.

2) Peripheral mis-configuration (e.g improper watchdog or clock).  To see a more detailed diagnostic of the issue, please press the 'Read boot diagnostic' button.

 

When Clicked Read Boot diagnostics button :

 

CS_DAP_0: Device diagnostic read = 0x00000036

CS_DAP_0:

Possible root causes could be one or multiple of the following:

1) Invalid CRC configuration

2) Invalid BCR configuration

3) Invalid BSL configuration

 

Possible recovery method:

1) Perform a DSSM factory reset

2) If method one does not work please remove power, hold nRST low, connect the device while nRST is held low, and then perform a DSSM factory reset

 

Questions:

1. Is there any recovery method for this situation?
2. Based on the diagnostic value 0x00000036, 

  • 0
    TI__Genius 12845 points

    Hi Abhilash,

    You could refer the 7.1 sector of MSPM0 MCUs Development Guide (Rev. G) for MSPM0 factory reset.

    Notice it should based on XDS110 debugger + Uniflash/CCS. The XDS110 embedded in MSPM0G3519 launchpad could also be used in this case.

  • 0 in reply to Pengfei Xie
    Prodigy 30 points

    Hi Pengfei Xie,

    We tried this method, but the board is not up 

    Unable to connect the board via CCS Studio, also getting the same diagnostic report as above 

    CS_DAP_0: Device diagnostic read = 0x00000036

    CS_DAP_0:

    Possible root causes could be one or multiple of the following:

    1) Invalid CRC configuration

    2) Invalid BCR configuration

    3) Invalid BSL configuration

    Possible recovery method:

    1) Perform a DSSM factory reset

    2) If method one does not work please remove power, hold nRST low, connect the device while nRST is held low, and then perform a DSSM factory reset

  • 0
    Prodigy 30 points

    Please have a look on below code which might have affected the board , since board was in running reset mode before going debug port timeout in t32 

    Please have a look on below code which might have affected the board , since board was in running reset mode before going debug port timeout in t32 :

FUNC(void, BSWM_APPL_CODE) Eb_Intgr_BswM_WaitMemDriverReady(void)
{
#if defined(BASE_MEMIF_ENABLED)
#if (BASE_MEMIF_ENABLED == STD_ON)
MemIf_StatusType status = MEMIF_UNINIT;
#endif
#endif
uint16 iterCount = 0U;

/* Loop until Fee reaches IDLE so it has time to write virtual-sector headers
* on blank data flash (first boot / after sector erase). Stop immediately on
* IDLE to avoid triggering spurious background compaction.
* Safety cap: 200 iterations prevents an infinite loop if Fee gets stuck. */
do
{
#if defined(BASE_FEE_ENABLED)
#if (BASE_FEE_ENABLED == STD_ON)
Fee_MainFunction();
/*
FLS_MAIN_FUNCTION_DEFINE is configured in McalExt and will be generated in Platforms_Modules.h file
e.g. #define FLS_MAIN_FUNCTION_DEFINE Fls_17_Pmu_MainFunction()
*/

#ifndef _X86_
/* MemAcc_MainFunction(); */
#endif
FLS_MAIN_FUNCTION_DEFINE;
#endif
#endif

#if defined(BASE_FEE_ENABLED)
#if (BASE_EA_ENABLED == STD_ON)
Ea_MainFunction();
Eep_MainFunction();
#endif
#endif

#ifndef _X86_
status = Fee_GetStatus();
#else
status = MemIf_GetStatus(0);
#endif
iterCount++;
} while ((MEMIF_IDLE != status) && (iterCount < 200U));

  • 0 in reply to abhilash k
    TI__Genius 12845 points

    Hi Abhilash,

    Two quick question here:

    • Do you use NONMAIN in your application?
    • Is this connection issue follow with your firmware or it follow a specific hardware board?

**Attention** This is a public forum