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.

[参考译文] MSPM0G3507:UNIFLASH 和 JLINK 编程失败

Guru**** 2680595 points

Other Parts Discussed in Thread: UNIFLASH, MSPM0G3507

请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1591812/mspm0g3507-uniflash-and-jlink-programming-failed

器件型号: MSPM0G3507
Thread 中讨论的其他器件: UNIFLASH

尊敬的 Champs:

 

客户现在在生产线上发现故障器件。 将其焊接到 EVM 上后、客户无法使用 JLINK 和 UNIFLASH 对其进行编程。  

JLINK 错误日志:

Application log started
 - J-Flash V7.98b (J-Flash compiled Jul 31 2024 16:14:36)
 - JLinkARM.dll V7.98b (DLL compiled Jul 31 2024 16:14:11)
Reading flash device list [C:\Users\huangsh1\SEGGER\JLink_V798b\ETC/JFlash/Flash.csv] ...
 - List of flash devices read successfully (451 Devices)
Reading MCU device list ...
 - List of MCU devices read successfully (11298 Devices)
Opening project file [D:\01_SourceCode\jlink\MSPM0G3507.jflash] ...
 - Project opened successfully
Opening data file [D:\00_ProjectCode\04_US100KW\ProductCode\old\CT\9.0030.060301PICF\US100KW_CT_V1.0.hex] ...
 - Data file opened successfully (7568 bytes, 1 range, CRC of data = 0xB743594F, CRC of file = 0x874275EB)
Connecting ...
 - Connecting via USB to probe/ programmer device 0
 - Probe/ Programmer firmware: J-Link V9 compiled May  7 2021 16:26:12
 - Probe/ Programmer S/N: -1
 - Device "MSPM0G3507" selected.
 - InitTarget() start
 - DAP initialized successfully.
 - No PWR-AP detected.
 - InitTarget() end - Took 4.94ms
 - 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
 - InitTarget() start
 - DAP initialized successfully.
 - No PWR-AP detected.
 - InitTarget() end - Took 2.41ms
 - 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
 - Target interface speed: 200 kHz (Auto)
 - VTarget = 3.288V
 - InitTarget() start
 - DAP initialized successfully.
 - No PWR-AP detected.
 - InitTarget() end - Took 3.08ms
 - 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
 - InitTarget() start
 - DAP initialized successfully.
 - No PWR-AP detected.
 - InitTarget() end - Took 3.64ms
 - 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
 - ERROR: Failed to connect.
Could not establish a connection to target.
 - ERROR: Connect failed

 

Uniflash 错误日志:
[2025/11/26 PM 4:15:27]【信息】Cortex-M0P:MSPM0G3507(引导加载程序)
[2025/11/26 pm 4:15:27][info] Cortex-M0P:正在调用引导加载程序
[2025/11/26 PM 4:15:28]【错误】Cortex-M0P:自动引导加载程序调用失败且响应为... 1.
[2025/11/26 PM 4:15:28]【错误】Cortex-M0P:尝试手动引导加载程序调用...
[2025/11/26 PM 4:15:29]【信息】CORTEX_M0P:
[2025/11/26 PM 4:15:39]【错误】Cortex-M0P:[ERROR_MESS]无法接收预期数据!
[2025/11/26 PM 4:16:25]【信息】Cortex-M0P:MSPM0G3507(引导加载程序)
[2025/11/26 pm 4:16:25][info] Cortex-M0P:正在调用引导加载程序
[2025/11/26 PM 4:16:25]【错误】Cortex-M0P:自动引导加载程序调用失败且响应为... 1.
[2025/11/26 PM 4:16:25]【错误】Cortex-M0P:尝试手动引导加载程序调用...
[2025/11/26 PM 4:16:26]【信息】CORTEX_M0P:
[2025/11/26 PM 4:16:37]【错误】Cortex-M0P:[ERROR_MESS]无法接收预期数据!

 

这是否意味着器件已锁定? 如何解决该错误? 以及 为什么锁定器件?  

谢谢!  

Julia

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Julia:

    您能否让客户在 UNIFLASH 中选择“MSPM0G3507"而“而不是“MSPM0G3507(引导加载程序)“选项并重试? 如果仍然无法成功刷写、请尝试调用器件进入 BSL 并进行恢复出厂设置、然后再次尝试刷写、这是进入 BSL 的方法、如下所示。

    此致、
    彼得