unable to flash:-Unable to perform operation! Command failed with exit code 1

[belagallakishore]

unable to flash 

Unspecified error -1
Script processing completed.
Unable to perform operation!
Command failed with exit code 1

i am able to unlock the mcu

J-Link>unlock kinetis
Found SWD-DP with ID 0x2BA01477
Unlocking device...O.K.

but unable to ease or flash the programme

J-Link>erase
Target connection not established yet but required for command.
Please specify device / core. <Default>: MK64FN1M0XXX12
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MK64FN1M0XXX12" selected.

Connecting to target via JTAG
InitTarget()
JTAG selected. Identifying JTAG Chain...
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
JTAG Chain Identified. Connecting to DAP TAP...
Successfully connected to selected DAP TAP.
Timeout while halting CPU.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
DPv0 detected
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x001C0000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
[0][6]: E0042000 CID B105900D PID 003BB907 ETB
[0][7]: E0043000 CID B105900D PID 001BB908 CSTF
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
No address range specified, 'Erase Chip' will be executed
'erase': Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: S_RESET_ST never gets cleared. CPU seems to be kept in reset forever.
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
CPU could not be halted
AfterResetTarget()
_TargetHalt: CPU did not halt.
CPU could not be halted

****** Error: Failed to halt CPU.
CPU could not be halted
Erasing device...
CPU could not be halted

****** Error: Cannot read register 16 (XPSR) while CPU is running
Cannot read register 20 (CFBP) while CPU is running
Cannot read register 0 (R0) while CPU is running
Cannot read register 1 (R1) while CPU is running
Cannot read register 2 (R2) while CPU is running
Cannot read register 3 (R3) while CPU is running
Cannot read register 4 (R4) while CPU is running
Cannot read register 5 (R5) while CPU is running
Cannot read register 6 (R6) while CPU is running
Cannot read register 7 (R7) while CPU is running
Cannot read register 8 (R8) while CPU is running
Cannot read register 9 (R9) while CPU is running
Cannot read register 10 (R10) while CPU is running
Cannot read register 11 (R11) while CPU is running
Cannot read register 12 (R12) while CPU is running
Cannot read register 14 (R14) while CPU is running
Cannot read register 15 (R15) while CPU is running
Cannot read register 17 (MSP) while CPU is running
Cannot read register 18 (PSP) while CPU is running

****** Error: Verification of RAMCode failed @ address 0x1FFF0000.
Write: 0xA801BE00 F0009900
Read: 0x94810441 26740E24
Failed to prepare for programming.
Failed to download RAMCode!
ERROR: Erase returned with error code -1.

[Celeste_Liu]

Hello @belagallakishore ,

Thanks for your detailed log.

From the log "Reset: S_RESET_ST never gets cleared. CPU seems to be kept in reset forever." and "Reset: Core did not halt after reset, trying to disable WDT.", the root cause is the MCU cannot be halted in debug mode, which prevents erase and programming operations.

This kind of issue is typically caused by one of the following: Watchdog resets the MCU continuously after reset, RESET pin is held low or unstable on hardware or User application interferes with debug (e.g., invalid clock/PLL or early code behavior).

I recommend you try the following steps:

1. Switch to SWD interface

2. Reduce debug speed (e.g., 1000 kHz or lower);

3. Check RESET pin hardware condition:

I suppose you are using a custom board, right? Could you please check whether the RESET pin is being pulled low externally? Is there any excessive RC delay? Or any waveform instability or noise on the RESET signal? Maybe you can use an oscilloscope to observe the RESET waveform?

4. Not sure how long your SWD/JTAG debug cable is, or if there are any EMI issues. Keep the cable as short as possible.

We have Production Flash programming best practices for Kinetis K and L MCUs for your reference.

If the issue persists, please share your hardware schematic (especially reset and debug interface). I am glad to assist further.

BR

Celeste