• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 696 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.

66AK2L06: Trouble Halting CPU error -1321

pch
Prodigy 180 points
Part Number: 66AK2L06


I have a custom board designed around the 66AK2L06.

I'm using CCS v7 with an XDS100v3.

Power-up/Clocking/Reset sequence appears to be OK since I have RESET STATUS going high and a 16.666mHz clock on the SYSCLKOUT pin.

CVDD is controlling around 0.94v

Running the JTAG 'Test Connnection' has no errors.

Bootmode pins set to Sleep Mode with ARM boot and PLL/System clock set to 1Ghz (100mHz input clock).

The problem is when I try to run a short test program in debug. The GEL loads and executes but I get the following error:

ARM_A15_0: Trouble Halting CPU (Error -1321). Device failed to enter debug/halt mode because security settings prevent debug.

I'm not sure what security settings they are talking about. Any ides on what I can try to debug/fix this?

Thanks!

  • 0
    TI__Guru 65405 points
    I've forwarded this to the experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 180 points
    Any idea when I'm going to hear back.... I'm pretty much stuck until I get this resolved.
    Thanks!
    Peter
  • 0 in reply to pch
    Prodigy 180 points
    I have done some more testing.

    Bootmode pins set for Sleep Mode, DSP boot (0x08B0).

    I then created a custom configuration ccmxl and ran 'Launch Selected Configuration'.

    Then, right-click on the C66xx_0 core and tried 'Connect Target'.

    I get the following error:
    Error Connecting to Target (-1143). Device core was hung. The debugger has forced the device to a ready state and recovered debug control... etc.

    I can then 'Load' my test program to the core and the debug code displays... I can single-step for a while and even look at some registers, but within a few seconds, I get the "Device Core is Hung" message again.

    Any ideas/suggestions on how I can get this to work?

    Thanks
    Peter
  • 0 in reply to pch
    Prodigy 180 points
    I was able to determine 'NO DSP boot mode' and configured the bootmode pins accordingly.

    I just want to be able to 'Connect Target' with ARM 0.

    However, no matter what I try, I always get the -1321 error: Device failed to enter debug/halt mode because SECURITY SETTINGS prevent debug.

    So.. as I have asked.. does anyone know what SECURITY SETTINGS this error is talking about?

    I've been stuck on NOT being able to connect to any target for over 4 weeks.

    Any help/suggestions are greatly appreciated.

    Thanks...
    Peter