winIDEA Help

Target Files will be loaded into the target system on explicit user request. Usually this is needed if a file can only be loaded after the application has initialized the system to a state which allows programming. Typically these will be Motorola S, Binary or Elf files. To program FLASH devices which are not memory mapped (SPI, eMMC,...) go to Hardware / Options / Programming.

 

Target download loads selected files defined in the Target Files page depending on the setting via Edit button.  A file can be executed on a demand any time during the debugging process. If you want to load a file at a certain stage during a debug session (simulation, testing,...), you should:

1. Specify any file that you will be using via the Add button.

2. Select the file added to the list and confirm.

3. Load the file by clicking the Debug menu / Target download / <appropriate file>. Note that this menu only existing in the main core.

 

To configure Target Files select Debug / Configure Session / SoC / Add or Edit button / Target Files page. To open File options dialog select the file and click Edit.

 

 

Add - Specify all files which you will need to load manually when the session is already active.

Edit / Remove - Edit / remove Target File(s).

Add build output file - Automatically include the build output file.

 

 

Use cases

Target Files are useful to:

•Restore a previously saved Debug state/context from memory

•Execute RAM or Flash dump and patches during runtime

•Specific use cases, e.g. Supervisory Flash (SFLASH) for Cypress Traveo II devices

 

 

Core-specifics

Target files can only be loaded through the workspace of the main core (Debug / Target download) and all the cores must be halted before performing the target download. The Memory Window of the main core workspace refreshes its contents immediately, however the Memory Windows of secondary cores workspaces still display the memory contents of the moment that the core was last halted and are not refreshed until single step/run-stop.