[ABANDONED] J-Link Commander Erasing SAME54: RAMCode never stops

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] J-Link Commander Erasing SAME54: RAMCode never stops

    I may have bricked my ATSAME54P20A: I was on the way to enabling the watchdog timer, which requires setting the NVM fuses. But when it failed to run, I decided to erase the chip with J-Link Base / J-Link Commander and start over.

    However, the "erase" command times out with the message:

    Source Code

    1. ****** Error: Timeout while restoring target, RAMCode did not respond in time (PC = 0xFFFFFFFE, XPSR = 0x01000003, SP = 0xFFFFFFD8)!
    2. Failed to restore target. RAMCode never stops
    3. ERROR: Erase returned with error code -5.

    (That is a suspicious looking PC!) Any suggestions on how to get over this bump would be appreciated!

    Full transcript follows:

    Source Code

    1. SEGGER J-Link Commander V7.82b (Compiled Nov 9 2022 17:08:19)
    2. DLL version V7.82b, compiled Nov 9 2022 17:06:50
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link V11 compiled Nov 9 2022 14:34:45
    6. Hardware version: V11.00
    7. J-Link uptime (since boot): 0d 23h 48m 06s
    8. S/N: 51028480
    9. License(s): GDB
    10. USB speed mode: High speed (480 MBit/s)
    11. VTref=3.328V
    14. Type "connect" to establish a target connection, '?' for help
    15. J-Link>con
    16. Please specify device / core. <Default>: ATSAME54P20A
    17. Type '?' for selection dialog
    18. Device>
    19. Please specify target interface:
    20. J) JTAG (Default)
    21. S) SWD
    22. T) cJTAG
    23. TIF>s
    24. Specify target interface speed [kHz]. <Default>: 4000 kHz
    25. Speed>
    26. Device "ATSAME54P20A" selected.
    29. Connecting to target via SWD
    30. InitTarget() start
    31. InitTarget()
    32. Reset released!
    33. InitTarget() end
    34. InitTarget() end
    35. Found SW-DP with ID 0x2BA01477
    36. DPIDR: 0x2BA01477
    37. CoreSight SoC-400 or earlier
    38. Scanning AP map to find all available APs
    39. AP[2]: Stopped AP scan as end of AP map seems to be reached
    40. AP[0]: AHB-AP (IDR: 0x24770011)
    41. AP[1]: AHB-AP (IDR: 0x74770001)
    42. Iterating through AP map to find AHB-AP to use
    43. AP[0]: Core found
    44. AP[0]: AHB-AP ROM base: 0x41003000
    45. CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    46. Found Cortex-M4 r0p1, Little endian.
    47. FPUnit: 6 code (BP) slots and 2 literal slots
    48. CoreSight components:
    49. ROMTbl[0] @ 41003000
    50. [0][0]: E00FF000 CID B105100D PID 000BB4C4 ROM Table
    51. ROMTbl[1] @ E00FF000
    52. [1][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
    53. [1][1]: E0001000 CID B105E00D PID 003BB002 DWT
    54. [1][2]: E0002000 CID B105E00D PID 002BB003 FPB
    55. [1][3]: E0000000 CID B105E00D PID 003BB001 ITM
    56. [1][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
    57. [1][5]: E0041000 CID B105900D PID 000BB925 ETM
    58. [1][6]: E0042000 CID B105900D PID 003BB907 ETB
    59. Cortex-M4 identified.
    60. J-Link>erase
    61. No address range specified, 'Erase Chip' will be executed
    62. 'erase': Performing implicit reset & halt of MCU.
    63. Reset: Halt core after reset via DEMCR.VC_CORERESET.
    64. Reset: Reset device via AIRCR.SYSRESETREQ.
    65. Erasing device...
    67. ****** Error: Failed to erase sectors.
    69. J-Link: Flash download: Total time needed: 7.102s (Prepare: 0.117s, Compare: 0.000s, Erase: 3.981s, Program: 0.000s, Verify: 0.000s, Restore: 3.003s)
    71. ****** Error: Timeout while restoring target, RAMCode did not respond in time (PC = 0xFFFFFFFE, XPSR = 0x01000003, SP = 0xFFFFFFD8)!
    72. Failed to restore target. RAMCode never stops
    73. ERROR: Erase returned with error code -5.
    74. J-Link>
    Display All