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.
10 years, 4 months ago.
KE06 port is failing to load application.
I am working on creating a port for the FRDM-KE06. I compiled a CMSIS-DAP application that loads onto the interface chip by following the steps on the following link (https://developer.mbed.org/handbook/cmsis-dap-interface-firmware) When I cycle power on the board it comes up as MBED in windows explorer. Next, I created a simple blinky application while following the instructions on the following link (https://developer.mbed.org/handbook/mbed-SDK-porting). When I drag the application onto the MBED drive (the board), it creates a Fail.txt file with "RESERVED BITS" inside.
What could cause this? Is it most likely an issue with the CMSIS-DAP application or the Target application?
Thanks!
RF
1 Answer
10 years, 4 months ago.
Check the binary, is at 0x400 the correct values for the reserved bits? 16 bytes there are dangerous ! I would check if the binary is correct first.
So you did some progress there with cmsis-dap interface for the KE06 ;)
How do I know what the correct values for the reserved should be? And what should I use to view and edit the bin file?
I think I got the cmsis-dap interface figured out... I'll know for sure once I can get an application on it!
thanks,
RF
posted by 18 Jun 2015Check cmsis-dap sources, there is that check done for that region. I recall its just default values which are in the reference manual.
I use my editor, sublime does show binary files. But for this , use python to read bin and show 16 bytes at 0x400
posted by 18 Jun 2015I use notepad++ with hex editor plugin for that also works good.
Quick check on old firmware I still had on my PC shows for both KL25 and K22F:
ff ff ff ff ff ff ff ff ff ff ff ff fe ff ff ff
So that is probably what you are looking for :).
posted by 18 Jun 2015Just to be clear, when referring to the binary file are you talking about the output from make.py (blinky.bin) that is loaded onto the target chip, or some other file?
posted by 18 Jun 2015I updated the binary file (0X400 was NOT right) however I am still getting the same results... any thoughts?
posted by 18 Jun 2015I checked the binary and updated 0x400 to ff ff ff ff ff ff ff ff ff ff ff ff fe ff ff ff as Eric suggested. Same result.
I looked up “Reserved Bits” in the CMSIS-DAP source code and found that it is thrown in two places. I changed the text for one of them to narrow down the problem and found that it is getting thrown around line 993 of usbd_user_msc.c. I have tried to chase this down but have thus far been unable to figure out what is going on.
Does anyone have any more ideas on what's going on here?
Thanks!
RF
posted by 22 Jun 2015