Download from the primary winIDEA instance (core PE0 or CPU0) to the secondary winIDEA instance (core PE1 or CPU1) RAM fails.
The reason for this is that winIDEA does not initialize the Local RAM of secondary cores. For the primary core, it is done partially by winIDEA to be able to perform flash programming, which means that only a part of the RAM is initialized that is used for the flash programming UMI monitor. For other cores, you have to perform the initialization.
That will make it 32-bit aligned and the file content will be correctly loaded. Note that other locations will be left uninitialized and, thus byte, word, and non-aligned writes will not work.
This can be done manually:
The RAM initialization survives CPU Reset until power-off.
Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.