No COM detected after connecting to PC
-
@Juraj Is the core2 charged?
-
@Juraj I can share my issue and solution using an M5Core3SE and a Win11 computer.
When I connected the M5 to the USB-A port on the PC using a USB-A to USB-C cable, I got power, but no COM ports.
When I connected the M5 to the USB-C port on the PC (using a USB-C to USB-C cable), BOOM: COM port.
I haven't dug into it to see particularly why (best guess right now is the M5 connection uses both the legacy USB 2.0 connection as well as the SuperSpeed connection: one for the terminal and one for the M5 program data stream?)
Hope this helps.
-
@JourneymanWizard said in No COM detected after connecting to PC:
@Juraj I can share my issue and solution using an M5Core3SE and a Win11 computer.
When I connected the M5 to the USB-A port on the PC using a USB-A to USB-C cable, I got power, but no COM ports.
When I connected the M5 to the USB-C port on the PC (using a USB-C to USB-C cable), BOOM: COM port.
I haven't dug into it to see particularly why (best guess right now is the M5 connection uses both the legacy USB 2.0 connection as well as the SuperSpeed connection: one for the terminal and one for the M5 program data stream?)
Hope this helps.
so you are using 2 different cables and its ok on just one...no issue with pc, no issue with M5..check with dofferent A to C USB
-
@JourneymanWizard The USB A cable is power only not a data cable.
-
@robski I tried multiple cables. Every USB-A to USB-C cable failed, some of which I had used in the past for data transfer. I am only using 1 cable: USB-C to USB-C
@ajb2k3 To clarify: are you saying that somewhere in the Core3SE documentation it says that USB-A is power only? Could you link that or point me to it? I clearly need to dig into the hardware a bit more :)
-
@JourneymanWizard No, I'm saying that not all cables are power+data. some cables are data only.
Also for some reason I have noticed that cables of late have a high failure rate (conductors breaking.
You are a core3, Have you pressed the boot button?
Another thing I have also noticed that I have to use a USB hub between the device and the computer for some reason. -
No COMM with USB-A cable
Recently with the M5Atom, only the USB-C to USB-C cable from my MacBook is recognized as a valid PORT. If using USB-A the port will not show up.
Some teammates were trying to just use the
Serial Monitor- and did not have the USB C - USB C cable. Although in this case, they say the PORT shows up, but is just not selectable. I haven't seen that - it just doesn't show up for me.I have tried many different USB-A to USB-C cables, and none work.
It would be nice for M5Stack to chime in and let us know what works.
-
so your setup is:
Mac --- usb A to C cables --- M5Atomdoes Atom works on diff machine? I mean non Mac
-
@robski I did some testing. When the USB-A is plugged into a PC (com4) it definitely works - is recognized, etc. But using that same cable (and a couple others) the M5Atom is NOT recognized on the MacBook (sometimes).
A teammate still cannot get the USB-A to work on her MacBook. (I'll mention the dongle issue stated below).
Now for the strange part: After testing the PC, I plugged the same USB-A into my Mac and it was working. So I thought the PC somehow altered the M5Atom.
But trying a brand new M5Atom - it works on PC, but not on the MacBook. (So that altered theory was debunked).It's strange that looking at a post here from 2020 - the problem was reversed: the USB-A was the only one that worked on MacBook.
UPDATE different dongle works
I just tried a non apple dongle, and it is working. Most interesting.
UPDATE 2: apple dongle works sometimes
Strange, after working with that non-apple dongle, I re-tried the apple dongle,
and it works now (on this M5Atom).SO it's not a uniform problem.
Maybe the MacBook get's woken up after and recognizes that device once. I just tried a brand new M5Atom - and it didn't recognize it. Then started to recognize.
-
@konacurrents any mac related drivers missing by chance?
-
@robski not that I know of. As I mentioned, the USB-C works fine. It's the USB-A that is hit or miss on working. I think this is a mac issue as I search the net. Eg: here and here and mac ports
Just was wondering if anyone has had this issue as well. I'm not stuck but my co-worker (not a developer) couldn't get the USB-A on a mac dongle to work. I just wanted her to use the Serial Monitor - as I implemented commands the user can type is to do an OTA update or other things. So they just needed a Serial Monitor (and this issue crept in).
Thanks.
