5 years ago.
FRDM K64F program upload caoses "SWD ERROR"
i have a brand new FRDM K64F. Done all as shown in the very good turorials and very helpful starting pages. All is very easy to unterstand. Having my first programm after 10 Minutes. Compile "blinky" and try to upload. But this was my last success with the new board. Everytime i uploaded a programm i get a "fail.txt" file, with the file content "SWD ERROR".
I changed Firmwarein Bootloader mode: - V0201 -> FW update > ok Version Check > ok upload blinky >"SWD ERROR". - V0202 -> FW update > ok Version Check > ok upload blinky >"SWD ERROR". - V0203 -> FW update > ok Version Check > ok upload blinky >"SWD ERROR".
I tried this with the folowing Host Systems: - Windows8.1 - Windows 7 - macosx 10.9.4
Heres the version check for the actual FW:
mbed Microcontroller Website and Authentication Shortcut >
<! Version: 0203 Build: May 30 2014 19:00:51 Git Commit SHA: ebe7dab202606d9dd80804b70ce95580d3077e23
Git local mods:Yes>
<meta http-equiv="refresh" content="0; url=http://mbed.org/device/?code=02400203B1170E424CEBF3FA"/>
<title>mbed Website Shortcut</title>
All looks ok, all is working ok but upload of a new binry is not possible!
I think that my board is in a wrong condition. Dbug mode or secure mode or something equal ...
Unfortunately I read al lot of this problem in internet but "mbed" and "fresscale" give no helpful answer to the comunity. The other threats to this problem are 3 Month old so i have only less hope toget a fast help.... but i will try it.
The pseudo help with upload the binary with the pressed reset button is nonsense so please don't post it here again. Thanky you guys in looking forward to some realy helpful answers.
Question relating to:
5 years ago.
That 'pseudohelp' is a virtually perfect method, on the original mbed LPC1768. On the K64F if you do the entire thing with reset button pressed it is just going to enter bootloader mode.
Now I don't have the K64F myself, but most boards come loaded with some kind of example code which blinks LEDs. Do you recall if that was the case on your K64F board? If yes we can rule out issues with the target MCU. If no, well then it would be helpful if someone knows if it should be the case.
I do have a K22F, so it might be on some things a bit different. However if you look at the bottom of your board, then below every jumper connector there should be a PCB connection. If this is cut there would be an issue. Is the reset jumper (three pin jumper, should be pins 1-2 connection) correct? (Dunno if that one matters, but can't hurt to check).
SWD ERROR is a pretty generic one that no communication was possible with the target. If it would be in a secure state it should give another error.
Finally: On which PC did you do the firmware update? On the windows 7 PC it should 100% sure be able to go correctly (if it gives that FW information I would consider it strange if the firmware didn't load correctly, but it needs to be something). A broken K64 is of course also an option, but in my experience it generally is something else.
4 years, 7 months ago.
Hi All, this morning I have the same problem on 2 board F401RE and F411RE.
When I plug them into usb port I can see a text file named fail.txt with SWD ERROR inside.
I've just updated the firmware but the problem is unsolved.
4 years, 7 months ago.
Just wanted to give you a heads up. Maybe you figured it out for yourself, but for anybody who has thisissue please follow these steps.
1.) Go to: https://www.segger.com/opensda.html 2.) download OpenSDA V2 3.) enter bootloader mode(hold down reset while plugging in board) 4.) paste .bin file in bootloader 4.1)at this point your red reset led should still be lit. Its okay just proceed 5.) Download J-flash Lite from here: https://www.segger.com/jlink-software-beta-version.html 6.) Select this device (MK64FN1M0xxx12 (allow security)) 7.)Download FRDM gpio and program using Jflash. 8.)Red light should go away 9.) re enter bootloader mode and upload the latest firmware for FRDM-k64f 10.) Device should now read MBED.
Hope it works for you I figured this out after reading way too many threads on the topic.
You need to log in to post a question