-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken pipe while flashing over USB, on macOS only #171
Comments
Can you try using master? We recently merged #169 which should fix this issue. |
I seem to get a different failure when using the latest from master:
|
I've unfortunately never seen this error in practice, so I'm a little stumped as to what the issue is. I run macOS as well and have never run into issues flashing the ESP32-S3, although I haven't used it much. Just out of curiosity, which version of macOS are you running? Also if you're able to share your project (either a repo or a zip file, or whatever is easiest) that would be helpful so I could at least try to reproduce this. |
We were seeing this on macOS Monterey 12.1, and trying to flash the app from this esp-idf example: https://github.com/espressif/esp-idf/tree/v4.4/examples/wifi/getting_started/station |
I can't seem to reproduce this.
espflash --bootloader build/bootloader/bootloader.bin build/wifi_station.elf
Serial port: /dev/tty.usbserial-1110
Connecting...
Warning: could not detect flash size (FlashID=0x3980C2, SizeID=0x39), defaulting to 4MB
Chip type: ESP32-S3
Crystal frequency: 40MHz
Flash size: 4MB
Features: WiFi, BLE
MAC address: 84:f7:03:80:09:64
[00:00:01] ######################################## 13/13 segment 0x0
[00:00:00] ######################################## 1/1 segment 0x8000
[00:00:37] ######################################## 363/363 segment 0x10000
Flashing has completed! Perhaps this is a hardware issue? |
I was also unable to reproduce the problem on my M1 running Monterey, unfortunately. |
We tested on two different Intel Macs (one is a MBP 2019, the other is a MBP 2017), and encounter this issue. |
I wasn't able to reproduce this issue on my ESP32-S3-DevKitC-1-N8R2, so I picked up an ESP32-S3-DevKitC-1-N8 (the same devkit that @allison-n-h is using), and I'm able to reproduce the issue there on my M1 Mac with espflash 1.4.1:
I can't reproduce it on espflash 1.5.1 or the current tip of the master branch (d5583ef), but that's only because I get a different error there (which is again the same one that @allison-n-h sees on those versions of espflash):
|
Thank you for the additional information! This at least highlights some hardware differences which may be causing these issues. I only have the
Based on the above data it seems possible that somehow the lack of PSRAM is causing this. I will see if I can get some more hardware to verify this, though I'm not sure when I will receive it. |
@mykmelez @allison-n-h If you could read the eFuse values from your devkit which exhibits the issue (ESP32-S3-DevKitC-1-N8) and post them here, it would be very helpful. This can be done using |
@jessebraham Perhaps we could add some more debugging information to see which of the WriteReg commands fails? |
Here's the output for my ESP32-S3-DevKitC-1-N8:
|
I think I found the bug (it was my bad!), could you try out #190 and see if it works? |
@MabezDev that fix seemed to work for me!
|
Trying to test flashing an image using the USB port on an ESP32S3 DevKit-C-1-N8. For larger images (like the wifi station example from the idf), flashing fails about ~75% through the image:
This seems to only be an issue with espflash on macOS and using the USB port on the devkit. Using the UART port works as expected, and using the native
idf.py flash
works as expected. It also seems to occur only 'larger' images - for example, flashing the hello_world example from the IDF completes successfully. Testing this on a Windows 11 machine, we don't see this issue either, so it does seem to be macOS specific.We did verify we are using the 1.4.1 version of espflash.
The text was updated successfully, but these errors were encountered: