FRDM-KL82Z Board is always in Bootloader Mode

[saydin]

Hi,

I've FRDM-KL82Z board and it is always in "Bootloader Mode". I cannot convert it to FRDM-KL82Z. I use Windows 10. I try to update the debugger to JLINK firmware but didn't work. How can I fix it?

Best Regards,

[saydin]

Hi @ErichStyger ,

thank you for your answer but it didn't work for me. It connects always in Bootloader Mode and i attached a screenshoot from bootloader mode. I cannot use my board anymore. Do you have any suggestion?

Best regards

[ErichStyger]

Can you use a Windows 7 machine to update the bootloader?

[saydin]

Hi @ErichStyger 

I tried with Windows 7 Machine to update Bootloader but I didn't work. Do you have any suggestion?

[ErichStyger]

Can you share details?

I think you might have missed a step or used the wrong bootloader/firmware.

I don't have your board, so I'm not 100% what bootloader it has on it.

For the P&E or older bootloader, see

https://mcuoneclipse.com/2014/11/01/illustrated-step-by-step-instructions-updating-the-freescale-fre...

If using a V2 bootloader, you can directly program it, see https://mcuoneclipse.com/2016/06/26/how-to-recover-the-opensda-v2-x-bootloader/ or https://mcuoneclipse.com/2017/10/29/adding-a-delay-to-the-arm-daplink-bootloader/ where I shared on GitHub a fixed binary.

I hope this helps,

Erich

[saydin]

スポイラ

Hi Erich,

I could see mbed.htm when I plug-in the KL82Z Board, before I had faced Bootlader issue. I was using windows 10. Now I use Windows 7.

I go to the website http://www.nxp.com/opensda  and choose my board, follow the steps. I tryied all binaries but doesn't work. I cannot understand where I make mistake. I also tried your patched binary. It does not work for me.

What kind of details do you want me?

Thanks

[saydin]

Hi @ErichStyger 

No not yet, I try to find a Windows 7 PC Will be KL82Z fixed after updating the bootloader? Is that the Problem?

[ErichStyger]

A Win7 machine is the easiest way to update the bootloader.

If you have an old bootloader on the K20 of the board, and using Win10 (or Win8), then it will always trigger it to get into bootloader mode.

So you have to update the bootloader with the links I have provided with a bootloader which is Win10 aware. After that you have to load the debug firmware of your choice (J-Link, P&E or CMSIS-DAP).

Unfortunately I don't have your board, so won't be able to check it myself what exactly is on the board.

I hope this helps,

Erich

[saydin]

Hi Erich,

This is my first experince with FRDM board and at my first day I`m stuck on bootloader mode. 

Should I buy LPC-Link2 to update bootloader? Thanks your help.

Best Regards

[ErichStyger]

having an LPC-LInk2 at hand is always a good thing (or a SEGGER J-Link or P&E Multilink). But I cannot tell you if this will help, because you only will be able to flash the K20 if you have a OpenSDA v2.x board. The OpenSDA v1.x have a locked K20 on it, and that one is blocked for debugging.

[ErichStyger]

Hi @saydin ,

I don't have your board, but I think it is the same thing as for other FRDM boards, if they have an older boodloader on it and if you use it with Windows 10. Bottom line is that you need to update the bootloader, see for example https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/ .

The above article describes a way how to disable a service, so this might do the trick for you.

If you happen to have a Windows 7 machine around: that's the easiest way for sure (I keep a Windows 7 laptop around just for this use case).

I hope this helps,

Erich

[bobpaddock]

Erich, you might want to add this note, as I just ran into it recently:

When the storage Service is turned off, the Microsoft Store application does not work.

The Store gives a strange error with no connection at all to the Storage Service.
Some updates come vis the Store update and not Windows Updates.

So I end up turning the Storage Service on when using the Store then have to turn it back off, to not brick boards.

[ErichStyger]

Hi Bob,

many thanks, note added.

Erich