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.

RM57Lx Launchpad debug thow error

I just bought  RMS57Lx LaunchPad

When I try Project 0 . I get below error when  I run debug.

Error connecting to the target:
(Error -260 @ 0x0)
An attempt to connect to the XDS110 failed.
The cause may be one or more of: invalid firmware update, invalid
XDS110 serial number, or faulty USB connection. The firmware and
serial number may be updated using the xdsdfu utility found in
the .../ccs_base/common/uscif/xds110 directory of your
installation. View the ReadMe.txt file there for instructions.
(Emulation package 6.0.14.0)

I am using CCS 6.1 . It updated.

Project build configuration:

Varient : RM57L8xx

connection : TI XDS110 USB Probe

Compiler version : TI v5.2.4

OS:

I am using Ubunut 14.

There are two device shown in /dev/ when I connect board

ttyACM0 

ttyACM1

Board Led Status

LED 7  , LED6 : on 

LED 3 :  blinking

I have used Project0 holacogen files.

I appreciate you time and efforts 

  • I had a similar problem but in Windows, not conosco While Linux platform, but maybe you need to update the drivers XDS110, that was the solution in window.

    However, if you still have trouble after you update to Hercules Emulation 6.0.7 – to debug flash programming problems it can be helpful to check the box
     
    “Enable Verbose Output”
  • Thanks Martin,

    I had trouble on Linux once and it turned out to be a problem with a system called 'udev'.

    'udev' controls rules for user applications accessing hardware like USB ports: manpages.ubuntu.com/.../udev.7.html

    I believe the scripts and udev rules file is in '<ccsv6>/install_scripts' ... look for a file like '71-ti-permissions.rules'.

    I think the ti_xds100_linux_install.sh script is supposed to copy this over but it needs to be run as root. And when it happened to me if I remember the installer really didn't fail because of not being run as root - rather I think it completed but this particular script didn't complete correctly. Anyway it wasn't 'obvious' that there was an installation problem.

    So check that udev rules file and then if it's not there try installing it (and I think you need to unplug your board and reboot to try again..)