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.

AM335x JTAG connection to PRU

Hello to all,

I'm trying to follow the "PRU training: Hands on Lab" and I'm not able to go over the point  2.9 (JTAG connection). I'm using a BeagleBone black, the Jtag is the XDS100V2. I'm using a CCS6.2 on UBUNTU 16.04.

When I try to run the script "PRU cape init" I obtain this message:

ortxA8: Output: ****** PRU Cape PINMUX is being configured  *****
CortxA8: Trouble Writing Memory Block at 0x44e10990 on Page 0 of Length 0x4: (Error -1065 @ 0x3D5A) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.407.3)
PRU_Cape_Init() cannot be evaluated.
Target failed to write 0x44E10990
    at *((unsigned int *) 0x44e10990)=(0|5) [PRU_CAPE.gel:40]
    at PRU_PINMUX_Config() [PRU_CAPE.gel:25]
    at PRU_Cape_Init()

If I try to connect the PRU core I obtain this message:

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.407.3)

If I make a connection by the CD_DAP_DebugSS I'm able to read the address 0x4A322000 e 0x44e10990.

Running the test connection I don't have failoure.

What can I do in order to make this connection?

Thanks

Matteo

  • Hi,

    The PRU experts have been notified. They will respond here.
  • Hi Matteo,

    A common scenario that could be causing this error message is:

    There is code already running on the target (Linux or any other flashed code), which may prevent access to some memory protected areas.

    Usually removing a SD/µSD card solves this problem.

    Alternatively, the board could be auto-running code that's been flashed to the NAND. To prevent the BBB from booting this code, press the "boot button" (S2 on the BBB) before switching-on the board and kept the button pressed for 2 or more seconds after the board is powered.  Now try connecting to CCS and running the GEL.

    Do either of these steps resolve your error message?

    Regards,
    Melissa

  • I created a wiki page to help with this sort of issue:

    processors.wiki.ti.com/.../PRU-ICSS_Debug_on_AM335x

    There's a video and everything. Please have a look. The method that I use there avoids the MMU issue you're encountering because I leverage something called the Debug Access Port.
  • Thanks for your help.

    The first solution suggested doesn't work.

    Applying the second solution I'm able to run the CAPE_Init script

    CortxA8: Output: ****** PRU Cape PINMUX is being configured  *****
    CortxA8: Output:     ****** Enabling PRU-ICSS clock ******
    CortxA8: Output: *    ***** Reseting the PRU-ICSS   ******

    but, when I try to connect the PRU0/1 core, the CCS 6.2.0.00050 crashes (it stops to work and restarts automatically).


    What I can do now? do you suggest to do a downgrade to some older CCS?


    thanks in advance

  • Matteo Giusti86 said:

    Applying the second solution I'm able to run the CAPE_Init script

    CortxA8: Output: ****** PRU Cape PINMUX is being configured  *****
    CortxA8: Output:     ****** Enabling PRU-ICSS clock ******
    CortxA8: Output: *    ***** Reseting the PRU-ICSS   ******

    Why aren't you following the directions from the wiki page?  I even have a start to finish video of the whole thing to make it really easy.

  • Hi Brad,
    I tried to apply also your solution but the result is the same: when I press the debug button the CCS6 crashes after few seconds.
  • Something is not right with your CCS installation... Even in the scenario where you don't have things setup properly, you normally would see some kind of warning or error message from CCS. I think something is wrong with your installation. You might try reinstalling CCS, or alternatively you may need to start a separate thread in the CCS forum to debug the issue of CCS crashing. Before you do anything of these things, I recommend doing a reboot of your computer and trying once more. Sometimes that is enough to get things working!
  • thanks to everybody for the help!

    I fixed the issue redoing everything in a new workspace. Now it runs.

    Matteo