6 years, 10 months ago.

K64F firmware problem

I had a firmware installed on my K64F board, I don't know exactly which version it was, but the last time I updated it was 2 years ago. The board was working fine until yesterday, when I noticed it wouldn't write anything to the serial port, so I decided to update the firmware. I have followed again the instructions on this page: https://developer.mbed.org/handbook/Firmware-FRDM-K64F and I have tried to upload all the CMSIS-DAP and DAPLink bootloaders I have found on this page: http://www.nxp.com/products/software-and-tools/run-time-software/kinetis-software-and-tools/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#FRDM-K64F and on the internet.

Some of the firmwares get uploaded and seem to be working, but when I try to upload any program and press the reset button of the board, all I get is the red Status LED. Does anyone have an idea how to fix this problem?

1 Answer

6 years, 10 months ago.

Hi Lucas,

From the page you posted:http://www.nxp.com/products/software-and-tools/run-time-software/kinetis-software-and-tools/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#FRDM-K64F

You need to install the following and only firmware onto the device:http://www.nxp.com/assets/downloads/data/en/ide-debug-compile-build-tools/0243_k20dx_frdmk64f_0x5000.zip

DAPLink rev0243 - works with default CMSIS-DAP bootloader (Download Binary / Source Code)

To install the firmware you must, hold down the reset button on the device, then plug it in, then drag the binary onto the drive that appears, once this is done simply repower the board!

In terms of why you are getting a Red LED this can be due to the fact the code actually running on the device is incorrect and causing an internal issue, have you checked your pin declartions for whatever you are using are correct, such as correct I2C pins and correct SPI pins etc?

Regards,

Andrea, team mbed

Thanks for the reply Andrea.

As I said, I had already done all of this you told me to do, including upload DAPLink rev0243 bootloader. And have followed exactly these steps to perform the upload, as had done other times before.

But anyway I gave it another try, just to be sure, and I still have no success. The bootloader gets uploaded, but the board is still behaving strangely. After rebooting the board no status LED is on and when I upload a program and press the reset, only the red status led turns on.

About the code I'm running, I don't believe there is any error on it, since not even a simple "turn on led" code is working. Do you have any other suggestions?

posted by Lucas de Mamann 07 Jun 2017

Hi,

Is J25 connected between 1 and 2?

Andrea

posted by Andrea Corrado 07 Jun 2017

Hi,

yes, pins 1 and 2 are connected on J25

posted by Lucas de Mamann 07 Jun 2017

When you say red status LED which are you referring to? Posting a picture will help :)

Regards,

Andrea, team mbed

posted by Andrea Corrado 08 Jun 2017

The one right on the side of reset button. What used to happen when it was working, was the green LED (which is close to the red LED) would stay on all the time. But now it stays off, it only blinks when I'm transferring a binary.

Here is a picture of what is happening https://drive.google.com/file/d/0B6Pp3UCqZVo-OG5QVkU4QjVBQzQ/view?usp=sharing

posted by Lucas de Mamann 08 Jun 2017

It sounds to me like an error with the interface chip.

Have a look here:

https://mcuoneclipse.com/2014/04/19/recovering-frdm-k64f-mbed-board/

Could you try looking at topics around this, or try other firmware?

Regards,

Andrea

posted by Andrea Corrado 08 Jun 2017

These days I'm not having much time to work on my board. But as soon as I'm able to have a look on this again, I'll post some answer for the suggestions you gave me.

Thanks

posted by Lucas de Mamann 13 Jun 2017