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.
9 years, 1 month ago.
Upgrading firmware bricked my K64F?
So I'm having this problem trying to get a UART working while I have SPI going via DMA, and decided that maybe I need to update the firmware in my K64F (from 0201 to 0221). I did the update, and now I can't successfully flash a new program to the MBED disk.
I have tried reflashing the firmware in the BOOTLOADER drive, and sometimes when I try to load a new program to MBED, it writes part of the file, then I get a popup that says it can't continue. If I try to look at the DETAILS.TXT file, it says it doesn't exist (after I try to open it).
Other times after flashing the firmware, the MBED disk comes up empty, and trying to drop a file on it gives me a "Could not find this item" popup. It seems like that's the dominant result.
Any pointers would be greatly appreciated.
Regards,
- Just Gary
Question relating to:
1 Answer
9 years, 1 month ago.
You can find some... using some tools, like pyOCD to reflash your target, or jlink command line or openOCD. It might happen sometimes that cmsis-dap gets confused with locked chip.. I just reflash the target using some other tools I mentioned above to "recover" it.
Search for unlock kinetis here on mbed, you should find some pointers.
Can you share the OS you're using? Also if the reset led is on in a dim red state.
posted by Sam Grove 10 Mar 2015Arrrrgggghhhh! Sorry to cause a ruckus, but the update apparently worked fine. I tried a second K64F board (not upgraded) and got the same errors. A reboot of the Bill Box got the MBED going just fine. I'm using Winders 7, so thanks, Bill.
Now back to figuring out the UART problem, which apparently is inhibiting the SPI DMA for some reason, and all I have to do is declare the serial type....
posted by Just Gary 11 Mar 2015OK, I guess I spoke too soon. I was able to download a new executable exactly once. Now the PC does not open the MBED drive automatically, and when I open it, it is empty and not able to let me drop a new file on it.
I tried reinstalling the driver for it, but I get "This device cannot start. (Code 10)".
posted by Just Gary 11 Mar 2015I was able to drop the firmware upgrade in the BOOTLOADER drive again, but I still get no hard drive for MBED. The device manager lets me change the port number to something else, but I get no drive for either MBED. What's going on?
posted by Just Gary 11 Mar 2015Tried an original LPC1768 MBED in another USB port, it works fine. Moved the K64F to that USB port, it is working fine. Clearly, I have a Billware problem that I need to figure out. Somebody suggest a switch to Un*x, and I will accept that as the correct answer.
posted by Just Gary 11 Mar 2015