• State
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 86 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM0G3505-Q1: Trouble Writing Memory Block

Alok Bardhan
Prodigy 10 points

Part Number: MSPM0G3505-Q1

Hello,

I am trying to flash a custom board having a SBC(TLE94613ESV33XUMA1) connected to the microcontroller(M0G3505QRHBRQ1) via SPI which drives two LED drivers(MPQ3324GRE-AEC1-P).
The SBC has a watchdog, so for the very fisrt time when I am flahing the G3505, I supply 3.3V to Test pin 10 ensuring the watchdog is disabled during flashing.

However, in many scenerio I get this error
"[9/21/2026, 1:54:51 PM] [INFO] CORTEX_M0P: GEL Output: Memory Map Initialization Complete[9/21/2026, 1:54:52 PM] [ERROR] CORTEX_M0P: Trouble Writing Memory Block at 0x2288 on Page 0 of Length 0x8: Flash download failed! ...[9/21/2026, 1:54:52 PM] [ERROR] CORTEX_M0P: File Loader: Verification failed: Target failed to write 0x00002288 "

And after that I am not able to connect the target and getting this error
" [9/21/2026, 1:54:56 PM] [ERROR] CORTEX_M0P: Error connecting to the target: Could not connect to target.[9/21/2026, 1:55:00 PM] [ERROR] CORTEX_M0P: Error connecting to the target: Could not connect to target. "

Why the flashing is failing, could you please provide some support?

 

  • 0
    TI__Expert 8010 points

    Hi Alok,

    It sounds like the flash procedure is getting interrupted, causing the CPU to lock up due to an incomplete/invalid application image. Can you verify the MSP's power and nRST lines are high for the full programming duration and that the SWD signals aren't being interrupted?

    Additionally, can you run the Boot diagnostic read script in CCS? An output code of 0x7 would confirm the CPU has indeed locked up.

    Best Regards,
    Brian