Recovering a RPK from a weird state

[joseph_reveane]

Hi,

My RPK device is in a weird state :

- the two LEDs on the right up corner remain on (blue and orange (may be) )

- when I plug the RPK kit on the docking station, the disk mount moves from IOT-DAPLINK to maintenance

I can't really tell how I ended up getting the RPK node in this state but I didn't find any solution

to get it back with its default factory FW.

Is there an easy way to move back the RPK node in a "normal"  and usable state ?

Thanks for your help.

Regards.

[frq05186]

:smileysad:

Hi Joseph,

For the time being I rate HW failure likelihood as extremely low.

Here is why:

   - The LED behavior indicates the KW41Z is not booting.

   - KW41Z not booting = KW41Z not properly intialized. It then keeps the reset pin on the docuking station down, which in turn explains why you are always seeing the maintenance mode on the docking station.

When you are chainging the switch position to KW41Z you are 'disconnecting' the KW41Z reset pin from the docking micro and it is normal you are no longer in Maintenance mode (as doing this, you left K64 only driving the reset pin)

I am now a bit lost on the status of your device. When you unplug it from the docking station and perform a reset, do you sitll see NXP and Atmosphere splash screen, with the blue and white diodes continuously blinking?

[joseph_reveane]

Hi Eric,

When I reset the device with SW5, the 2 LEDS (blue and white) get switched ON.

There is no splash screen displayed.

Regards.

/joseph

[frq05186]

Ok - you likely need to reflash everything including bootloaders - Théeophile is preparing a video for that, will be faster and clearer than writing long text...

The video is already shot but we nned to do some post processing so it fits the 50Mo attachment limit.

Will be posted before end of tomorrow.

Eric

[estephania_mart]

Hello, 

Could you please try reflashing the KBoot in each of the devices? After that could you please load the OOB demo just to verify it ? 

Regards, 
Estephania 

[joseph_reveane]

Hi Estephania,

Unfortunately not and this is indeed what this thread is all about: I'm not able to get the device back to a "Factory" state.

Regards.

/joseph

[frq05186]

Hi Joseph,

Yes -try this one:

https://community.nxp.com/message/1041174

The LED behavior seems to indicate that KW41Z Inside the kit is not booting, certainly because the memory image was altered.

[joseph_reveane]

Hi Eric,

Thanks for your email.

Unfortunately, I had tried that already but without any success.

Indeed, using this procedure, the 2 LEDs turn on again as soon as I release the SW5...

Is there any other alternative to get the device back on line using the Docking station ?

Regards.

/joseph

[frq05186]

Hi Joseph,

 'the 2 LEDs turn on again as soon as I release the SW5'

   ==> The last switch you should release is SW2 not SW5 so I suspect you are possibly not following the recommended procedure.

Please check the video at he bootom of this post:

https://community.nxp.com/thread/481369

There are 3 ways you can use to recover, depending on the starting point. From the easiest to the more complex:

1. Flashing a binary via MSD as if you would update the programs (no docking needed)
   1. Chapter 4.1.3 in user guide <== This is what I recommend to you for nowThis assumes you have the production binaries, which I will attach to this postThey must be flash one after the other
2. Recovering K64 and KW41Z from the external memory (no docking needed)
   1. Chapter 4.1.1 in user guide
   2. Chapter 4.1.2 in user guide
3. Flashing K64 and KW41Z binaries with a docking station
   1. Chapter 4.3.2.6 in user guide

[joseph_reveane]

Hi Eric,

Thanks a lot for spending time on this issue.

 I had a look at the video and I believe that I was pushing/releasing the SW5/SW2 switches with the proper timing.

I've retried this procedure several times but without any success.

I was not able to get the device to enter in MSD mode either for the K64 or the KW41Z MCU (chapter 4.x.x).

I've tried the docking station way as decribed in Chapter 4.3.2.6:

- configured the docking station to debug K64F

- Kept the MK64 Reset Button of the docking station while turning the Power switch On

- copied the SEGGER OpenSDA_V2_1.bin file into the "MAINTENANCE" disk

- the copy went fine, the MAINTENANCE disk got umounted

- BUT the MAINTENANCE got mounted back

- the JLink Commander Tool is unable to find the USB device to open

I've tried the procedure several times, without any luck.

So, as you mentioned that the issue was coming from the KW41Z MCU, I've tried to apply the second part of the procedure:

- configured the docking station to debug KW41z MCU

- Kept the KW41 Reset Button of the docking station while turning the Power switch On

- copied the SEGGER OpenSDA_V2_1.bin file into the "MAINTENANCE" disk

- the copy went fine, the MAINTENANCE disk got umounted

- fired the JLink Commander Tool:

SEGGER J-Link Commander V6.40 (Compiled Oct 26 2018 15:08:38)
DLL version V6.40, compiled Oct 26 2018 15:08:28

Connecting to J-Link via USB...O.K.
Firmware: J-Link OpenSDA 2 compiled Oct 10 2018 16:29:51
Hardware version: V1.00
S/N: 621000000
VTref=3.300V

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

Connecting to target via SWD
InitTarget()
Found SW-DP with ID 0x0BC11477
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: 0x04770031)
AP[1]: JTAG-AP (IDR: 0x001C0020)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xF0002000
CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
Found Cortex-M0 r0p1, Little endian.
FPUnit: 2 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ F0002000
ROMTbl[0][0]: F0000000, CID: B105900D, PID: 001BB932 MTB-M0+
ROMTbl[0][1]: F0001000, CID: B105900D, PID: 0008E000 MTBDWT
ROMTbl[0][2]: E00FF000, CID: B105100D, PID: 000BB4C0 ROM Table
ROMTbl[1] @ E00FF000
ROMTbl[1][0]: E000E000, CID: B105E00D, PID: 000BB008 SCS
ROMTbl[1][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT
ROMTbl[1][2]: E0002000, CID: B105E00D, PID: 000BB00B FPB
Cortex-M0 identified.
J-Link>erase
Erasing device...
Comparing flash [100%] Done.
Erasing flash [100%] Done.
Verifying flash [100%] Done.
J-Link: Flash download: Total time needed: 3.405s (Prepare: 0.028s, Compare: 0.000s, Erase: 3.369s, Program: 0.000s, Verify: 0.000s, Restore: 0.007s)
Erasing done.
J-Link>loadbin kboot_kw41z.bin 0
Downloading file [kboot_kw41z.bin]...
Comparing flash [100%] Done.
Erasing flash [100%] Done.
Programming flash [100%] Done.
Verifying flash [100%] Done.
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (16384 bytes)
J-Link: Flash download: Total time needed: 0.723s (Prepare: 0.085s, Compare: 0.015s, Erase: 0.104s, Program: 0.441s, Verify: 0.014s, Restore: 0.061s)
O.K.
J-Link>exit

Then, nothing else happened !

I've tried to unplug the RPK device from the Docking station but the LEDs remained on for ever...

Could it be an HW failure ?

Thanks for your help.

Regards.