We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I've got a Freescale evaluation board that I'm working through for the KL02. All of the Freescale documentation is awesome, and then I jump into the example code and the world of KEIL MDK and am stunned by how there is literally no documentation whatsoever. It's like I'm on an egg hunt. I've got uVision compiling the example project and it produces an AXF file. I have no idea what to do now. Searching online I have found no information on how to convert an AXF to SREC, which is what OpenSDA wants for loading, that or a binary file. How do I get a BIN file?
Also, the debugger doesn't seem to work. I installed the "Freescale Kinetis OSJTAG Drivers V1.14" just as instructed on the Freescale website, and after installing KEIL MDK. When I try to debug or even just download the code to Flash, it doesn't see any device connected to USB. Come on guys, not even a readme file or something? Really disappointed.
Here on the forum I see someone else who had the exact same problem as me back in March, no replies. I hope I get some replied.
It's pretty odd you managed to find an old post, which you didn't cite, and I was able to find a direct hit with Google for the answer in seconds. The information to do the things you want is out there.
C:\Keil422\ARM\BIN40\fromelf.exe
There is a check button to make INTEL .HEX files, which uses FROMELF.
Motorola S-Records are atypical in ARM development, in my experience, and I've used both, though generating INTEL, MOTOROLA or TEKTRONIX hex files is NOT a complex task, neither is writing loaders to process, or translate them.
When you spend millions developing an SoC, you often have to create custom tools, scripts, generators, translators and fitters, a $5K tool from Keil is not a particularly expensive product, nor is it a silver bullet. The IDE does provide provision for pre/post link processing, user tools can compress, encrypt and package firmware images. Flexibility is the name of the game, not rigid dogma.
What does OpenSDA need for debug? Motorola S-Records don't really provide much in the way of symbolic information, unlike Tektronix hex. The ELF/AXF format provides symbolic and line numbering info, but creating binary or hex data strips all that metadata away.
>>3) Why is everything referring to ELF when the filename is AXF? I'm I supposed to convert from AXF to ELF to BIN?
Look at an .AXF file in a hex editor/file viewer some time.
Please consider that I'm working with an evaluation board here. An evaluation board that came with zero documentation from KEIL. I don't know what terms you typed into the search, but they are probably from the perspective of someone with more information. If they simply had a 2 page readme that were included with the sample code all this could have been avoided. A welcome to ARM document explaining themes like AXF/ELF, etc. The only documentation I have is from Freescale, and it uses terminology that is different than what you guys use. I'm sure things will smooth out after I get past the learning curve, but that process doesn't need to be so painful. I've never run into these sort of initial problems with any other embedded platform I've worked with. Even Microchip, who's IDE is historically lousy, it's intuitive or at the least well documented when it's not.
I've got code compiling now, but debugger still won't connect. As for what OpenSDA needs? I'm not sure what you're asking me. The drivers are all installed, it just isn't seeing the USB device in the debugger for some reason. Although Windows sees it. This may be a failing unrelated to KEIL. I'm waiting to hear back from the OpenSDA folks as well.