• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 1663 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/BEAGLEBK: BeagleBone Black PRU CCSv7 C compiler, Training Lab 1

Dennis Kohlhafer
Prodigy 10 points

Part Number: BEAGLEBK

Tool/software: Code Composer Studio

I have a BeagleBone Black with the PRU cape and have been trying to run Lab 1 in the "PRU Training: Hands-on Labs"

Running Code Composer Studio Version: 7.2.0.00013 on Windows 7 SP1 and using the XDS200 USB Debug Probe.

Loaded the PRU compiler version 2.1.5 as well as the PRU software support package V5.0.1.

I have followed the LAB 1 instructions and everything works up to the point where it says "b. After it loads right click on the CortxA8 core and select Connect Target."

When I attempt to connect to the CortexA8 core I get the following message:

Error connecting to the target:
(Error -1170 @ 0x0)
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.628.3)

I tried lowering the TCLK setting from 10MHz to 1MHz and also tried resetting the BeagleBone, the debug probe and the PC in various combinations.

I tried to connect to the BeagleBone using various other connections, such as the M3_WakeupSS_0 and PRU_0 without successfully being able to load the PRU code.

I am new at this and was wondering if I could get some assistance.

  • 0
    TI__Guru**** 171034 points
    Hi,

    Usually the connection to the Cortex A8 works just fine on BeagleBone boards in general, therefore I ask: by any chance do you have Linux running on the board when you try to connect to it?

    Linux in general tends to power down the JTAG circuitry which prevents the target from being properly connected via a debug probe.

    Apart from this I can only suspect there may be other issues at play, such as improper power, continuous reset of the device, etc.

    Hope this helps,
    Rafael