Verification of Memory Addresses
At the end of the build process, Ginmake can be used to check addresses between the firmware build and the resultant GIN file or ecudef. The firmware’s linker map is compared to the address map held in the GIN file, and errors will be raised for any address mismatches between ginmake calculated addresses, and linker generated addresses.
Address mismatches can sometimes arise from compiler optimisations. If using optimization, it is recommended to use -fno-toplevel-reorder to avoid re-ordering of global variables. Alternatively it may be possible to use structs instead to ensure ordering.
Address verification can be started using the command line options –verify-mapfile-gin=ginpath and –verify-mapfile=mapfilepath for the specified GIN and linker map. If no GIN is supplied, the most recent GIN will be used. The linker map file is mandatory.
For a full report of the items checked, specify the –verbose command line option.
GCC Section names must be associated with [SEGMENT] definitions (or in Simulink options file). It is possible to specify a fixed physical address of a segment. If not specified then ginmake will attempt to deduce this from the map file.