Thanks for the info, you found some great sources that did not come up in my search. I will break out my laptop to try again.
I did try it on my desktop and had no problem. The ESP32 that I am using is fresh out of the antistatic bag with no wires connected. I also used a known good one from an older project and got the same results. Both worked on my desktop.
I purchased my motherboard on my desktop partly because it has a ton of USB on the back so I do not need a hub. Since I do not have a hub, would it be safe to cut a USB cable and only reconnect the data pins and power it from a different source? I might end up having to buy a hub anyways, but I would like to have a test to find out for sure before I do. This would be my only use for it. I do have one of those USB testers that displays the power(volts and amps). I will have to remember where I put it.
Some troubleshooting items that I did that I forgot to include above:
- Swapped USB Ports (I tried them all)
- Disabled antivirus and window defender (temporarily)
- Confirmed the VID/PID were registering as the default, they were. That might also be important since it did return that information from the ESP32.
- Checked the USB driver install log and it had the correct VID/PID and nothing else looked out of place.
- I used multiple cables. The same cables worked on my desktop.
- Restarting with and without the ESP32 plugged in.
I should also note that the laptop is Windows 10 home and my Desktop that it worked on is Windows 10 Pro.
@madmisha Or find out why it is in or thinks it's in low power state. It's been a while since I messed with windows but I think I remember that at least 2 maybe more USB ports share a common controller. If all your connection attempts have been through the one controller then I would be very highly suspicious that is the cause.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
There are 2 controllers. None of the ports are working. After experimenting today, I noticed that one of the ports on the opposite side than I normally use gets a different error. I believe it's because the driver is not installed for that one, after uninstalling it so many time. But I am looking into it now.
@madmisha I realize you have probably done htis, but have you tried a SAFE boot?
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
Sure you can learn to be a programmer, it will take the same amount of time for me to learn to be a Doctor.
@madmisha I realize you have probably done htis, but have you tried a SAFE boot?
This sound's like a driver problem to me. I have sometimes in the past just deleted the ports entirely (some are hidden, so you have to enable to see them), and then let windows pick them back up on reboot, giving you the opportunity to manually select a driver.
Hi @madmisha et al,
As you say, it appears to have 'forgotten' to 'uprate' the USB output from the 'initial' 100mA default ....
I confess, I haven't totally understood this part of USB mythology ... it is confusing in that clearly 'USB power supplies' often appear to have nothing more than 'safety' fuse of 500mA or more, often based on PTC device.
I am vaguely aware the 'full' standard 'recommends' the port to start at a low current limit (e.g. 100mA), and it is up to the load to request more if it needs it, say up to 500mA with the 'older' USB standards. Exactly how this is implemented is less clear, but I have recollections of it being based on the value of a resistor connected between two of the pins, suggesting this may be part of the hardware implementation, rather than buried deep in software driver land.
As I said, the above paragraph may be full of junk, but I am not presently in a position to spend time looking it up, so please take with many pinches of salt, but maybe it gives a clue as to what to look for.
Good luck.
Dave
I couldn't find anything in my bios, setting wise. I might update the bios. I don't usually do that unless it's really needed.
I got a USB hub. It works and I have the com port showing up now, but in USB View, it looks almost the same except for some of the hex addresses are changed, as expected. It still says cannot read in low power state.
Thanks @davee , @zander and @ronbentley1
You guys really helped me work through the problem. I will have to do more research as to the low power setting on it. I will have to install the USB View on my desktop to see what it look like there.