When I create a hex file for a C file the addresses are not in order. Is there an option in uVision to make sure they are in order? The addresses are fine when I use an assembly file.
There is no requirement that the HEX file records be in address order. Jon
The author did not state that the addresses should be in order. He specifically asked if there was such an option. Please answer the question.
" There is no requirement that the HEX file records be in address order." Except for some PROM burners. Erik PS the file can be sorted as follows: Use your favorite editor (mine is CodeWright) to cut the columns before the address and relocate them at the end of the line. Then put XXX in front of the last line. Then use DOS sort to sort the file. Use the editor to bring the characters back to the front and remove the xxx.
Beware of the record types (e.g. 02) that change the segment. In such a case, you can split the hex file into subfiles and sort the subfiles. Also, some programmers allow output to a file. In such a case, the output hex file is sorted.
There is no requirement that the HEX file records be in address order." Except for some PROM burners. Please name these brands we can all avoid buying one of them. Who wants a PROM burner that is not compatible with the Intel HEX File standard? :-) Jon
The author did not state that the addresses should be in order. He specifically asked if there was such an option. Please answer the question. OK - Here's the original question. When I create a hex file for a C file the addresses are not in order. Is there an option in uVision to make sure they are in order? The addresses are fine when I use an assembly file. There is no option in uVision2 that checks the contents of a HEX file to determine if the records are in order. Jon
TaskLink software for Data I/O Optima won't take the hex file that addresses are no in the order.