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/MSP-FET: Unknown device on Linux, works on Windows

Part Number: MSP-FET
Other Parts Discussed in Thread: RF430FRL152HEVM, , UNIFLASH, RF430FRL152H

Tool/software: Code Composer Studio

I am encountering the "Unknown device" error trying to flash/debug an RF430FRL152HEVM board using an MSP-FET when running CCS on Linux, but the exact same hardware setup works on Windows.

My Linux machine is running Ubuntu 20.10, CCS v10.1.1. I have also tried using MSPFlasher (result below) and UniFlash with no success.

jason@galvani:~/ti/MSPFlasher_1.3.19$ MSP430Flasher -s /home/jason/Work/s3-firmware/Debug/s3-firmware.txt -v -g
* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.19                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers: 
* Found USB FET @ ttyACM0 <- Selected
* Initializing interface @ ttyACM0...done
* Checking firmware compatibility: 
* FET firmware is up to date.
* Reading FW version...done
* Setting VCC to 3000 mV...done
* Accessing device...
# Exit: 16
# ERROR: Unknown device

I have checked that the `70-mm-no-ti-emulators.rules` file appears in `/etc/udev/rules.d` after running the post-installation script, and have tried reboots & not using a USB hub.

My Windows machine is running Win10 and CCS 9.3.0.

  • Since the debugger at ttyACM0 is being found there is no problem with your udev rules. This would appear to be a problem with the debug stack. Check to see what version of libmsp430 is being used and that it supports the device you are trying to program.

    It is possible, even likely that you have several versions of libmsp430 installed. I just checked and I have several. Including versions in the gcc and Flasher directories. The Flasher documentation has some details on how to get it to use a particular copy.

  • Hi David,

    Thanks for the fast response. As it turns out I was able to get MSP430Flasher to work. I needed to use the `-o L` option described in the help since I am using a RF430FRL152H device. The successful flash is below. I used the version of libmsp430 that was packaged with MSPFlasher v1.3.19 by setting my LD_LIBRARY_PATH environment variable.

    However, I still can't get it working in CCS and need to use the debugging environment. How can I check the location of the libmsp430.so that is being used by CCS?

    jason@galvani:~/Work$ MSP430Flasher -w "/home/jason/Work/s3-firmware/Debug/s3-firmware.txt" -v -g -o L
    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP Flasher v1.3.19 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Checking for available FET debuggers: 
    * Found USB FET @ ttyACM2 <- Selected
    * Initializing interface @ ttyACM2...done
    * Checking firmware compatibility: 
    * FET firmware is up to date.
    * Reading FW version...done
    * Setting VCC to 3000 mV...done
    * Accessing device...done
    * Reading device information...done
    * Loading file into device...done
    * Verifying memory (/home/jason/Work/s3-firmware/Debug/s3-firmware.txt)...done
    
    * Writing to external memory...done
    * 
    * ----------------------------------------------------------------------------
    * Arguments : -w /home/jason/Work/s3-firmware/Debug/s3-firmware.txt -v -g -o L 
    * ----------------------------------------------------------------------------
    * Driver : loaded
    * Dll Version : 31400000
    * FwVersion : 31200000
    * Interface : TIUSB
    * HwVersion : U 3.0
    * JTAG Mode : AUTO
    * Device : RF430FRL152H
    * EEM : Level 4, ClockCntrl 2
    * Erase Mode : ERASE_ALL
    * Prog.File : /home/jason/Work/s3-firmware/Debug/s3-firmware.txt
    * Verified : TRUE
    * BSL Unlock : FALSE
    * InfoA Access: FALSE
    * VCC OFF
    * ----------------------------------------------------------------------------
    * Powering down...done
    * Disconnecting from device...done
    * 
    * ----------------------------------------------------------------------------
    * Driver : closed (No error)
    * ----------------------------------------------------------------------------
    */

**Attention** This is a public forum