Part Number:MSP432E401Y
Tool/software: Code Composer Studio
I'm trying to do some development work on an MSP in a Linux environment, using 64-bit Fedora 25 build. I've tested the board on windows development system and it works just fine there, it only on Linux I'm having a problem. I know this may end up being more of a Linux type issue, but I'm hopefully someone out there has some experience and can see what my problem is.
I got Code Composer installed, bno problem (v8.2). I am using the tcpecho example from sdk 2.30, unmodified (CCS/tirtos version). It builds fine.
My problem lies in trying to load the software to the MSP, the system won't recognize the board despite everything seeming to indicate it should.
Here is the error message from Code Composer during the load op:
[Start] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ /home/pbyers/.ti/ti/0/0/BrdDat/testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100- or 510-class product. This utility will load the adapter 'libjioxds110.so'. The library build date was 'Sep 28 2018'. The library build time was '17:16:01'. The library package version is '8.0.803.0'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. An error occurred while hard opening the controller. -----[An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. The value is '-260' (0xfffffefc). The title is 'SC_ERR_XDS110_OPEN'. The explanation is: An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. 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. [End]
What I've tried so far:
Well, not much, I just looked at a lot of syslog outputs to confirm the board was being recognized and it seemed it was. Here's what I see:
[pbyers@localhost ~]$ dmesg | grep tty [ 0.000000] console [tty0] enabled [ 3.253236] dw-apb-uart.0: ttyS4 at MMIO 0xdf14c000 (irq = 20, base_baud = 115200) is a 16550A [pbyers@localhost ~]$ dmesg | grep tty [ 0.000000] console [tty0] enabled [ 3.253236] dw-apb-uart.0: ttyS4 at MMIO 0xdf14c000 (irq = 20, base_baud = 115200) is a 16550A [ 308.024095] cdc_acm 1-1:1.0: ttyACM0: USB ACM device [ 308.024521] cdc_acm 1-1:1.3: ttyACM1: USB ACM device [pbyers@localhost ~]$ dmesg [ 307.831170] usb 1-1: new full-speed USB device number 5 using xhci_hcd [ 308.000800] usb 1-1: New USB device found, idVendor=0451, idProduct=bef3 [ 308.000808] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 308.000813] usb 1-1: Product: XDS110 (02.03.00.15) Embed with CMSIS-DAP [ 308.000817] usb 1-1: Manufacturer: Texas Instruments [ 308.000821] usb 1-1: SerialNumber: ME401023 [ 308.006567] hid-generic 0003:0451:BEF3.0003: hiddev96,hidraw2: USB HID v1.11 Device [Texas Instruments XDS110 (02.03.00.15) Embed with CMSIS-DAP] on usb-0000:00:14.0-1/input5 [ 308.024095] cdc_acm 1-1:1.0: ttyACM0: USB ACM device [ 308.024521] cdc_acm 1-1:1.3: ttyACM1: USB ACM device [ 308.024843] usbcore: registered new interface driver cdc_acm [ 308.024844] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [pbyers@localhost ~]$
So it seems like the board is recognized on ttyACM0 and ttyACM1
I tried using Putty to connect serially to those ports. No connection could be established.
I followed the instructions to attempt a reset of the xds probe, the system says it can't find it on the bus
[pbyers@localhost xds110]$ ./xds110reset
ERROR: Failed to connect to XDS110 (-260).
Check USB connection to the XDS110.
[pbyers@localhost xds110]$ ./xdsdfu -f firmware.bin -r
USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved.
Scanning USB buses for supported XDS110 devices...
The requested device was not found on the bus.
[pbyers@localhost xds110]$
I'm sort of at the end of what I can think to do right now. Any help or possible suggestions would be a help. I can still use a JTAG to program the MCU directly, so I'm fine there, but it would be really keen to be able to use the XDS for ease of dev and debug.
Thanks
