topic Re: Compare New .s19 with Old .s19 - Not matching, _Date_ Code function? Please Help in CodeWarrior for MCU

Compare New .s19 with Old .s19 - Not matching, _Date_ Code function? Please Help

AlexanderLeenus — Wed, 18 Aug 2010 16:24:25 GMT

In my code I am using a function called "__DATE__" .

The build date is inherently connected to the .S19 file.

After somedays I was repeated the build and compared the new .s19 file with the original .s19. Obviously, the dates will not line up - 8 bytes.

But more than 8 bytes are changing and different.

Expectation : It should not be different anything other than date (8 bytes). In my case more than 8 bytes...Please help

Re: Compare New .s19 with Old .s19 - Not matching, _Date_ Code function? Please Help

kef — Wed, 18 Aug 2010 17:48:13 GMT

Why only 8 bytes? __DATE__ should evaluate to string, "18 Oct 2010" IIRC. That's more than 8 bytes.

Re: Compare New .s19 with Old .s19 - Not matching, _Date_ Code function? Please Help

Emac — Mon, 23 Aug 2010 22:35:48 GMT

copy of other post, just in case:

Be sure to turn of the inclusion of the Timestamp (default is on) by changing the linker properties and adding the following environment variable setting:

-EnvINCLUDETIME=OFF

Edit>[your tool] Settings>Target>Linker for [HC12|HC08]>Command Line Arguments

just add -EnvINCLUDETIME=OFF

This may help in the binary comparison. All the above comments are correct as well regarding space for the _DATE macro.

My suggestion is to try it first without the date macro, get that to compare consistently, and then work in your _DATE macro