CCSV6 on 64bit Linux host, problem while debugging with target = CC3200 Launchpad board Cortex_M4_0: Error connecting to the target

user1818910

Other Parts Discussed in Thread: CC3200MOD, CC3200

I have installed CCS V6.1.3.00033 on 64bit Linux host, Ubuntu 16.04LTS.

My target is TI's CC3200 Launchpad board (CC3200MOD LAUNCH XL Rev1.0)

I see from http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv6#Ubuntu_16.04_64bit CC3200 is supported but "(requires updating to latest TI emulation update)". Is there something I should do to get the latest TI emulation update, does it not happen automagically when I install CCS for my platform and chosen target ?

I have managed to build a project (wlan_station). I have tried CC3200 and CC3200-SWD targets in the target configuration (copied from CC3200.ccxml) but neither of these work. The console says:

Cortex_M4_0: GEL Output: 
Memory Map Initialization Complete
Cortex_M4_0: Error connecting to the target

On the host, udev rules were installed (by running install_drivers.sh), the rules are present under /etc/udev/rules.d

The USB device comes onto the device tree, I can see it with 'lsusb' alright:

Bus 005 Device 004: ID 0451:c32a Texas Instruments, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0451 Texas Instruments, Inc.
  idProduct          0xc32a 
  bcdDevice            5.00
  iManufacturer           1 FTDI
  iProduct                2 USB <-> JTAG/SWD
  iSerial                 3 cc3101
  bNumConfigurations      1
  Configuration Descriptor:
...


I have tried installing libftdi1 32 bit version ( using sudo apt-get install libftdi1:i386) although I see CCS has its own, but it made no difference.

Any pointers will be much appreciated. Thanks for reading.

over 9 years ago

0 user1818910 over 9 years ago

Intellectual 270 points

Exploring the GCC toolchain option now. I'm reporting my further findings.

There wasn't any udev rule to write VID,PID to /sys/bus/usb-serial/drivers/ftdi_sio/new_id and that was why /dev/ttyUSB{0,1} were not getting created. After adding a suitable rule to /etc/udev/rules.d, these two character devices came alive after plugging in the Launchpad board. So far so good.

Now tried openocd:

cd  /proj/TI/CC3200SDK_1.2.0/cc3200-sdk/tools/gcc_scripts
openocd -f cc3200.cfg

Openocd spat out:

Open On-Chip Debugger 0.9.0 (2015-09-02-10:42)
Licensed under GNU GPL v2
For bug reports, read
	openocd.org/.../bugs.html
adapter speed: 1000 kHz
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
cc3200_dbginit
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: cc3200.jrc: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors

and stayed there until killed with a Ctr-C.

Now if I look, the /dev/ttyUSB0 is gone but the /dev/ttyUSB1 is present.

Any helpful clues? I see the green light on the Launchpad board, so it can't be a power issue.

0 user1818910 over 9 years ago in reply to user1818910

Intellectual 270 points

I suspect that my current stumbling block i.e. the error message "Cortex_M4_0: Error connecting to the target" may be due to the ARM going into a low power state with JTAG shut down, or because the JTAG clock is too fast. Are there any magic spells (GEL scripts?) I can try out? I do not necessary need CCS to work right away, I could go with the GCC tool chain too if that solves my issue, but I need to understand what could be happening here.

If this query is in the wrong forum, I request the moderator to move it to a more relevant place (e.g debug hardware support / JTAG / power management as appropriate). Thanks

0 Mark Garrett over 9 years ago in reply to user1818910

TI__Intellectual 2010 points

Hi,

The "Error connecting to the target" message can be very vague for ICDI devices. Can you confirm that the SOP jumpers are set up for JTAG mode? (See section 2.4.5 in http://www.ti.com.cn/cn/lit/ug/swru372b/swru372b.pdf).

Thanks,

Mark

0 user1818910 over 9 years ago in reply to Mark Garrett

Intellectual 270 points

Thanks, Mark, for attending to my query. It was not the SOP jumpers (all were off, ie JTAG) but a missing jumper on J13. With J13 off, the FTDI chip has power and is responsive, but reads out all zeros while the processor and peripherals are functioning normally. Particularly hard to spot.

Code Composer Studio™︎

Code Composer Studio forum

CCSV6 on 64bit Linux host, problem while debugging with target = CC3200 Launchpad board Cortex_M4_0: Error connecting to the target