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 and JLINK programming failed

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

Hi Champs,

 

Customer now found a fail device on the production line. After soldering it onto the EVM, the customer failed to program it using both JLINK and UNIFLASH. 

JLINK error log:

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 error log:
[2025/11/26 pm 4:15:27] [INFO] CORTEX_M0P: MSPM0G3507(Bootloader)
[2025/11/26 pm 4:15:27] [INFO] CORTEX_M0P: Invoking Bootloader....
[2025/11/26 pm 4:15:28] [ERROR] CORTEX_M0P: Automatic Bootloader invocation failed with response....1
[2025/11/26 pm 4:15:28] [ERROR] CORTEX_M0P: Try manual Bootloader Invocation...
[2025/11/26 pm 4:15:29] [INFO] CORTEX_M0P:
[2025/11/26 pm 4:15:39] [ERROR] CORTEX_M0P: [ERROR_MESSAGE]Failed to receive expected data!
[2025/11/26 pm 4:16:25] [INFO] CORTEX_M0P: MSPM0G3507(Bootloader)
[2025/11/26 pm 4:16:25] [INFO] CORTEX_M0P: Invoking Bootloader....
[2025/11/26 pm 4:16:25] [ERROR] CORTEX_M0P: Automatic Bootloader invocation failed with response....1
[2025/11/26 pm 4:16:25] [ERROR] CORTEX_M0P: Try manual Bootloader Invocation...
[2025/11/26 pm 4:16:26] [INFO] CORTEX_M0P:
[2025/11/26 pm 4:16:37] [ERROR] CORTEX_M0P: [ERROR_MESSAGE]Failed to receive expected data!

 

Does this mean the device is locked? How to solve this error? And  why the device is locked? 

Thanks! 

Julia

  • Hi Julia,

    Could you please let customer select the "MSPM0G3507" instead of "MSPM0G3507(Bootloader)" option in the UNIFLASH and try again? If still cannot flash successfully, try to invoke the device into BSL and do the factory reset, then try to flash again, the method to enter into the BSL as shown below.

    Best Regards,
    Peter