Download Files

Debug ›› Debug Menu ››
Parent Previous Next

winIDEA IDE features two types of downloads:

'Debug' Download often called Download

Target Download


Download

Download loads files defined in the Download Files tab.


Target Download

Target Download loads files defined in the Download Files or Target Download tab depending on the setting in the Target download field in the Options tab. Also, a file defined in the Target Download tab can be executed on a demand any time during the debugging. If the user wants to load a file at a certain stage during debug session (simulation, testing,...), he should:

specify any file that he will be using, in the 'Target Download' list.

at the desired time, the file to be loaded should be selected and loaded by clicking the 'Download' button in the 'Target Download' dialog.

The development system and target application requirements dictate, which download type needs to be used.

Normally, beside the code, a file contains debug information, which is generated by the compiler/assembler and allows high-level source debugging. To be able to use a high-level source debugging, the user needs to instruct the linker to output the debug information beside the code. WinIDEA supports most of the existing debug formats. Of course, binary, Intel or Motorola hex files without the debug information can be loaded as well.


Loading files on debuggers with overlay emulation memory

On In-Circuit and Active emulation systems, Download loads files into the overlay emulation memory, while the CPU is held in reset. The debugger loads files directly into the memory bypassing the CPU. Thereby, only overlay emulation memory is accessible by the Download.

Target Download is used when it’s necessary to load the files to the target (writable) memory or into the internal CPU memory other than the internal flash or ROM, for instance RAM or EEPROM. If some of the memory is not writable out of the CPU reset, the user needs to add an initialization (CPU configuration) sequence, which is carried out before the Target Download. The CPU being emulated or its emulation substitute (e.g. bondout) resides on the development system and carries out Target Download. Thereby all CPU memory resources, including overlay emulation memory, are accessible by the Target Download.


Loading files on on-chip debuggers (no overlay emulation memory)

If an on-chip debugger is used, there is no need to use the Target Download option. If it is used, this may yield downloading the code twice (depending on settings).






More:

Processes

Download Files

Options

Target Download

Endian

VLE