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.

TMP1827EVM: Troubles with Linux GUI startup - unable to open serial device

Part Number: TMP1827EVM
Other Parts Discussed in Thread: TMP1827, USB2ANY

Tool/software:

Hey folks! Our customer is seeing some errors when trying to use the Linux GUI with the TMP1827. Any ideas? 

pasted info below:

“It is still failing to see the device. DMESG is returning the following once I connect the Device:

[937825.695489] usb 1-1: USB disconnect, device number 47
[937842.356274] usb 1-1: new full-speed USB device number 48 using xhci_hcd
[937842.506929] usb 1-1: New USB device found, idVendor=2047, idProduct=0301, bcdDevice= 2.00
[937842.506933] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[937842.506934] usb 1-1: Product: USB2ANY/OneDemo device
[937842.506935] usb 1-1: Manufacturer: Texas Instruments
[937842.506936] usb 1-1: SerialNumber: 85F2A26E12000100
[937842.510801] hid-generic 0003:2047:0301.001E: hiddev2,hidraw6: USB HID v1.01 Device [Texas Instruments USB2ANY/OneDemo device] on usb-0000:00:14.0-1/input0

So I suspect I have a bad UDEV rule. The following are the rules that were installed by the installer:
root@OLA-FTJ9724:/etc/udev/rules.d# cat 61-msp430uif.rules 70-mm-no-ti-emulators.rules 71-ti-permissions.rules  
#TI MSP430UIF
ATTRS{idVendor}=="2047",ATTRS{idProduct}=="0010",MODE="0666"
ATTRS{idVendor}=="2047",ATTRS{idProduct}=="0013",MODE="0666"
ATTRS{idVendor}=="2047",ATTRS{idProduct}=="0014",MODE="0666"
ATTRS{idVendor}=="2047",ATTRS{idProduct}=="0203",MODE="0666"
ATTRS{idVendor}=="2047",ATTRS{idProduct}=="0204",MODE="0666"
ATTRS{idVendor}=="0451",ATTRS{idProduct}=="f432",MODE="0666"

ACTION!="add|change", GOTO="mm_usb_device_blacklist_end"
SUBSYSTEM!="usb", GOTO="mm_usb_device_blacklist_end"
ENV{DEVTYPE}!="usb_device",  GOTO="mm_usb_device_blacklist_end"

# TI USB Emulators
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0010", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0013", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0014", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0203", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="2047", ATTRS{idProduct}=="0204", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="0451", ATTRS{idProduct}=="F432", ENV{ID_MM_DEVICE_IGNORE}="1"

LABEL="mm_usb_device_blacklist_end"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0403",ATTRS{idProduct}=="a6d0",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0403",ATTRS{idProduct}=="a6d1",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0403",ATTRS{idProduct}=="6010",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0403",ATTRS{idProduct}=="bcd9",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0403",ATTRS{idProduct}=="bcda",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1cbe",ATTRS{idProduct}=="00fd",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="1cbe",ATTRS{idProduct}=="00ff",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef1",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef2",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef3",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef4",MODE:="0666"
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0451",ATTRS{idProduct}=="c32a",MODE:="0666"
ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef0",ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="0c55",ATTRS{idProduct}=="0220",ENV{ID_MM_DEVICE_IGNORE}="1"
KERNEL=="ttyACM[0-9]*",MODE:="0666"


I did retrigger udev to make sure, but I am not sure why the GUI is failing to connect since it is not explicit about what it is trying to connect to (it seems to be referencing a ti_transport_usb and cannot open a serial device, but I am not sure which one).
  • Hello,

    This thread has been brought to the attention of the GUI Composer experts. They should be able to assist further.

    Thanks

    ki

  • Hi Cameron, 

    I think we may be missing an additional rule in our installer. I'll file a ticket for this issue. However, would you be able to modify one of rules files to add the line highglighted in white in picture below? I used 71-ti-permissions.rules and added this line:

    ATTRS{idVendor}=="2047",MODE:="0666"

    I then restarted my system or you could restart udev. 

    Martin