ESP32 Feather V2 serial port not found (MacOS) Moderators: adafruit_support_bill, adafruit

[carpedatum]

I am just getting started with the Adafruit ESP32 Feather V2 (Product ID 5400). I bought a few of these and am working with Adafruit's Primary Guide for the product to familiarize myself. I am working with a Mac Pro (the 2013 trash can) running macOS Monterey (12.4). Since I've successfully used the Arduino IDE on this box for other projects, I'm following the Guide's Arduino IDE Setup section for the moment.

I have installed the CHP9102/CH34X driver as described, and rebooted and verified the installation as shown in the installation guide. Then I installed the ESP32 Board Support Package from GitHub. This all seemed to go swimmingly.

Then I set up the Arduino IDE (v1.8.13) as described and attempted to load the provided Blink program. I regularly get "the selected serial port [7425] Failed to execute script 'esptool' due to unhandled exception! does not exist or your board is not connected". Very sad. I tried a second Feather - same result.

I know it is connected because its neopixel is still doing its factory-supplied demo. I do have two ports that manifest when I plug in the cable, but it doesn't make much difference which one I pick. I've tried two different ports on the Mac and four different cables. One cable does produce a slightly different result - the Feather goes dark just before the error appears, as if it reset but could not continue. However the message remains the same - no Blink for you! Hitting the reset button on the board at that point (or unplugging/replugging) restores the demo program to operation.

Does anyone have any idea what else I might try?

[adafruit_support_carter]

Double check the board you are selecting in the Arduino IDE under Tools -> Board. Make sure Adafruit Feather ESP32 V2 is selected.
https://learn.adafruit.com/adafruit-esp ... -ide-setup

[carpedatum]

Hey thanks for that really quick response - much appreciated!

Unfortunately that isn't it.

Here's what I have under Tools (through many attempts now):

Screen Shot 2022-06-23 at 12.13.39 PM.png (83.5 KiB) Viewed 92 times

Any other thoughts? I did try reducing the upload speed to 115200 - didn't make a difference.

[adafruit_support_carter]

Thanks. Can you turn on verbose output and then try an upload and post all the Arduino upload messages here. Can take a look at the specific error it's hitting.

[carpedatum]

Sure! I have omitted the compilation and linking steps (a lot of bulk there and the forum software had objections) but here is the more relevant bit, I think:

Code: Select all | TOGGLE FULL SIZE

...
esptool.py v3.3
Creating esp32 image...
Merged 2 ELF sections
Successfully created esp32 image.
python3 /Users/dave/Documents/Arduino/hardware/espressif/esp32/tools/gen_esp32part.py -q /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/partitions.csv /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/adafruitfeatherblinktest.ino.partitions.bin
2022-06-23 14:54:14.259 xcodebuild[7070:159568] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-06-23 14:54:14.260 xcodebuild[7070:159568] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
/Users/dave/Documents/Arduino/hardware/espressif/esp32/tools/xtensa-esp32-elf/bin/xtensa-esp32-elf-size -A /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/adafruitfeatherblinktest.ino.elf
Sketch uses 251237 bytes (19%) of program storage space. Maximum is 1310720 bytes.
Global variables use 16416 bytes (5%) of dynamic memory, leaving 311264 bytes for local variables. Maximum is 327680 bytes.
/Users/dave/Documents/Arduino/hardware/espressif/esp32/tools/esptool/esptool --chip esp32 --port /dev/cu.wchusbserial54790485671 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size 8MB 0x1000 /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/adafruitfeatherblinktest.ino.bootloader.bin 0x8000 /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/adafruitfeatherblinktest.ino.partitions.bin 0xe000 /Users/dave/Documents/Arduino/hardware/espressif/esp32/tools/partitions/boot_app0.bin 0x10000 /var/folders/31/s26x2hxj5lg1tk71ylf5sdpw0000gn/T/arduino_build_793304/adafruitfeatherblinktest.ino.bin
esptool.py v3.3
Serial port /dev/cu.wchusbserial54790485671
Connecting.............Traceback (most recent call last):
  File "esptool.py", line 5387, in <module>

  File "esptool.py", line 5380, in _main
  File "esptool.py", line 4687, in main
  File "esptool.py", line 115, in get_default_connected_device
  File "esptool.py", line 664, in connect
  File "esptool.py", line 614, in _connect_attempt
  File "esptool.py", line 598, in bootloader_reset
  File "esptool.py", line 532, in _setDTR
  File "serial/serialutil.py", line 603, in setDTR
  File "serial/serialutil.py", line 473, in dtr
  File "serial/serialposix.py", line 715, in _update_dtr_state
FileNotFoundError: [Errno 2] No such file or directory
[7078] Failed to execute script 'esptool' due to unhandled exception!
the selected serial port [7078] Failed to execute script 'esptool' due to unhandled exception!
 does not exist or your board is not connected


The FileNotFoundError is a little baffling as that device does seem to exist:

Code: Select all | TOGGLE FULL SIZE

Daves-Mac-Pro-2:tools dave$ ls -l /dev/cu.*
crw-rw-rw-  1 root  wheel  0x16000007 Jun 23 11:40 /dev/cu.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel  0x16000005 Jun 23 11:40 /dev/cu.BoseQC35II
crw-rw-rw-  1 root  wheel  0x16000003 Jun 23 11:40 /dev/cu.usbmodem54790485671
crw-rw-rw-  1 root  wheel  0x16000001 Jun 23 15:18 /dev/cu.wchusbserial54790485671
 

Thanks for looking at this!

[adafruit2]

the only odd thing is its kind of an ancient mac - im assuming ya managed to install the driver by turning off driver signing right? and we know the drivers work for sure on an M1 and recent macbooks for upload...
can you open the serial console with the port selected? do you have another computer you could try?

[carpedatum]

Hoping you can clarify. The particular trash can I have was discontinued in December of 2019 - not yet three years ago (when the cheese grater came out) and it is running the latest version of macOS available to non-devs on any platform. Is an M1 chip required?

I installed the driver by telling the S&P applet in System Preferences to let the installer run anyway.

I can open the Serial Monitor in the Arduino IDE, if that's what you mean, but I'm not sure what I should see. If I have it open when I first plug in the Feather, I get this:

16:55:44.512 -> ESP32 Self Tester
16:55:53.126 -> ⸮⸮⸮

That timestamp is pretty accurate assuming Mountain Time (my time zone, coincidentally). Nothing additional appears in the serial monitor when the error is reproduced. As before the Feather just goes dark, as if it hangs post-reset, when the "does not exist" error comes up. What would one normally see? Or by "serial console" did you mean some other application?

I have myriad other computers - was just hoping to continue developing on this one. It isn't particularly energy efficient but with six 3.5GHz Xeon cores, it is still my daily driver desktop. I will perform the setup tasks on a Macbook Pro (Intel) next and post the results. Please LMK regarding that M1 question. I have an M1 mini but it is in mothballs as we just moved.

[adafruit2]

ok well it looks like the serial data part works, but i wonder if the auto-reset part of the serial chip does not. the drivers for sure work on M1 and other recent (non M1 macs). right now i just cant tell if its a mac-hardware issue or a feather-hardware issue. so the only thing i can recommend is seeing if you can upload with some other computer just cause then we can narrow down the two choices!