I have to use command line flash programming for a project . So I created a fake project similar thand the original one. The problem is that I'm using a .ini for flash downloading to program a modfied .hex and not the axf file. If I'm using command line , the .ini is ignored and uv4 want to flash an .axf file ... How can I solve this problem ?
It's a part of a process where the hex code is patched with various CRCs and version numbers . Thats' why .hex are used with srec tools.
That explains why you're producing a modified .hex file. It does not explain at all why you so aggressively insist on using a software development tool for what is obviously the job of a production programmer. Or to put it in a different way: if you're not going to be doing any debugging anyway, why even use the debugger?
That pain you feel is from using a screwdriver to do what is the hammer's job.
I absolutely don't want to use ulink as a production flashing tool. I just want to be able to program my firmware from Eclipse IDE . In an ideal world I would like to debug from Eclipse too , but the eclipse plugin does not work.
The Keil tool is happy to program a hex file without using an ini file.
I have a "Generic Project" that is called burnhex.uvprojx
The Name of the executable in this project is burnhex.hex. This is the name of the file you want to burn (and yes, it can be and is a hex file)
IF if run this from the command line "UV4 -f burnhex.uvprojx" it burns the burnhex.hex file to the board. Is this what you want?
Ok , thanks, I'll try !!. I just hop the text field manages relative/absolute path and not only the name of the file to program.