[SOLVED] Linux pytrack USB to serial
Tamm Buhez last edited by Tamm Buhez
When I plug the pytrack on the USB port of my laptot, the device is not recognized as a USB serial device converter. I got the following log looping over and over:
Jun 13 02:07:27 mp-de-053 kernel: [ 727.050092] usb 1-1: USB disconnect, device number 85
Jun 13 02:07:28 mp-de-053 kernel: [ 727.467729] usb 1-1: new full-speed USB device number 86 using xhci_hcd
Jun 13 02:07:28 mp-de-053 kernel: [ 727.608256] usb 1-1: New USB device found, idVendor=04d8, idProduct=f014
Jun 13 02:07:28 mp-de-053 kernel: [ 727.608258] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 13 02:07:36 mp-de-053 kernel: [ 735.651707] usb 1-1: USB disconnect, device number 86
Jun 13 02:07:36 mp-de-053 kernel: [ 736.067624] usb 1-1: new full-speed USB device number 87 using xhci_hcd
Jun 13 02:07:36 mp-de-053 kernel: [ 736.207949] usb 1-1: New USB device found, idVendor=04d8, idProduct=f014
Jun 13 02:07:36 mp-de-053 kernel: [ 736.207951] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 13 02:07:44 mp-de-053 kernel: [ 744.251230] usb 1-1: USB disconnect, device number 87
Jun 13 02:07:45 mp-de-053 kernel: [ 744.667687] usb 1-1: new full-speed USB device number 88 using xhci_hcd
Jun 13 02:07:45 mp-de-053 kernel: [ 744.807839] usb 1-1: New USB device found, idVendor=04d8, idProduct=f014
Jun 13 02:07:45 mp-de-053 kernel: [ 744.807841] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 13 02:07:53 mp-de-053 kernel: [ 752.850206] usb 1-1: USB disconnect, device number 88
I tried to change without succeeded the USB cable. Also disabling USB3 in the BIOS does not help.
My wipy2 expansion board is well recognized as a FTDI USB Serial Device converter and works like a charm.
I'm running Debian 8.8 with a 4.9.0-0.bpo.3-amd64 kernel (4.9.25-1~bpo8+1)
Any help would be grately appreciated.
You should create a new post as your problem is really different from the original I posted to avoid confusing people.
That beeing said, I see a typo on address path "/dev/ttyUS0" should be /dev/ttyUSB0"
If you want to continue the discussion please create a new topic.
I work with Atom environment.
When I want to connect, with the plugin, I have the following message :
Failed to connect (Error: Port is not open). Click here to try again. Failed to connect ( error..
My seetings are :
failed to set dtr/rts
HI @jacquej1 ,
What is exactly your problem? I also have those messages and my device works very well.
When I connect the Pytrack and send the linux command "dmesg", I have the following message "failed to set dtr/rts". Before I have updated the firmware with fd-util -D ...
So, what is way to solve this problem ?
I finally successfully updated the device as root user. Problem resolved. Thanks a lot!
@jmarcelino I already tried after you first answer but dfu-util says that the device is not in DFU mode.
jmarcelino last edited by
Thanks, I'm not sure what it can be but since it is in DFU mode you can try upgrading the firmware using the procedure at https://docs.pycom.io/pycom_esp32/pycom_esp32/toolsandfeatures.html#updating-pysense-and-pytrack-firmware
dfu-util -D ...step right after Linux picks up the device, when
New USB device found, idVendor=04d8, idProduct=f014
shows up in the log. You only have 7 seconds after that to enter the dfu-util command.
Hope this helps!
Hello @jmarcelino ,
Thank you very much for your help. To answer your questions, I'm not pressing the buttton at all, it seems indeed stuck. I already tried to press the button without effect.
With a multimeter the continuity is established when I press the button.
The behaviour is identical with and without the WiPy and nothing is connected to the G4/P14 pin.
Is there a way to "unstuck" the device? I received it yesterday, it's a bit disapointing.
jmarcelino last edited by
That's acting as if the PyTrack was constantly entering DFU mode.
If you're not consciously pressing the button on the board, perhaps it's somehow 'stuck', try pressing it or maybe tap it to see if it somehow dislodges. Can you check the button for continuity with a multimeter?
Is it possible you have something connected to the G4/P14 pin on your WiPy/LoPy/..?