FRDM-KE04Z always starts in Bootloader-Mode

[Stabsauger]

Hello,

i´ve got a FRDM-KE04Z Devboard for getting used to the programming of Kinetis K MCU with MCDXpresso. Later i will use one of these controllers for a student research projekt.

Problem is:

The devboard always starts in Bootloader-Mode. In Windows i get a MSD named BOOTLOADER with 4 files.

The LASTSTAT.TXT is filled with "Programming... ". The green LED is flashing a few times with a break of like 2s. Refering to the manual this means error.

What i tried:

Update openSDA firmare by copying BOOTUPDATEAPP_Pemicro_v111.SDA in the MSD.

Update openSDA Programm by copying MSD-DEBUG-FRDM-KE04Z_Pemicro_v118.SDA in the MSD.

The behaviour stays the same. Does enyone have some tipps?

Im a beginner to NXP Products so maybe the solution is quite simple and a just dont get it.

Thanks.

[Stabsauger]

I solved the problem by updating the bootloader using Windows 7.

Now its working fine as a debugger.

Thank you.

[Robin_Shen]

Hi Stabsauger,

SW1 is the TARGET RESET AND BOOTLOADER PUSH BUTTON. If you didn't press it and OpenSDA is always in Bootloader-Mode, then the low voltage signal is from RESET_b pin of KE04.

If you don't have an external debugger, I'm afraid you'll need to modify the circuit.
for example:
Remove R35 and use J5 to isolate the low voltage to avoid putting OpenSDA into Bootloader-Mode when powered through J6.
Or remove R11, R12, and make KE04 get power later than OpenSDA through J9.

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[Stabsauger]

Thank you for your fast reply.

I removed R35. Unfortunally this changed anything.

Whats confusing for me is that the pin 1 of J5 is now at 1.5V. It gets pulled down to 0V by pressing SW1. What about the 1.5V? Shouldnt this point be pulled up to 3V by the 10k resistor?

Nevertheless, the openSDA controller should not start in the bootloader now, right?

Any other suggestions?

[Robin_Shen]

The low voltage is from RESET_b pin of KE04(the KE04 is resetting). If the voltage of pin 2 J5 is 3.3v, then you should able to make the OpenSDA exit Bootloader-Mode. refer: Recovering OpenSDA Boards with Windows 10 

After recover the OpenSDA, you can connect the J5 and program KE04.