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/AM3358: PRU debug

Part Number: AM3358

Tool/software: Code Composer Studio

Hi

I have BBB and I want to program and debug PRU using CCS. I checked "processors.wiki.ti.com/.../PRU_Training:_Hands-on_Labs" and now I have some question:

question 1: in  Hardware section has been said FTDI cable and jtag emulator is necessary. my question is that as regards program and debug can be done by jtag emulator(XDS100), what should we have FTDI cable?

question 2: please guide me about  "Use a minicom console to stop U-Boot to prevent the kernel from booting": how should to do this?please guide me or refer me to a document to do this.

question 3: is it possible to program and debug PRU using CCS without using jtag emulator?

question 4: after I program PRU and then I be use PRU and OS together, if OS hangs,then PRU can go on it's work?(do PRU works completely stand-a lone from OS ? or it's depended on to OS for work?)

Thanks a lot for your support.

  • Hi,

    These labs were written by the Sitara team, therefore the best answers would be provided by someone on their forum. I can, however, provide some clarifications:

    1) The FTDI cable (a USB-to-RS232 converter cable) is necessary in case the PRU sends text messages via UART. Also, it can be useful for your question 2 below.

    2) The note in blue of Lab 1 has a procedure to prevent u-boot from taking control over the device either by using a FTDI cable and a terminal program (minicom, teraterm, putty) or by disabling the stored code from running. Carefully read its contents and you may not need to use a FTDI cable. Otherwise, several guides to connect BeagleBone Black using a FTDI cable are available on the internet - one that I find particularly clear is below:
    www.dummies.com/.../

    If helps, the entire boot process for BeagleBone Black is described in several references on the internet. Two of them are shown below:
    dumb-looks-free.blogspot.com/.../beaglebone-black-bbb-boot-process.html
    www.linuxjournal.com/.../handy-u-boot-trick

    3) Lab 4 has a procedure to perform code loading without a JTAG debug probe, while Lab 5 contains a procedure to interact with the PRU via the target Linux OS.

    4) Unless the PRU requires a resource from the main core, it can operate as an independent processor. However, if the main core causes power issues or issues a System Reset or other device-level events, the PRU will be affected.

    As I mentioned before, the experts at the Sitara forum may provide additional references.

    Hope this helps,
    Rafael
  • Dear desouza,

    Thanks a lot for your response and support.