USB problem with OS X #586
Comments
|
My PyBoard seems is on the way and, although I'm mainly a Linux user, I have an OSX laptop and I know how to deal with it to debug hardware issues. I'll check and try to collect data for this issue ASAP as I have my board. |
|
@skgsergio, yes, your board is on its way. Any info you could give on OSX would be great. Here is 1 report of not working: Mac Mini, latest version, i5 processor, running OS X Mavericks. Mac refuses to see the board at all. |
|
No pyboard, but I have hardware similar enough to run and test Micro Python. |
|
Okay, so one OSX report was simply a problem with the micro USB cable. Changing the cable fixed the problem straight away. We shall see, but perhaps this is not a software problem after all. |
|
Wanted to mention that one of known USB debugging measures is trying to connect via an external hub. I have some doubts for this case specifically, as Pyboard might overload an unpowered hub, but well, as one of debugging steps, why not to suggest "if you have an external hub, try to connect board via it" (but definitely not "go and buy a hub if you don't have one, it will surely help"). This is not MacOS-specific of course, posting here, as it appears to catch the most attention in this regard so far. |
|
In the other known-case, it was also a broken/faulty USB cable (2 of them in fact!). So it seems that there are no more outstanding issues of pyboard USB driver on Mac. Reopen if things change. |
|
I can confirm it working on my 3 machines with an Amazon Basics USB 2.0 cable. |
|
Thanks @skgsergio, good to know. |
This PR refines the _bleio API. It was originally motivated by the addition of a new CircuitPython service that enables reading and modifying files on the device. Moving the BLE lifecycle outside of the VM motivated a number of changes to remove heap allocations in some APIs. It also motivated unifying connection initiation to the Adapter class rather than the Central and Peripheral classes which have been removed. Adapter now handles the GAP portion of BLE including advertising, which has moved but is largely unchanged, and scanning, which has been enhanced to return an iterator of filtered results. Once a connection is created (either by us (aka Central) or a remote device (aka Peripheral)) it is represented by a new Connection class. This class knows the current connection state and can discover and instantiate remote Services along with their Characteristics and Descriptors. Relates to micropython#586
There have been reports by some users of the stmhal/ USB device not working at all on their Mac OS X machine. The pyboard works, but there is no mass storage device, nor any serial device. At this point I have very little information about this.
I want to collect here information about which OS X versions have the problem, and any other details (eg does DFU work?).
The text was updated successfully, but these errors were encountered: