# Cannot get serial console **URL:** \ **Category:** NXP LX2160\ **Created:** [June 5, 2021, 10:43pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64 "2021-06-05T22:43:46Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![sjg20](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sjg20](https://community.solid-run.com/u/sjg20)\ **Post date:** [June 5, 2021, 10:43pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/1 "2021-06-05T22:43:46Z")
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 ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 6, 2021, 8:20am UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/2 "2021-06-06T08:20:25Z")
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. ---
**Author:** ![sjg20](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sjg20](https://community.solid-run.com/u/sjg20)\ **Post date:** [June 6, 2021, 3:15pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/3 "2021-06-06T15:15:39Z")
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 ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 7, 2021, 4:27am UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/4 "2021-06-07T04:27:10Z")
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? ---
**Author:** ![sjg20](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sjg20](https://community.solid-run.com/u/sjg20)\ **Post date:** [June 7, 2021, 2:54pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/5 "2021-06-07T14:54:36Z")
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 ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 8, 2021, 5:23am UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/6 "2021-06-08T05:23:21Z")
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 ---
**Author:** ![sjg20](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sjg20](https://community.solid-run.com/u/sjg20)\ **Post date:** [June 8, 2021, 2:55pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/7 "2021-06-08T14:55:15Z")
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 ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 9, 2021, 9:45am UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/8 "2021-06-09T09:45:22Z")
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? ---
**Author:** ![sjg20](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sjg20](https://community.solid-run.com/u/sjg20)\ **Post date:** [June 10, 2021, 2:04pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/9 "2021-06-10T14:04:24Z")
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 ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [June 11, 2021, 12:45pm UTC](https://community.solid-run.com/t/cannot-get-serial-console/64/10 "2021-06-11T12:45:05Z")
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.