This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi!
Im using a conversion tool to convert a debuggers out file to intel hex and add an application CRC (after last application addr).
While the debugger flashes the out file, I can't check the application CRC on debug. I botched this by flashing the hex via command line before starting the debug, but this is not the best way.
Is there any way to convert the hex file back to out, or to any other format loadable by the debugger?
Sorry I don't know of a way to convert the hex file back to a .out file. However if the binary has already been loaded to target, are you not able to connect to it via the debugger and then maybe read off some memory locations to get what you are looking for?
That's exactly what I do.
See my postbuild steps:
1. build out file
2. convert out to hex and add application CRC
3. flash hex via commandline tool
4. start debug (flashes out file)
=> application can read the CRC even in debug mode
problems:
1. double flash access => waste of time on debugging; not the best way for flash usage
2. command line tool uses other firmware for MSP-FET430IF as CCSv5.5
=> leads to firmware update on commandline access and second firmware update on debug start