Interesting, I get the opposite! On the “left side” it repletely disconnects while on the right side its been connected without problems.
And on the left, if I have my TB3 dock connected then connect the reader, it makes the machine reboot!
ok. I’m gonna spend some time today trying to narrow this down. so far, the FT device is the only thing I can get to trigger this but we’ll see what else I have laying around here.
Another device I found that doesn’t work on the right side but does work on the left
idVendor=10c4, idProduct=ea60, bcdDevice= 1.00Product: CP2102 USB to UART Bridge Controller
I’ve swapped the USB ports around, tried USB A vs USB C, removed all expansion cards etc and still run into the same behavior. @Kieran_Levin did you receive your adapter? I can ship you some of the ones that are causing me trouble if it would be helpful. I’ve tried several different types of devices from bluetooth adapters to microphones and it seems to be limited to a few USB-Serial adapters and localized to just one side of my machine.
1 Like
@Scratch I got my adapter and I can replicate the issue on the upper right, and lower left ports. When this happens the PD controller reboots and both ports on that side are disconnected and reconnected again. (These are both port 0 on the PD controller on each side)
It will take some time to root cause this and get a fix, but while this is getting fixed I think you can use the other 2 ports.
11 Likes
@Scratch I was able to root cause this to a firmware bug in our PD controller.
It looks like this device has a high inrush current, and causes the overcurrent detection signal to glitch. We are supposed to debounce this in firmware, but the code doing the debouncing was only handling this correctly for 1 port on each controller.
If an overcurrent condition happens on the upper right or lower left ports on bios 3.03 or below it will cause both ports to reset on that side.
To mitigate this, use the other port on each side until the firmware update is available.
I am planning on rolling this into release 3.04 assuming all our testing is ok.
I don’t have an exact ETA for this update yet.
20 Likes
right on! That had to be a huge pain to track down, well done!
3 Likes
I have two SanDisk 16B USB 3.0 drives that show in windows up but go away and throw errors when you start copying data off them. It happens on both right side ports. Have not tried the left side yet. Other USB flash drives or USB external SSD drives work fine. These same SanDisk drives that don’t work in the Framework work fine in all my other computers.
Is this the same issue as above?
I found a flash drive with a strange behavior. Specifically Kanguru Flashblu30 8gb, 32gb, and 64gb. Plugging them directly into the USB-A expansion card results in nothing happening. No device detected and the LED on the drive doesn’t light up. That said, if I use an A to C converter, including the A expansion card, and connect it to a C card, the flash drives work properly and I can read/write at full speed. All my other flash drives work properly with the USB-A card.
So you mean you can take the A card out of the computer and plug it into one of the C cards, and that works, but the A card directly doesnt? Maybe you just have a problem with the port the A card is normally in.
I’ve seen this before with some USB 3 drives. The connectors seem to be just a hair too long, Try plugging it into the A port and then slowly sliding it back out, fractions of a mm at a time, and I bet it will suddenly pop up as available.
1 Like
I don’t think so, it wasn’t detected regardless of which slot the A card is in.
I just tried this and slowly removing the drive still does nothing, however it does show up when I slowly insert the drive! Thank you for this suggestion, now I don’t need the weird double adapter workaround.
I will say I’ve noticed the same thing, detection being kind of wonky with my USB-A card when using a USB 3 stick. I only have the one USB 3 stick so I haven’t been sure if it’s the stick or the port at fault.
Is the suggestion that there’s something out-of-spec with the USB-A card? I’d have thought the physical port would be a quite standardized part. Surely “slow insertion” shouldn’t be required, though.
Was this fixed in 3.06?
This issue is fixed in Bios 3.06
1 Like
Can confirm, my flash drive issue was fixed after installing the 3.06 bios update. Thanks!
Still an issue for me with BIOS V3.07 on Windows 10. Plugging in slowly does work with this USB 3 drive but plugging in quickly and the drive does not show up.
I did however find that if you plug in the drive quickly and it does not show up, if you then open the device manager and click the ‘Scan for hardware changes’ button the drive will show up. This makes me think that this could be fixed in software.
Hi @Kieran_Levin,
I too am facing this issue, lower left port, 3.07 BIOS, Windows 10. Let me know if you need any other information as well. Framework USB C to USB A adapter.
The same adapter works fine on the bottom right port.