Hi,
I have problems with my Hex file generated by uVision 4.
My original project built in uVision V1.31 was generating an Hex file to work on a 80C251SB16
Now that I have rebuilt my project with the same code files in uVision V4, there seems to be much more options to input for creating the target.
With the default target options (as used to be done in V1.31) I get Linkage erros, now by fixing these by tweaking the options (Memory model, code rom Size and External memory adress) I manage to generate an Hex file but it does differ from the original one created in V1.31.
Question is: Is it normal for an Hex file to differ when created with different uVision versions ?
Obviously the new Hex file won't work when implemented on ROM, is this just a matter of getting the right target options or do I get something wrong somewhere ?
"My original project built in uVision V1.31"
That is very, very old - isn't it?!
"in uVision V4, there seems to be much more options"
Yes, that does tend to be the case with any software update!
"Is it normal for an Hex file to differ when created with different uVision versions ?"
I presume that you are not only using the much newer version of uVision, but also the corresponding much newer versions of all the other tools - compiler, linker, etc?
Yes, it is perfectly normal and to be expected that different tool versions will produce different outputs - for any tools.
And, when the version difference is as great as this, one should expect significant differences.
This is why changing tool versions during an established project should never be assumed to be a trivial exercise.
Yes, it's quite common to not be able to recreate the same identical output, when having the C compiler changed. In case of Keil, the linker is also a big part in the decisionmaking.
"bviously the new Hex file won't work when implemented on ROM, [...]"
Why "obviously"?
"Obviously" otherwise if everything had worked perfectly, I guess I wouldn't have posted a thread.
Yes you are very right and it's not at all a trivial exercise to upgrade a (very) old project with newer tools.
However my main problems seems to be mainly (I hope) beginner's stuff (as I am) since good progress was made when I used the FIXDRK directive that was eventually needed for the 80C251SB. However I am still battling to understand better how to define the Target options and getting the right settings, especially in mapping memory spaces. If someone has some kind of Application Note on this I'd be very grateful.
Thanks for your replies
I trust someone has considered (or is considering) whether this is worth updating at all...?
"I am still battling to understand better how to define the Target options and getting the right settings, especially in mapping memory spaces."
What's so puzzling?
Do you have a particularly complex memory setup?