This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to (easily) flash a custom .hex file with debugger?

Aina R over 6 years ago

Hello,

I am developping on a firmware using a bootloader which verifies main application's CRC prior to let it start. To do this, I am generating an extra .hex file with data for bootloader added to the .hex file created by Keil.

I thought I just had to rename my .hex file with data to the name of the one generated by keil... But Keil's debugger is loading the .axf file, not the .hex one :-(

The only workaround I found was to load my .hex with data with another flash programmer, and then start debugging with Keil to have debug symbols.

Does anyone know how I could do this directly with Keil ?

Thanks a lot in advance!

Top replies

Aina R over 6 years ago in reply to Aina R +2 verified

I asked to Arm's support and got the reply: the .ini file shall be called through the "Utilities" tab (which is called at flashing time), not from "Debug" as I did. Using Utilities tab solved my trouble...
Westonsupermare Pier over 6 years ago +1 suggested

The tools I built can generate .HEX and .ELF(AXF) files when they checksum/sign the images. I seem to recall that the debugger, and scripting, has a LOAD command that will take .HEX files, although admittedly...
Ron Wedge over 6 years ago +1

I think you can go to Project -> Options For Target ->Output tab, and change the name from "My_project" to. "My_project.hex" - that should load the hex file. Otherwise, you can write a simple script...