• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 646 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.

CCS 5.1.1 with Blackhawk LAN560 Emulator (maybe trying to unwind stack trace too far)

Jonathan White
Intellectual 830 points

I am using CCS 5.1.1 on Windows-7

I can connect to my target (a C6678 R2.0 silicon DSP with 8 cores) using a Blackhawk emulator.

But when I load symbols, I suddenly get the error below (and it just comes back again and again when I hit Cancel or hit OK):

Blackhawk LAN560 Emulator, 20-pin JTAG Cable_0,C66xx_0:

Trouble reading memory block at 0xffffff94 on Page 0 of Length 0x6c. Error - 1202). Device core is hung. The debugger will attempt to force the device to a ready state to recover debug control. Your application's state will be corrupt. You should have limited access to memory and registers, but you may need to reset the device to debug further.
(Emulation package 5.0.569.0)

It looks as if (although this is just my best guess), that when I load the symbols, the debugger tries to unwind the stack (to get stack trace), but instead of stopping at the topmost function call, it tries to dereference a null pointer.

Is this a known problem, and/or is there a workaround?

I have recently moved from CCS 5.0.3 on Windows-XP to CCS 5.1.1 on Windows-7. I did not have this problem previously in exactly the same scenario.

  • 0
    TI__Guru**** 486181 points

    Hi Jonathan,

    Sorry for the delayed response. Are you using a GEL file that properly sets up the debugger memory map? This should help prevent invalid memory access. The symbols for your application - where they generated by TI compiler?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 830 points

    Hi Ki, thanks for your reply.

    The symbols were generated by the CCS 5.1.1 tool chain.

    I load the code over PCIe (using a .hex file generated from the .out by the hex6x utility).

    Actually, I'm not using a GEL file. My thinking was that I did not want to do anything intrusive, just observe the system, and that a GEL file would not be needed.

    Are you saying that the GEL file is needed? If so, I wonder which one to use, and it would be useful to know why it's needed [I never seemed to need one with CCS 5.0.3]

    Regards, Jon