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.
horse and cart. Is it not putting the cart before the horse to change a file that adhere to the standard in order to use equipment that does not adhere to the standard. If a "programmer" (in quotes, because calling it that is an insult to other devices with that name) can not handle .hex files that adhere to the standard, but do not go beyond, then the programmer should be fixed or trashed, not the file sorted. Every extra step you add to the process makes failure more likely. Erik