This topic explains the process of programming multiple Program Files using winIDEA, and particularly focuses on creating memory images and handling overlapping files.
When downloading files, winIDEA creates a single memory image that encompasses
all the files to be programmed onto the target device. These files, referred
to as Program Files, are listed in a single list within the Program Files
dialog. They are loaded into the memory image in the order specified. This
allows for sequential loading of files, enabling patches or updates to be
applied easily.
In cases where multiple files overlap in memory, winIDEA provides a warning after the download process is initiated. This warning alerts you to potential conflicts and allows for appropriate action to be taken. However, it's crucial to note that overlapping files are not common in typical use cases, except for external devices, where each device may have its own set of files.
The content of the overlapped region will be taken from the last file in the Program Files dialog list that writes to that region.
Regardless of file overlaps, the memory image is independently checked using the Image Checker tool, providing an additional layer of validation.
1. Open Hardware | CPU Options | Debugging | Optional Device Checks.
2. Enable Mirrored regions overlap option.
winIDEA checks the Program File for such overlaps and cancels the programming if the overlap is detected. Note that the Program File is also checked if this option is disabled; however, it doesn't cancel the programming, just displays the warning in the Progress window.
Check for overlaps before the actual download, ensuring smooth programming without conflicts. The Demo Mode can be enabled via Tools | Demo Mode.
Load Map option is enabled by default. You can disable it in Debug | Configure Session | SoC | Startup.
Enabling this option in Debug | Configure Session | SoC | Startup verifies the downloaded files against the target device's memory, ensuring accurate programming and data integrity.
For specific use cases, such as programming AURIX devices, it is recommended to disable HSM (Hardware Security Module) before proceeding with the download process. Then you initiate a reset for the CPU to reload changed UCB (UCB_HSMCOTP0_ORIG where you disabled HSM).
In the second stage, you execute the download of your other files which is also a file that enables the HSM again.