Topic : difference of *.aof and *.hex file in release build

Forum : ST7/STM8

Original Post
Post Information Post
October 19, 2009 - 5:55pm
Guest

Hi to all

I'm using STVD with toolchain Raisonance RCSTM8 COMPILER V2.17.09.139 Lite (16 Kb code limited) and RLST7 V2.17.09.139 Lite (16 Kb code limited). My question is what are the difference of *.AOF and hex file when I do a build in Release mode?

Another question is why when I flash the hex file with RFLASHER7 the uC seems to not work at all, instead when I flash the AOF file it works?

Thank's in advance.

Franco
Replies
Post Information Post
+1
0
-1
October 20, 2009 - 11:40am
Raisonance Support Team

Hi Franco,

The AOF file contains lots of debugging information, although the HEX file only holds the ROM contents as a series of adresses/values. There is no symbolic information (at all) in HEX files.

Regards,
Bruno
+1
0
-1
October 20, 2009 - 12:06pm
Raisonance Support Team

Hi,

In theory, flashing data from the aof or hex files should give the same result.

Please make sure that when you flash the CPU with the AOF it still works after a Power-On-Reset.

If it does not work, then probably your aof file contains initialization data in the RAM, which are not put in the hex file because doing this makes no sense in the final version of the 'real application'. You should then change your source code to correct this problem.

If the application works after POR, then there could be a problem in the generation of the hex file. Or it could be in the reading of the hex file. In this case please try this: Program the flash with the aof, check that it works, read the flash to an hex (use the fill/save command in RFlasher, or use the 'D' command of STM8_pgm) and then try to program the flash using the dumped hex. That will tell us if the problem is in the generation or usage of the hex file.

Best Regards,

Vincent