21

How did you flash it, did you follow: https://github.com/OpenEVSE/openevse_esp32_firmware/blob/master/docs/wired-ethernet.md#for-rev-fg

It looks the unit is a boot cycle, probably caused by a corrupt flash. Try erasing the module, then do a full flashing including the bootloader and partitions file. These can be downloaded from the release page.

esptool.py erase_flash

Then

esptool.py --before default_reset --after hard_reset write_flash 0x1000 bootloader.bin 0x8000 partitions.bin 0x10000 olimex_esp32-gateway-f.bin

22

Hi @gadgetbazza did you succeed in flashing the ethernet board in the end?
I too have a rev G ethernet board with 4.0.1 firmware on it at present, which cannot be flashed via the UI. I plan to update to 5.1.1 and would appreciate any advice before flashing the board.

Thanks for any advice you can give

Jules

23

Since I posted here, I went ahead and flashed it anyway and was eventually successful. Once I had found a way of getting esptool to run.
I decided to leave the olimex board in place so couldn’t use my desktop. I first tried a Chromebook with crostini and found that esptool couldn’t see any serial ports. I then tried ubuntu on another laptop installed the latest esptool, but found that it failed part way through flashing with a missing file stub_flasher_32.json, this seems to be a known problem. See https://groups.google.com/g/linux.debian.bugs.dist/c/xtmno2U9P0g Lastly I installed esptool on windows which worked with python -m esptool and otherwise the same parameters from --before, which worked!
I installed 5.1.1 with new UI which looks much tidier. More importantly the http interface now corresponds with recent documentation.

24

Nice work getting the FW uploaded!

I often use a Chromebook with Crostini to run esptool, you should see this popup when the USB to serial device is connected asking if you want to enable Linux access, you need to choose ‘Connect to Linux’ to allow Crostini and therefore esptool to be able to access the serial port.

Screenshot 2024-08-12 00.58.09

The same option is available under: Settings > About > Linux dev environment > Manage USB devices

25

HI Jules,

Sorry for the late reply, I was away. Yes I did fix it in the end with the full flash as advised by @glyn.hudson

My first attempt was using the command on post 16 of this thread. I’m not familiar with the parameters but I see two addresses listed 0x1000 and 0x10000 but only 1 bin file, maybe there is something I did wrong there.

Anyhow, thankfully the charger worked as a dumb charger without the ESP32 functioning in the short term and everything back to normal with the boot loader and partition bin files added.

Thanks
Barry