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.

AM3352 unable to connect over JTAG - "security violation"

Other Parts Discussed in Thread: TPS650250, AM3352, AM3359

Hi All,

I'm bringing up a custom design based on the AM3352 and the TPS650250 PMIC chip. I've checked a number of things out, including power sequencing and incoming reset signal (PORZ), and I persistently get the following error from CCS 5.3.0.00090 when I try to connect a debug session:

Error connecting to the target:
(Error -1260 @ 0x0)
Requested operation failed for security violation. Check security/priviledge settings, and retry the operation.
(Emulation package 5.0.872.0)

I've verified my setup using a beaglebone - ie, populated the JTAG header, etc, and the exact same XDS100v2 and cable connect fine to the beaglebone.

Interestingly, the low level JTAG "test connection" passes. Any thoughts on what could cause such an odd error?

Thanks,

Morgan

morgan@mojolabs.net

  • Hello Morgan,

    Sorry for the delayed response.

    Morgan Jones said:
    Requested operation failed for security violation. Check security/priviledge settings, and retry the operation.

    From what I have read in the past, that error indicates that the device has a security module of some sort which is enabled that is preventing the debugger from accessing the device. Perhaps this module got enabled on your device or there is some issue with the PMIC chip

    i am not too familiar with the specifics of the device myself. It may help to ask around in the AM335x device forum. The experts there can confirm my suspicions.

    Thanks

    ki

  • Hi Morgan,

    Did you ever fix your issue? If so, how?

    I am getting the same error message for a custom designed board with the AM3359.

    As far as I know, there is no security module in the AM3359.

    Regards,

    Jon

  • Hi Jon,

    We did resolve it - it was very perplexing. It turned out to be a mis-connected power rail to the processor. Exactly how this turns into a security error message on a part without a security module, I have no idea. But, connecting the missing rail did the trick.

    Good luck,

    Morgan