Hex file failure

You'll really have to be a good deal more specific than this before it becomes a sensible project for anyone else to look into it:

What does "older" project actually mean? How old is it, and what uV version was it made with originally?

What exactly does "the hex file is incorrect" mean to you?

And even if the failure is for real, why do you consider a "rebuild all", once, an inappropriate burden to fix it?

You'll really have to be a good deal more specific than this before it becomes a sensible project for anyone else to look into it:

What does "older" project actually mean? How old is it, and what uV version was it made with originally?

What exactly does "the hex file is incorrect" mean to you?

And even if the failure is for real, why do you consider a "rebuild all", once, an inappropriate burden to fix it?

Assume you have two projects A & B

Load project A.
Compile -> failure using the HEX file in the controller.
Recompile A -> Hex is working in target

Load project B.
Compile -> failure using the HEX file in the controller.
Recompile B -> Hex is working in target

Load project A.
in a file type a "space" anywhere to modify the file. (no code changes!)
Compile -> failure using the HEX file
Recompile B -> Hex is working fine.

and so on ....

This can be repeated over and over .....

The Hex file is incorrect.
how, what, details, please

Erik

Have you saved each HEX file in this progression so you can compare the ones that work to the ones that don't work?

Jon

The first time you compile... the hex file is empty ....

So controller starts unwanted EMPTY code!

Kind regards

The hex file is created by the Object-to-Hex converter from the Linker's Absolute Object module output.

Is the Absolute Object module OK?
(you can load it into the Simulator)

Are you sure there's no error, warning, or other messages?

i'm using µvision3 and i made the experience that in case of using an folder for my created objects with a path longer than 7 steps (i mean c:\programm\keil\arm\gnu\examples\sensor\flash...) the hex file is only created once. when i delete the hex file and compile my changed code again, it creates all c files correctly but not the hex file. it is only created again when i restart my computer. after i selected a shorter path everything works fine...

You have spotted the problem!

"c:\programm\keil\arm\gnu\examples\sensor\flash"

Remember that the GNU tools originate in UNIX land; I have seen this sort of "oddity" before (not under Keil) where GNU does not totally understand the ways of Microsoft... :-(