How to load Firmware without .hex or .bin file

Taimoor · 9 March 2025 10:47

I successfully customized my OpenEVSE GUI and can access it on localhost. I followed the instructions from the official GitHub repository: OpenEVSE GUI v2.

After building the project, I noticed that it only updates some JavaScript files in the dist folder and does not generate any .hex or .bin files. Since I usually upload firmware using the OpenEVSE programmer, I am unsure how to proceed with flashing my custom GUI onto the controller.

Could someone guide me on how to properly upload my modified GUI firmware to the OpenEVSE controller?

Thanks in advance!

Guillaume_S · 20 March 2025 10:25

You need to build a new firmware with your gui modification from firmware repository:

put your gui sources in /gui-v2/ folder, and build it:

cd gui-v2
npm install
npm run build

then build the firmware using platformio :

github.com/OpenEVSE/openevse_esp32_firmware

docs/developer-guide.md

master

# Development Guide

## Compiling and uploading firmware

It is necessary to download and build the static web assets for the GUI before compiling and uploading to the ESP.

### Building the GUI static assets

The GUI static web assets are minified and compiled into the firmware using a combination of Webpack and a [custom python build script](../scripts/extra_script.py).

You will need Node.js and npm installed: <https://nodejs.org/en/download/>

In addition, the GUI is now maintained in a [separate repository](https://github.com/OpenEVSE/openevse-gui-v2/) and is included as a Git submodule.

If the `gui` directory is empty, use the following to retrieve the GUI source and fetch the dependencies:

```bash
git submodule update --init --recursive
cd gui
npm install

This file has been truncated. show original

Taimoor · 25 March 2025 05:15

I hope this message finds you well. I am reaching out regarding an issue I have encountered with my OpenEVSE system.

When I connect the ESP32, the device begins blinking a yellow light continuously. After a brief period, the light changes to purple. Additionally, the display on the unit shows the error message: “OPENEVSE Module Missing.”

I have checked and confirmed that no modules are missing from the system, so I am uncertain what this error signifies. Could you kindly clarify the meaning of this error and provide guidance on how to resolve the blinking lights and error message?

I appreciate your assistance and look forward to your response.

@Guillaume_S

[Edited to include ‘@’ link - Moderator (RW) ]

Guillaume_S · 25 March 2025 16:09

This means the Wifi module ( aka ESP32 ) doesn’t see the Evse module ( aka the Atmega part ) . So booth are either not connected with the cable, or there’s a problem with firmware/hardware of Evse module.

Taimoor · 26 March 2025 03:54

How can we rectify this issue where the WiFi module (ESP32) is unable to detect the EVSE module (Atmega)? Could you please provide possible solutions, including checking hardware connections, firmware compatibility, or any necessary troubleshooting steps? I also attached my Connection of EVSE

@ Guillaume_S