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/PROCESSOR-SDK-AM335X: JTAG XDS100v2 Unable to Access DAP CSSv7

Part Number: PROCESSOR-SDK-AM335X

Tool/software: Code Composer Studio

I'm running CCSv7 on my ubuntu 16.04 host. I am using a BlackHawk USB100v2 JTAG Emulator to try to program the PRU on the AM335x of the BeagleBoneBlack. I followed all steps on the wiki for installation, and that all goes fine. I can create projects and compile them just fine. When I start to follow Lab 1 of the "Hands-on-labs" I can't get the debugger to connect. 

When I go to run the debugger I get error dialog:

Error connecting to the target:
(Error -1170 @ 0x4A322000)
Unable to access the DAP. 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 6.0.576.0)

If I just run the debugger for the Target Configuration, without a project selected, I get the same error when I try to connect to the PRU core. If I try to connect to the CortexA8 core it gives me another error "No source available for 0x233ac. I have to assume they're related, but no clue how I can go about fixing them.

I had tried running all this on CCSv6 first, then thinking maybe some updates have been done, I just installed CCSv7 and same problem. Any assistance would be amazing a this point.

  • Hi,

    This is due to the fact you are trying to access the PRU core without releasing it from reset.

    This can be done from the master Cortex A8 core.

    On the Debug view, simply highlight the line "Texas Instruments XDS100v2 USB Debug Probe_0/CortxA8", right click on it and select "Connect Target".

    After it finishes performing the initialization, go to menu Scripts --> PRU_ICSS --> PRU_ICSS_Init. This should release the PRU cores from reset.

    After that, highlight the line "Texas Instruments XDS100v2 USB Debug Probe_0/PRU_0" (or PRU_1), right click and connect.

    The reason for all this is due to the fact the master core of the device keeps these cores in reset until they are explicitly started.

    Hope this helps,
    Rafael