Please try not moving the goalposts - you're now talking about an ESP32 on an upgraded Raspberry Pi!
The upgrade is good. I assumed you'd be using Stretch because everyone should be. But
please try with the ESP8266 again. Are you sure that your one has enough flash? Some of the old ones have very little and you need to use a different MicroPython build.
If you upgraded Raspbian, you'll need to reinstall esptool:
Also, check that the device is on /dev/ttyUSB0. It could be anywhere:
One detail I neglected to add: in miniterm.py - which gets installed with PySerial when you install esptool - you have to hit
Return one or more times to get the
>>> MicroPython REPL prompt. Also in miniterm, to see the MicroPython REPL results, you have to type in these four commands:
Code: Select all
import os
os.uname()
import ubinascii
help(ubinascii)
The
os.uname() command is to check the version of MicroPython: if it's not recent, rshell cannot work. The
help(ubinascii) command is to further verify that MicroPython has the module you need.
I'm fairly sure that the problem is that your ESP board isn't flashed with MicroPython. Quite what's going wrong I don't know, but I just tried rshell with an ESP32 flashed with some other thing entirely (instead of MicroPython), and this is what I got:
Code: Select all
rshell --buffer-size=30 -p /dev/ttyUSB3
Using buffer-size of 30
Connecting to /dev/ttyUSB3 (buffer-size 30)...
Testing if ubinascii.unhexlify exists ...
Like you, it just hangs waiting for
ubinascii.unhexlify to exist, which it never will.
The syntax for flashing an ESP32 is
different from an ESP8266: read about it here:
Firmware for ESP32 boards
The fact you're seeing
flash read err in miniterm confirms that the image isn't written correctly.
‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.