MSPM0G5187: J-Link Programming Questions

Sorry Team, Let me correct that the customer is use MSPM0G3507

B.R.

Eason

Hi Eason,

Can you try performing a mass erase on the MCU using UNIFLASH and rebuilding the image to see if that fixes the error?

Best Regards,
Brian

Hi Brain,

It is confirmed that after I first use XDS to perform a mass erase on the 3507, and then use J-Link to program the device, the ERROR no longer occurs.

However, when I use the J-Link programmer, I noticed that on the “Settings & Utilities” page in UniFlash, no functions are available.

Does this mean that when using J-Link, it is not possible to perform reset or erase operations through UniFlash, and that only programming and verification are supported?

Best regards,

Mike

Hi Mike,

Mike Yang2 said:

Does this mean that when using J-Link, it is not possible to perform reset or erase operations through UniFlash, and that only programming and verification are supported?

This is correct for Uniflash. However, it is possible to write scripts with the J-Link that perform the same functions.

Best Regards,
Brian

Hi Brian,

I would like to ask how to use a J-Link script to perform erase and reset operations. Thank you.

Best regards,

Mike

Hi Mike,

The following includes how to perform a factory reset: [FAQ] MSPM0C1104: How to do factory reset with J-Link.

I will reach out to another team member for more information regarding a script for mass erase.

Best Regards,
Brian

Hi Mike,

You can use Segger's J-Flash software to perform a mass erase on the device. The J-Flash User guide has more information on how to perform this erase, and other capabilities of the software.

Best Regards,
Brian

Hi Brian,

I am currently using J-Link Commander V8.96 to perform an erase operation, but I encounter the following error:

"Failed to erase sectors 0 @ address 0x41C00000 ((sector is locked)) Failed to erase sectors."

Please refer to the logs for more detailed information.

SEGGER J-Link Commander V8.96 (Compiled Dec 18 2025 16:52:18)
DLL version V8.96, compiled Dec 18 2025 16:51:21

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Dec  8 2023 20:16:22
Hardware version: V9.70
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 602718599
License(s): GDB, RDI, FlashBP, FlashDL, JFlash
VTref=3.275V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MSPM0G3507
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MSPM0G3507" selected.


Connecting to target via SWD
InitTarget() start
DAP initialized successfully.
Setting up LPM debug bits
PWR_AP_DPREC0v: 0x0079002F
InitTarget() end - Took 2.51ms
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 seems to be 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.
Setting up LPM debug bits
PWR_AP_DPREC0v: 0x0079002F
InitTarget() end - Took 3.25ms
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[5]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x84770001, ADDR: 0x00000000)
AP[1]: MEM-AP (IDR: 0x002E0001, ADDR: 0x01000000)
AP[2]: JTAG-AP (IDR: 0x002E0000, ADDR: 0x02000000)
AP[3]: MEM-AP (IDR: 0x002E0003, ADDR: 0x03000000)
AP[4]: MEM-AP (IDR: 0x002E0002, ADDR: 0x04000000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0000000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ F0000000
[0][0]: E00FF000 CID B105100D PID 000BB4C0 ROM Table
ROMTbl[1] @ E00FF000
[1][0]: E000E000 CID B105E00D PID 000BB008 SCS
[1][1]: E0001000 CID B105E00D PID 000BB00A DWT
[1][2]: E0002000 CID B105E00D PID 000BB00B FPB
[0][2]: 40402000 CID B105900D PID 001BB932 MTB-M0+
Memory zones:
  Zone: "Default" Description: Default access mode
Cortex-M0 identified.
J-Link>Reset
Reset delay: 0 ms
ResetTarget() start
DAP initialized successfully.
ResetTarget() end - Took 4.16ms
Device specific reset executed.
J-Link>erase
No address range specified, 'Erase Chip' will be executed
'erase': Performing implicit reset & halt of MCU.
ResetTarget() start
DAP initialized successfully.
ResetTarget() end - Took 3.95ms
Device specific reset executed.
Erasing device...
J-Link: Flash download: Total time needed: 0.108s (Prepare: 0.055s, Compare: 0.000s, Erase: 0.026s, Program: 0.000s, Verify: 0.000s, Restore: 0.026s)

****** Error: Failed to erase sectors 0 @ address 0x41C00000 ((sector is locked))
Failed to erase sectors.

J-Link: Flash download: Total time needed: 0.068s (Prepare: 0.038s, Compare: 0.000s, Erase: 0.014s, Program: 0.000s, Verify: 0.000s, Restore: 0.015s)
Erasing done.
J-Link>

Could you give me some advice?

Thank you.

Best regards,

Mike

Hi Mike,

This sector is where nonmain memory is located and should not be erased without being programmed before a reset. Erasing nonmain without reprogramming before a reset will result in the device becoming permanently locked.

From what I can find in the J-Link Commander documentation, the "Exec" command with "map reset" command string should restore access to all memory locations.

Best Regards,
Brian