VMWARE Ubuntu 18 - Cannot Recognise PYBOARD

The official pyboard running MicroPython.
This is the reference design and main target board for MicroPython.
You can buy one at the store.
Target audience: Users with a pyboard.
Post Reply
User avatar
devnull
Posts: 473
Joined: Sat Jan 07, 2017 1:52 am
Location: Singapore / Cornwall
Contact:

VMWARE Ubuntu 18 - Cannot Recognise PYBOARD

Post by devnull » Fri Apr 05, 2019 6:10 am

Fresh install abut an hour ago - Ubuntu cannot recognise the PYBOARD:

Code: Select all

dmesg
[   86.174022] usb 2-2-port1: attempt power cycle
[   88.154102] usb 2-2.1: new full-speed USB device number 10 using uhci_hcd
[   88.180832] usb 2-2.1: device descriptor read/8, error 2
[   88.313327] usb 2-2.1: device descriptor read/all, error 8
Any suggestions ??
Last edited by devnull on Sat Apr 06, 2019 1:53 am, edited 1 time in total.

rhubarbdog
Posts: 168
Joined: Tue Nov 07, 2017 11:45 pm

Re: Ubuntu 18 - Cannot Recognise PYBOARD

Post by rhubarbdog » Fri Apr 05, 2019 9:01 am

Can you interact via screen or what ever serial terminal you use

User avatar
devnull
Posts: 473
Joined: Sat Jan 07, 2017 1:52 am
Location: Singapore / Cornwall
Contact:

Re: Ubuntu 18 - Cannot Recognise PYBOARD

Post by devnull » Fri Apr 05, 2019 9:58 am

No, it just kept trying to enumerate continually.

Solved it by connecting it via a USB hub instead of directly to the USB port.

User avatar
devnull
Posts: 473
Joined: Sat Jan 07, 2017 1:52 am
Location: Singapore / Cornwall
Contact:

Re: Ubuntu 18 - Cannot Recognise PYBOARD (SOLVED)

Post by devnull » Sat Apr 06, 2019 1:52 am

Well it took quite a long time to resolve this and eliminate the need for a USB2 Hub.

When plugging in the Pyboard the pyboard was listed in the ESXI VM's devices as a USB device by Vendor Name and PID and was never enumerated by the VM O/S.

After applying this fix, the device is correctly listed as a "MicroPython Pyboard Virtual Comm Port in FS Mode"

But this problem only affects VMWARE/ESXI 6.5 and looks like it is caused by USB3 Port incompatibility of some sort, but I thought I would post the solution anyway just in case anybody else should encounter this and save them some time.

SSH into the ESXI Machine and execute the following & reboot the machine.

Code: Select all

esxcli system module set -m=vmkusb -e=FALSE

Post Reply