I've ordered 4 #esp32 units from one Amazon vendor. One works great. One worked and then died. One never got past "Retrieving sysname" after loading #micropython (I haven't tried the 4th board yet)
Ordered two more from another vendor. Hung on "Retrieving sysname"
Am I doing something wrong or are these things really flaky?
@syaochan On the left is the one I'm current struggling with, from the new vendor. The blurry thing on the right is of unknown working state, from the original vendor with 1.5 successes and 1.5 failures.
"Retrieving sysname" is actually from rshell. If I go right in with picocom, some times it will just not respond (not fail to connect, just no prompt) and other times I get a message about a corrupt filesystem.
@syaochan Neither #esp32 board from the new vendor write and boot a #micropython firmware. This is after spending a couple hours trying to get any other board to join my one successful one. (i.e. cable is fine, have the right firmware, etc)
I'm getting pretty sick of dicking around with just turning these things on. Is there a reliable vendor to buy from? Or maybe just a different #microcontroller that will run #micropython?
@syaochan omgomgomgomgomg
I realized that I was running #esptool installed from the #debian repo, not via `pip install`. So I did that.
1. 2.8 -> 4.5.1
2. No longer need to hold the boot button down
3. erase_flash works
4. *** SO DOES THE BOARD ***
#PraiseTheLord #TimeForNewErrorMessages #microcontroller #micropython #python #esp32
dr 🛠️🛰️📡🎧
syaochan