Post Go back to editing

Memory areas

Category: Software
Product Number: ADSP-21593

Hello together,

I currently have a problem with executing my program in the following setting:

  • ADSP-21593 on a custom board (no ARM processor)
  • CCES 3.0.1
  • C++ as the programming language
  • usage of external SDRAM (1024MB) as L3
  • shared L2 SRAM
  • ICE1000

The problem is that when I start my DEBUG-session using the emulator I get a IllOpCodeDetected exception with a certain error program counter. At first this occurred everytime I started the program, even if I comment out all code executed in the main function. After activating the linker settings 'Eliminate unused objects' and 'Individually map functions and data items' in the project properties the error does not longer occur when commenting out all the code but reappears at some point when adding the code, previously commented out, incrementally. Therefore when wanting to execute the complete program it gives the exception again. In a previous version of my project this issue did not occur. Also using all options of the Sharc Compiler's Run-time Checks did not provide any insights. 

The error program counter is in the area of 0x00b00000. When checking the generated map-xml file from the linker, one can see that this is in the dxe_l2_sw_code output section.

Since activating the linker settings as mentioned at least allowed me to execute my program of reduced size, I think that there is maybe a problem with the size of my program? Maybe is some way there is some problem with the memory areas for code and data so that after returning from some function the processor returns to a invalid address where it wants to continue its execution. 

Did somebody maybe experience this issue already or does somebody maybe have an idea what I can check or how I can assure that my memory areas do not overlap and therefore solve this issue?

Best,

Vitus

Edit: this is the map file of the linker if it provides useful information.

MB_Core1.map.xml



Added linker map file
[edited by: vb_015 at 7:22 AM (GMT -4) on 29 Aug 2024]

Thread Notes

  • Hi Vitus,

    We request you to confirm, whether you have tried workarounds from the below Ezone link, which we already discussed with you regarding the same "IllOpCodeDetected" exception for ADSP-21593 processor.
    ez.analog.com/.../fatal-error-when-adding-code

    Also, please provide us the below details to isolate your issue. This will help us to assist you further.

    1. What are the changes have you done in the current project compare to existing project?
    2. Whether the same issue occurred in different CCES versions (i.e. 2.11.0)
    3. If possible, please share us the example project along with steps to reproduce the issue here. This would be helpful for us to assist you further.

    Regards,
    Santhakumari.K