Flash programming with multiple Program Files

03-Jul-2024

This topic explains the process of programming multiple Program Files using winIDEA, and particularly focusing 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.


Handling overlapping files

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 Program Files dialog list that writes to that region.


Infineon AURIX

Use Image Checker

Regardless of file overlaps, the memory image is independently checked using the Image Checker tool, providing an additional layer of validation.

More information in the topic UCB Management.


Enable Load Map and use the Demo Mode

This allows you to 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.


Verify after download

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.


Disable HSM first

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.


More resources in winIDEA Help

Was this answer helpful?