• Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 1789 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 6.2 and 6.1.3 crash when connect to BeagleBoneBlack am335x PRU using XDS100v2 or XDS200 debugger

Adam Duncan68
Prodigy 180 points
Other Parts Discussed in Thread: AM3358, CCSTUDIO

Hi,


I am trying to connect either a XDS100v2 or XDS200 debugger to PRU0 on the AM3358 sitara chip on the beaglebone black. CCS is crashing every time I select the PRU and click "connect". I can connect to the A8 core in the AM3358 and step through running code just fine and this just appears to be related to connecting to the PRU. I have tried fresh installs of the CCS 6.2 050 and 6.1.3 034 each with two different debuggers and get the same result. Can you please give me suggestions for ways to connect to the PRU without crashing?

Specific HW and SW:

host: Ubuntu 16.04 with 16G RAM and 6th gen Intel processor

target: Beaglebone black with AM3358

debuggers used: XDS100v2 and XDS200

steps to reproduce issue: I followed this wiki about blinking an LED on the beaglebone black step by step.

processors.wiki.ti.com/.../PRU_Training:_Hands-on_Labs

Everything works as in the wiki including being able to connect to the cortex A8 with the debugger and running the PRU gel scripts. As soon as I try to connect to PRU0 though, CCS crashes.

Here is the output I see from the terminal window after the crash:

"user@cpu:~/ti/ccsv6/eclipse$ ./ccstudio
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "unity-gtk-module"
flxInitLoad: client has not been protected.

log4j:WARN No appenders could be found for logger (org.eclipse.jetty.util.log).
log4j:WARN Please initialize the log4j system properly.
dvtLogOptions.xml DOES NOT exists
*** Error in `/home/user/ti/ccsv6/eclipse/ccstudio': free(): invalid pointer: 0xa53f2e80 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x67257)[0xf763f257]
/lib/i386-linux-gnu/libc.so.6(+0x6d577)[0xf7645577]
/lib/i386-linux-gnu/libc.so.6(+0x6dd31)[0xf7645d31]
...

"

  • Prodigy 180 points

    Checking in again to see if anyone has any suggestions or help for this.

    Thanks!

  • TI__Guru**** 171074 points
    Hi,

    I couldn't hit this issue with CCSv6.2.0 - connecting with both Ubuntu 14.04/64 and 16.04/64 did not show any problems.

    However, I noticed the errors are coming from 32-bit libraries - are you testing this with CCSv6.1.3 (32-bit) or CCSv6.2.0 (64-bit)?

    Also, when you installed each version did you completely remove the previous files from the directory (assuming you used the same directory /home/user/ti/ccsv6)? If not, I strongly recommend you doing so to prevent any conflicts between the 32-bit components of 6.1.3 and the 64-bit components of 6.2.0. Check section 2.4 of the linked page at the end of this post.

    If you have done the above, then I try to start as fresh as possible to eliminate any possible conflicts between the versions. Close CCS, empty the cached information (by running fsclean) and restart using a new workspace. Check sections 4 and 6 of the page below.

    The details are shown at the CCSv6 Troubleshooting page at:
    processors.wiki.ti.com/.../Troubleshooting_CCSv6

    Hope this helps,
    Rafael
  • in reply to desouza
    Prodigy 180 points

    Hi Rafael,


    I initially started with CCS 6.2.0 64 bit and experienced the issue. I then ran the uninstall script, then removed the ti directory for the install  and installed 6.1.3 since it seemed like the most stable fo the 6.1 versions. the only version I saw available was the 32 bit version so I went installed some 32 bit libraries on my system and then installed the 32 bit CCS 6.1.3. I currently still have the 6.1.3 32 bit on my system. But I saw the same exact crashing behavior with the 64 bit CCS 6.2.


    I ran the fsclean script and the script executed with a successful message. However, I still get a crash when I try to connect to the PRU in CCS.

    Thanks for your help on this!

    Adam

  • in reply to Adam Duncan68
    TI__Guru**** 171074 points
    Adam,

    Well, it seems you had uninstalled it properly and therefore there shouldn't have any problems.

    In this case, can you zip and send the log files shown in the section below? This may help shed some light to the issue.
    processors.wiki.ti.com/.../Troubleshooting_CCSv6

    Just FYI, I searched around and there is only one report where a customer mentions a very similar scenario as yours
    e2e.ti.com/.../519579

    Regards,
    Rafael
  • in reply to desouza
    Guru 92251 points

    desouza said:
    Just FYI, I searched around and there is only one report where a customer mentions a very similar scenario as yours
    e2e.ti.com/.../519579

    There is also a recent report in the Sitara forrum on CCS 6.2 crashing when attempt to connect to a PRU - see CCS v6.2.0 JTAG debug fails

    Edit: in the referenced thread the backtrace appears to show the crash occurring when a function in ccsv6/ccs_base/DebugServer/bin/../../emulation/tpi/libdisassemble_pru.so calls free with an invalid pointer.

  • in reply to Chester Gillon
    Prodigy 180 points
    The thread mentioned by desouza sounds exactly like my issue.

    I uninstalled 6.1.3 a few days ago (and deleted every TI directory as described) then reinstalled 6.2 050 64 bit and am having intermittent problems now. I tried the default workspace and still experienced a crash. However, I then made a new workspace and did not experience a crash.

    I haven't been able to spend much time on this lately but will be able to try again tomorrow and will post my results.

    Thanks for your help.