openevse_wifi_tft_v1.bin problem

[ToniRos]

openevse_wifi_tft_v1.bin binary fails when installing it in the module https://store.openevse.com/collections/all-products/products/openevse-color-lcd-wifi

openevse_wifi_v1.bin has been tested in a standard module and works perfectly

Compiling the sources produces a binary that doesn't work either.

Any idea what to try?

Greetings.

[ClassicGOD]

Same here. In debug console it goes to 99% and stops. Web interface remains accessible even after restarting so at least it does not brick the EVSE.

My TFT module is currently on "v5.1.0_modified" - it was shipped to me with this firmware about a month ago.

Debug console extract attached.
OpenEVSE WiFI debug.txt

[FrancoisBourdon]

Hello all,
I am also getting the same problem.

Trying to update the installed v5.1.0_modified openevse_wifi_tft_v1.bin file on my OpenEVSE Color LCD / WiFi board using either the UI or the Web Interface and I get the following results:

• updating to v5.1.1 fails (UI stuck at ~99% progress or Web Interface returns "Error: 4")
• updating to July 11th dev build fails (UI stuck at ~99% progress or Web Interface returns "Error: 4")
• "updating" to v5.1.0_modified succeeds (UI progress completes or Web Interface returns "OK")

For the Web Interface update I use the following command and return.

/tmp/5.1.1$ curl -F 'file=@openevse_wifi_tft_v1.bin'  http://10.165.122.130/update && echo
Error: 4

According to the following define, it appears to be related to a lack of space
#define UPDATE_ERROR_SPACE (4)

As mentionned before, if I update to the already installed and working v5.1.0_modified with the following command, it returns OK.

/tmp/5.1.0$ curl -F 'file=@openevse_wifi_tft_v1.bin'  http://10.165.122.130/update && echo
OK

I dont have the specific LC231X USB debug adapter, nor there is a DEBUG connector mounted on the display PCB, so I could not try to delete everything as suggested here:
https://github.com/OpenEVSE/openevse_esp32_firmware/blob/master/docs/user-guide.md#via-usb-serial-programmer

In all cases, the OpenEVSE Color LCD / WiFi board is still running (it is not bricked) with v5.1.0_modified

Hope this data helps in the investigation.

Best regards,
François

[jeremypoulter]

This worked for me ok, however I do have a theory, @chris1howell can you confirm the command used to flash the device in the factory? Can you also let me know if you use the same partitions.bin as the non-LCD board?

Also if anyone else is able can you try flashing the latest dev build using Platform IO?

[jeremypoulter]

Note you don't need the debug connector to flash using Platform IO, the EVSE connector is used for programming for exactly this reason. Connect to a USB to UART adapter, hold down the boot button and press the reset button should put it into programming mode.

[ToniRos]

I tested with Patform IO and firmware loads OK:

git checkout master
...
pio run -e openevse_wifi_tft_v1 -t upload
...
Writing at 0x001e75c3... (98 %)
Writing at 0x001ec9c1... (100 %)
Wrote 1972112 bytes (1340651 compressed) at 0x00010000 in 19.6 seconds (effective 805.5 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Now I try with esptool:
esptool.py --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 openevse_wifi_tft_v1.bin

And seems that works:

In the console apperars:

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13964
load:0x40080400,len:3600
entry 0x400805f0
E (412) psram: PSRAM ID read error: 0xffffffff
[    55][E][vfs_api.cpp:105] open(): /littlefs/schedule.json does not exist, no permits for creation
$GV^35

[jeremypoulter]

Thanks, I suspect the boards have been flashed with the wrong partitions file. @chris1howell

[FrancoisBourdon]

Note you don't need the debug connector to flash using Platform IO, the EVSE connector is used for programming for exactly this reason. Connect to a USB to UART adapter, hold down the boot button and press the reset button should put it into programming mode.

Oh! Thank you Jeremy! In that case I actually have what is needed to use the primary serial port to perform the format with the proper partitions as you are suggesting in another post. Thanks again for following up

[FrancoisBourdon]

Hello all,
I was able to fix my problem by installing esptool & PlatformIO and recompiling the latest version of the firmware.
Then I was able to download the firmware (including the proper partitions) to my device using a USB to serial comm adapter connected to serial port of the display board where the OpenEVSE board usually connects.
To put the display board in bootload mode, I had to press Boot button, then Reset button.

git clone https://github.com/OpenEVSE/ESP32_WiFi_V4.x.git
pio run -e openevse_wifi_tft_v1 -t upload

Also, after an initial success, I had to completly erase the device flash due to a crash that left me with a device stuck with a blank screen.

esptool.py erase_flash
esptool.py write_flash 0x000000 blank_1MB.bin 0x100000 blank_1MB.bin 0x200000 blank_1MB.bin 0x300000 blank_1MB.bin
pio run -e openevse_wifi_tft_v1 -t upload

Thanks for the help.
François

[rbray89]

I'm assuming this is a size issue? I was able to "sidegrade" to the non-tft version. If we can update the partition info in the non tft version, people should be able to migrate to that as an intermediate step to update to current tft bins.

[andy-81]

I am having the same issue as this having just received my unit. Happy to follow the details above to resolve the issue but keen not to have the same problem when updating again, is the plan to resolve the issue with a new release of firmware or should I follow the steps to fix this one knowing that I will not have the issue again when the next firmware is released?

Any advice on how best to solve the issue would be appreciated 😄

[jeremypoulter]

Yeah if you do the above that will fix the device going forward

[ClassicGOD]

Yeah if you do the above that will fix the device going forward

Is there any official fix or guide coming? I'm asking because I'm lazy as hell and I will wait if that means I don't have to remove the display from my evse, drag it back to my PC, dig out UART adapter that I have not used for so long that I'm pretty sure is lost to time and flash it that way.

Is there an action plan for people that don't have a necessary hardware or know how to flash the boards themselves? Because it sounds like all boards in at least the latest production run are affected.

[jeremypoulter]

Possibly, we need to see if we can reduce the firmware size so it fits in the existing partition size, then we need to see if you can rewrite the partition table from the firmware

[ausil]

I just opened up and flashed two units that were impacted. Ideally, an OTA update will fix it, I suspect many will not have the necessary tools or connectors. I had to use some dupont wires to get things wired up right to do the update.

[jeremypoulter]

python3 ~/.platformio/packages/framework-arduinoespressif32/tools/gen_esp32part.py min_spiffs.csv partitions_4mb.bin
python3 ~/.platformio/packages/framework-arduinoespressif32/tools/gen_esp32part.py openevse_16mb.csv partitions_16mb.bin

[jeremypoulter]

https://gist.github.com/floitsch/ed2530caa613581057d8998dee0a911f

[blaxer]

I think I might be experiencing the same issue but I am very new to this so I apologize in advance for my ignorance.

But, I was able to get the charger up and running, everything seemed to be fine but it said there was a firmware update to v5.1.1 from v5.1.0_modified so I went ahead and did that. Now everything seems to be working, charging is good, web interface is fine, MQTT working, except the TFT display is completely blank / dead / off (no backlight)...

UPDATE:

For anyone who finds this thread because their LCD is blank these steps worked for me:

esptool.py erase_flash
esptool.py write_flash 0x000000 blank_1MB.bin 0x100000 blank_1MB.bin 0x200000 blank_1MB.bin 0x300000 blank_1MB.bin
pio run -e openevse_wifi_tft_v1 -t upload

Thank you @FrancoisBourdon you are a life saver!

[UKenGB]

I've recently received 2 large LCDs, one with a new lid to upgrade an existing EVSE I already have and the other part of a full kit. The first new LCD I've tried has this problem. Current firmware is v5.1.0 modified. It tells me the latest is v5.1.1. So I press the Update button and choose 'direct from GitHub' and as per usual says it's starting the download, but it gets no further. Never gets to the update progress bar. In fact it seems stuck and I have to refresh the page.

Looking here, the actual file for this display seems to have been removed which might explain the problem?

It is currently running on v5.1.0 modified, but what's the actual solution to this. Is there a new correct v5.1.1 (or later) being prepared? When might we see that?

[andy-81]

Any update on this?

I have an FT232 serial board which I tried to update as per the above details however I was unable to connect to the display board. It must have been the wiring as the error was that it could not connect to the USBtty0 board.

I wired the VCC to the 5-12v pin, GND to the GND, RX to TX, TX to RX. I even tried switching the TX/RX pins around just incase but still no connection. The display turned on so it should have been powering the esp board.

This is the command I was using:
esptool.py --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 openevse_wifi_tft_v1.bin

and the FT232 board is an older version of this one with only 3.3v or 5v as the options (obviously I have it set to 5v at present:
Board

I also notice the download is no longer available for the TFT board for 5.1.1 firmware, is this because it is being worked on at present? I downloaded the original file while it was available so have been trying with this firmware.

[jamarju]

@andy-81 check that your board is in bootloader mode: press boot, then reset, then release reset and finally release boot. The screen should go black meaning you entered the bootloader, then you can flash. I just upgraded from 5.1.0_modified to 5.1.2 using your exact command line:

esptool.py --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 openevse_wifi_tft_v1.bin

The ESP32 will stay in the bootloader so press reset again to get out of it after it's done.

Wiring:

• VCC - 5-12
• GND - GND
• RX - TX
• TX - RX

My FT232 is also in 5v mode. Also doublecheck the connections if you are using the provided harness as pins RX/TX and 5-12V/no label are crossed.

I also flashed from source before that using pio run -e openevse_wifi_tft_v1 -t upload before flashing the released 5.1.2 bin file but I'm not sure that actually mattered.

[andy-81]

@andy-81 check that your board is in bootloader mode: press boot, then reset, then release reset and finally release boot. The screen should go black meaning you entered the bootloader, then you can flash. I just upgraded from 5.1.0_modified to 5.1.2 using your exact command line:

esptool.py --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 openevse_wifi_tft_v1.bin

The ESP32 will stay in the bootloader so press reset again to get out of it after it's done.

Wiring:

• VCC - 5-12

• GND - GND

• RX - TX

• TX - RX

My FT232 is also in 5v mode. Also doublecheck the connections if you are using the provided harness as pins RX/TX and 5-12V/no label are crossed.

I also flashed from source before that using pio run -e openevse_wifi_tft_v1 -t upload before flashing the released 5.1.2 bin file but I'm not sure that actually mattered.

Thanks for that, I managed to flash but now my screen wont turn on and the esp board isnt booting. When I open the serial port and look at the output I am getting an

rst:0x10 (RTCWDT_RCT_RESET), boot:0x13

with a load of invalid header signals which just keeps repeating. any ideas?

[jamarju]

Try this:

"
The current repartition process for the TFT LCD in the short term requires a USB => Serial adapter and esptools (requires Python and pyserial).

Download the 5.1.2 - openevse_wifi_tft_v1.bin, bootloader_16mb.bin and partitions_16mb.bin from
https://github.com/OpenEVSE/openevse_esp32_firmware/releases/tag/v5.1.2

Connect the module to the USB => Serial adapter, then put the module in bootloader mode by holding BOOT and then pressing RESET then release BOOT

Run the command:

esptool --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_size=detect 0x1000 bootloader_16mb.bin 0x8000 partitions_16mb.bin 0x10000 openevse_wifi_tft_v1.bin
"

(as suggested by the OpenEVSE folks)

[andy-81]

Try this:

" The current repartition process for the TFT LCD in the short term requires a USB => Serial adapter and esptools (requires Python and pyserial).

Download the 5.1.2 - openevse_wifi_tft_v1.bin, bootloader_16mb.bin and partitions_16mb.bin from https://github.com/OpenEVSE/openevse_esp32_firmware/releases/tag/v5.1.2

Connect the module to the USB => Serial adapter, then put the module in bootloader mode by holding BOOT and then pressing RESET then release BOOT

Run the command:

esptool --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_size=detect 0x1000 bootloader_16mb.bin 0x8000 partitions_16mb.bin 0x10000 openevse_wifi_tft_v1.bin "

(as suggested by the OpenEVSE folks)

Thank you, I was worried I would be stuck for a lot longer. This solved it for me, so it obviously needed the partition table with it to resolve.

All updated now so hopefully future updates should be straight forward from now on.