Bilal Saleem

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

8 years, 8 months ago.

FRDM K64F board behaving oddly

The red LED adjacent to the the green LED on the board keeps turning and on, sometimes the green LED flickers. Also when I plug the board into my computer, i also get a fail text document which when opened, reads "TIMEOUT".

How can I fix this?

Thanks

Flickering RED LED could mean a hardfault on the board. What firmware are you running on it?

posted by Jan Jongboom 30 Mar 2016

Since this is a university project, I'm afraid I dont know much about the board. We were just given the box it came in and thats it, we just started programming.

posted by Bilal Saleem 31 Mar 2016

1 Answer

Erik -
8 years, 8 months ago.

Which OS are you using? Did you put the latest mbed firmware on it? Did you do this with windows 7 or earlier? (I am not sure this is required for the K64F, but I believe the KL25 still ships with a bootloader that does not function properly under windows 8.1 and later).

Windows 7 Enterpise. Its a university project so I didnt really make any alterations. Hope that helps

posted by Bilal Saleem 31 Mar 2016

Well that should be fine for sure. If it is a university project, do you happen to have more of them?

In the end I have always managed to unbrick my mbeds (well doubtfull my LPC1114 is ever going to be unbricked since it gets really hot, so simply damaged), but it can be quite a hassle. You can try exporting a helloworld mbed project to uvision (or another program that supports CMSIS-DAP debuggers), and try to use the debug option to erase the target MCU. If erasing works this solves issues due to wrongly programmed devices, but if the interface chip has issues not. You can try also reprogramming the mbed firmware on it. And have you tried another PC?

posted by Erik - 31 Mar 2016

How do I go about doing this

"ou can try exporting a helloworld mbed project to uvision (or another program that supports CMSIS-DAP debuggers), and try to use the debug option to erase the target MCU. "

posted by Bilal Saleem 06 Apr 2016

Right mouse button on your project in the online compiler, export. I use uvision myself (free edition), but others should also do the job. uVision is sometimes irritating that you need to find an MCU pack if the device is not supported by default.

posted by Erik - 06 Apr 2016