nanoff --listdevices crashing

[martinmcnally]

When i run nanoff --listdevices it just freezes and does nothing crashing PowerShell.

I can see my device in device explorer and can connect using PUTTY every thing seems normal. I have updated VS, removed and reinstalled nanoff, erased the firmware cache and re flashed the device etc.

Still shows No available COM port and crashing when running listdevices.

Any ideas?

Thanks
Martin

[alberk8]

I find that the nanoff --listports unreliable. on my machine it still list com ports that is non existent. The Device Manager is the only source of truth for com ports. I only trust COM port as listed there.

[josesimoes]

--listdevices operation may run into issues with COM ports provided by Bluetooth devices and other virtual ports.
At this time, because there is no way to specify a list of port to exclude from the search, I would recommend using it with caution.

[josesimoes]

As for --listcomports it's a simple wrapper to System.IO.Ports.SerialPort.GetPortNames() API from .NET anything not working as expected it's up to the OS...

[martinmcnally]

Any ideas how I can get VS to see this device?

[alberk8]

What is make and model of ESP32 that you are using now?

[martinmcnally]

ESP32-DEVKITC-32EESP32-WROOM-32E 4MB FLASHHopefully I didn’t get the wrong one. MartinOn Aug 5, 2024, at 5:48 PM, alberk8 ***@***.***> wrote: What is make and model of ESP32 that you are using now? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[josesimoes]

@martinmcnally this is what I'm getting right now on my VS setup (same versions as you have).

If there is no mention to the COM port of the nanoFramework device you have connected, that's because the SerialPort couldn't be opened. That means that something else on your system has opened that COM port and it's using it thus preventing the extension from querying the device...

Double check for other VS extensions or any other software using/searching COM ports. Arduino is one of those reportedly messing the search workflow.

[martinmcnally]

nanoff --target ESP32_REV3 --update --serialport COM1 --masserase

I switched it to COM1 to see if COM5 was the issue.

Ill keep trying to see what is up however VS is the only program running on the machine and its been reinstalled. Cant imagine anything else is using the COM ports but ill keep digging.

This the board (has one red LED on when plugged in).

[josesimoes]

@martinmcnally after VS is running if you unplug and plug back the USB cable, following the USB sound, do you see any message on that verbose output of the extension?

[martinmcnally]

I bought a new board arrived today and connects just fine in VS.

This one:
https://www.amazon.ca/dp/B0C9TGJRPH?ref=ppx_yo2ov_dt_b_product_details&th=1

Not sure what is up with the other one I bought from DigiKey but im glad this one is working.

Thanks for all the help.

--listdevices even works now too

Weird that the other board could run the firmware but not connect to it or show as a real device.

[alberk8]

one possibility is the LDO is not providing enough power (that is the three legged IC with a big pad on the opposite side) below the ESP32 module).