• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1056 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error is CCS4 when attempting to use all of L2 as SRAM

Sean Bedford
Expert 1560 points


Hello,

I am trying to use the whole of the 256k of L2 as SRAM in my C6713B.  The problem comes when I go over the 192k mark into the memory that is configurable between SRAM and cache.   When i try to load a program that uses this portion the program starts to run on its own (not doing what it's meant to) and crashed the emulator when you try to halt it.  These are the messages in the console from the crash.

TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution, An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.

TMS320C671X: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

The cache is turned of in the bios, any suggestions as to what I can do to be able to make use of the extra memory would be great.

Thank you

Sean

 

  • 0
    TI__Guru**** 171309 points

    Sean,

    Contrary to common belief, the JTAG emulation requires the CPU to acknowledge its requests - in other words, if the processor completely loses its execution status the emulator rarely manages to take back control.

    From an emulation/IDE standpoint there is no limitation in accessing any valid memory region of your target - provided it is properly configured by either your application or a GEL file.

    In your case it seems to me there is some leftover configuration that is causing this failure, but to confirm this could to manually connect to the target without any code? From your workspace you can right-click on the .ccxml file and select Debug As --> Debug Session. Once the debugger shows up, right-click on the core and select Connect. This way you can open a memory view and see if you can view and edit the memory region you are trying to access.

    If you still can't access it through the memory view, check if a GEL file is also performing this configuration for you.

    If you can access it, I suggest re-checking your application configurations. Maybe BIOS or a CSL call is trying to use a cache API that may be disrupting the execution.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 1560 points

    Yes thank you Rafael, it was the gel file only specifiying the length of the RAM as 0x30000.

     

    Sean