• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 241 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6713B: TMS320C671X: Trouble Halting Target CPU: (Error -2130 @ 0x0) Unable to access device memory.

Decheng Yan
Prodigy 20 points
Part Number: TMS320C6713B

DSP memory setup

Hi, dear technical support team, I've been having the following issue every time when I was trying to connect to TMS320C6713B-DSP:

TMS320C671X: Trouble Halting Target CPU: (Error -2130 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.10.0.00080)
TMS320C671X: Trouble Halting Target CPU: (Error -1060 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.10.0.00080)

The debugger is able to enter into debug-mode and run the code until line 874, as I marked in the blue circle. However, after that, it shows the error "Unable to access device memory" and then it shows the second error. I wonder if anything is set up incorrectly in my device memory. Above you can see my memory setup and the board configuration setup. I've also attached the target configuration setup. 

I've been having the same issue over three years on my DSP. Usually, the problem went away automatically after one or two days passive wait. I am not sure what could be going wrong here. Could you double check on my setups that I uploaded and see if there is any obvious mistake? I appreciate your help!

Best,

Decheng

  • 0
    Prodigy 20 points

    Hi all, ok. There are two things that I did and now the debugger works again.

    1. Flash the DSP with a previous back-up code and it does not show the issue.

    2. Add a breakpoint in the current code and then even the current code is working now without changing any of the actual content.

    Could you explain if this is logically? By adding a break-point in the interrupt to make it work does not seem very logical to me. But at least, it works now. I'll expect, it will face the same issue after couple weeks though.

    Thanks,

    Decheng

  • 0 in reply to Decheng Yan
    TI__Guru* 78455 points

    Hello Decheng

    Unfortunately we no longer support C6713B technical queries. 
    This is a very old device family and the support team no longer has any EVMs or software to recreate/reproduce the issues are you  sharing. 

    Regards

    Mukul 

  • 0 in reply to Mukul Bhatnagar
    TI__Mastermind 40215 points

    Hello Decheng,

    As Mukul said, we can no longer provide technical support for SW development on C67x DSP. With that said, one thing you can try is to step into the function which caused memory access failure. Then try to find out which memory can not be accessed and then check you .map file to see if that memory is valid. Then rearrange your memory sections in the linker command file to make sure you only use valid memory for both data and code.

    Regards,

    Jianzhong