Reference
Images, symbols and provenance
Choose the output that belongs to the intended build.
An ELF may contain executable sections, debug symbols and source paths. BIN and HEX usually serve programming workflows with different address/metadata behavior. A linker map explains placement; it is not an executable image.
Always associate an artifact with source revision, native configuration, build directory and tool versions. For multiple presets, cores or bootloader/application images, do not let file discovery silently choose the first match.
Prescaler refuses ambiguous artifact discovery in supported paths. Complete preset/multi-image provenance is still an integration boundary: explicitly select the image when automatic association is unavailable.
For debugging, use symbols from the image actually running. For release packaging, keep the manifest and compatibility information with the output. File modification time alone is not proof that an image matches the current source.