Hi,
I dug this box out of the pile recently and now when I connect the serial console USB cable I see:
$ lsusb
Bus 001 Device 004: ID 04e8:6001 Samsung Electronics Co., Ltd sd-wire
It seems to have lost its programming somehow? What can I do to make the console work again?
Regards,
Simon
Could you please be more specific regarding which device you have plugged in, and to what host OS? The USB serial console is a dedicated non programmable usb to uart chip. There is a second uart closer to the QSFP+ ports that is a programmable stm32f0, that device is not flashed by default out of the factory.
Hi,
Thanks for your reply.
The device I have plugged in is a x86 Linux machine, running Ubuntu. I just tried it on a different machine, a Lenovo laptop also running Ubuntu 20.04. The ‘lsusb’ output above shows what is coming up on the machine.
For the other port, I see:
Bus 001 Device 005: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
which seems right to me.
Could there be someone wrong with the boot-mode jumpers which breaks the UART?
Regards,
Simon
Thanks for the extra info. The boot jumpers will not effect the UART in any way.
The curious part is the USB ID that is being enumerated. the device should be detected as 0403:6015
Could you please attach the dmesg snippet that includes the usb enumeration of the serial cable when it is plugged in?
Hi,
Thanks for the reply. Yes:
sglass@ELLESMERE ~> sudo dmesg
[437367.300275] usb 1-12: new full-speed USB device number 8 using xhci_hcd
[437367.649111] usb 1-12: New USB device found, idVendor=04e8, idProduct=6001, bcdDevice=10.00
[437367.649114] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[437367.649116] usb 1-12: Product: sd-wire
[437367.649117] usb 1-12: Manufacturer: SRPOL
[437367.649118] usb 1-12: SerialNumber: None
Regards,
Simon
I am still very curious why you are getting that vendor ID. What kernel version are you running on your x86 host machine? Also could you run sudo udevadm monitor -e and send me the output of that?
Thanks
Hi Jon,
Yes I wondered if there was something odd about my udev rules. I do use SDwire modules but cannot find any local changes related to that.
Oddly enough. this rule seems to hit it but I am not sure why:
ACTION==“add|bind”
, SUBSYSTEMS==“usb”
, ATTRS{idVendor}==“15a3”
, ATTRS{idProduce}==“0054”
, SYMLINK+=“mx6”
, MODE=“0666”
In any case, how come the lsusb output shows that vendor ID? Could something be messing with it?
$ sudo udevadm monitor -e >asc
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[523555.988395] add /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/013
DEVTYPE=usb_device
PRODUCT=4e8/6001/1000
TYPE=0/0/0
BUSNUM=001
DEVNUM=013
SEQNUM=145692
MAJOR=189
MINOR=12
KERNEL[523556.001072] add /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=4e8/6001/1000
TYPE=0/0/0
INTERFACE=255/255/255
MODALIAS=usb:v04E8p6001d1000dc00dsc00dp00icFFiscFFipFFin00
SEQNUM=145693
KERNEL[523556.001160] bind /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12 (usb)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/013
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4e8/6001/1000
TYPE=0/0/0
BUSNUM=001
DEVNUM=013
SEQNUM=145694
MAJOR=189
MINOR=12
UDEV [523556.114087] add /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/013
DEVTYPE=usb_device
PRODUCT=4e8/6001/1000
TYPE=0/0/0
BUSNUM=001
DEVNUM=013
SEQNUM=145692
USEC_INITIALIZED=523556096777
ID_VENDOR=SRPOL
ID_VENDOR_ENC=SRPOL
ID_VENDOR_ID=04e8
ID_MODEL=sd-wire
ID_MODEL_ENC=sd-wire
ID_MODEL_ID=6001
ID_REVISION=1000
ID_SERIAL=SRPOL_sd-wire_None
ID_SERIAL_SHORT=None
ID_BUS=usb
ID_USB_INTERFACES=:ffffff:
ID_VENDOR_FROM_DATABASE=Samsung Electronics Co., Ltd
adb_user=yes
ID_PATH=pci-0000:01:00.0-usb-0:12
ID_PATH_TAG=pci-0000_01_00_0-usb-0_12
DRIVER=usb
ID_FOR_SEAT=usb-pci-0000_01_00_0-usb-0_12
MAJOR=189
MINOR=12
DEVLINKS=/dev/mx6
TAGS=:uaccess:seat:
UDEV [523556.119422] add /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12/1-12:1.0
SUBSYSTEM=usb
DEVTYPE=usb_interface
PRODUCT=4e8/6001/1000
TYPE=0/0/0
INTERFACE=255/255/255
MODALIAS=usb:v04E8p6001d1000dc00dsc00dp00icFFiscFFipFFin00
SEQNUM=145693
USEC_INITIALIZED=523556118242
ID_VENDOR_FROM_DATABASE=Samsung Electronics Co., Ltd
ID_PATH=pci-0000:01:00.0-usb-0:12:1.0
ID_PATH_TAG=pci-0000_01_00_0-usb-0_12_1_0
UDEV [523556.171841] bind /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12 (usb)
ACTION=bind
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-12
SUBSYSTEM=usb
DEVNAME=/dev/bus/usb/001/013
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=4e8/6001/1000
TYPE=0/0/0
BUSNUM=001
DEVNUM=013
SEQNUM=145694
USEC_INITIALIZED=523556096777
ID_VENDOR=SRPOL
ID_VENDOR_ENC=SRPOL
ID_VENDOR_ID=04e8
ID_MODEL=sd-wire
ID_MODEL_ENC=sd-wire
ID_MODEL_ID=6001
ID_REVISION=1000
ID_SERIAL=SRPOL_sd-wire_None
ID_SERIAL_SHORT=None
ID_BUS=usb
ID_USB_INTERFACES=:ffffff:
ID_VENDOR_FROM_DATABASE=Samsung Electronics Co., Ltd
adb_user=yes
ID_PATH=pci-0000:01:00.0-usb-0:12
ID_PATH_TAG=pci-0000_01_00_0-usb-0_12
ID_FOR_SEAT=usb-pci-0000_01_00_0-usb-0_12
MAJOR=189
MINOR=12
DEVLINKS=/dev/mx6
TAGS=:uaccess:seat:
Regards,
SImon
at this point I have no explanation why the device is being read as a Samsung 1 wire device. Have you tested this after a clean reboot with no 1 wire devices plugged in to see how a fresh kernel boot enumerates the port?
Hi Jon,
Well I did attach a laptop and got the same result. It is just very hard to understand why ‘lsusb’ would report what it does.
I would be happy to set it up so you can ssh in while I fiddle with the physical cables if that would help?
Regards,
Simon
If the kernel is reporting that, I don’t know how much more data I will be able to obtain. This is really baffling to me. Thanks for providing the debug output I have requested. I think I need to evaluate things a bit more and will get back to you.