MK82F board stuck in reset

cancel
Showing results for 
Search instead for 
Did you mean: 

MK82F board stuck in reset

77 Views
Contributor I

I have a MK82F board. I had previously been using segger JLinks to load programs on to the board and debug.

I attempted to re-flash a debugger binary on to the K82F board in order to rule that out in the search for a bug. However, in doing this, the board now has D3 lit-up in red at all times. I have read this means it is stuck in a constant reset state. 

I have tried reloading the OpenSDA bootloader on to it, but no luck there. In DETAILS.TXT within the board, it says I have "Bootloader Version: 0244". I also tried loading updated firmware on to it. No help there.

If I enter the board in MAINTENANCE mode, then I see only the small green light (D1). This leads me to believe the board is recoverable.

When I run JLinkExe, I can connect to the board, but only while it's not in MAINTENANCE mode. Once connected, I get this output:

Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.
Found SW-DP with ID 0x2BA01477
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
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.

I can run "exec EnableEraseAllFlashBanks", but if I try to run "unlock kinetis", I get the following:

Found SWD-DP with ID 0x2BA01477
Unlocking device...ERROR: Read from DP/AP register failed!

If I try to run "erase", I get:

**************************
WARNING: CPU could not be halted
**************************

Erasing device...

**************************
WARNING: CPU could not be halted
**************************


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


****** Error: Failed to prepare for programming.
Could not preserve target memory.
ERROR: Erase returned with error code -1.

Let me know what to try or who to contact... Thanks

0 Kudos
1 Reply

6 Views
NXP TechSupport
NXP TechSupport

Hello Nicolette,

Hope you are doing well.

You may retry the steps to unlock and erase the microcontroller in the following post:

Unlocking and Erasing FLASH with Segger J-Link | MCU on Eclipse 

However, from the first line in your description it states that :

Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.

If this is true then it will not be recoverable. 

You can try the following to check if read protection is set by reading the address 0x0 - 0x1000. If you are not able to then it is set. As you are not able to unlock the kinetis then this means that mass erase is disabled as stated. This would be the last recovery option. If you have secured your device with mass erase disabled, then the device is bricked.

Best Regards,

Sabina

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

----------------------------------------------------------------------------------------------------------------------- 

0 Kudos