jeremypoulter
commented
11 months ago What enviroment are you using to compile? Can you show a full log? We do build via a GitHub workflow 
and that is passing.
Open aaronwesel opened 11 months ago
jeremypoulter
commented
11 months ago What enviroment are you using to compile? Can you show a full log? We do build via a GitHub workflow and that is passing.
aaronwesel
commented
11 months ago I am using vscode pio, I followed all the instructions. I am not sure where to get these logs. Here is screenshot if that helps.
jeremypoulter
commented
11 months ago Which board/env are you building? Are they actually compilation errors from Platform IO, or just VSCode trying to parse the code? The latter may just be a VS Code miss configuration of VS Code and not impact building/uploading/etc
aaronwesel
commented
11 months ago Yes, these are build errors. It is the same for every env I try. Here is the terminal output.
Processing openevse_esp32-gateway-e_dev (board: esp32-gateway; platform:
@.***; framework: arduino)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Verbose
mode can be enabled via -v, --verbose option
Firmware Revision: -D BUILD_TAG=local_master_ff55cf44_modified -D
BUILD_HASH=ff55cf44_modified
CONFIGURATION:
https://docs.platformio.org/page/boards/espressif32/esp32-gateway.html
PLATFORM: Espressif 32 (6.0.1) > OLIMEX ESP32-GATEWAY
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog,
iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h,
olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
Environment Status Duration
On Wed, Aug 2, 2023 at 6:53 PM Jeremy Poulter @.***> wrote:
Which board/env are you building? Are they actually compilation errors from Platform IO, or just VSCode trying to parse the code? The latter may just be a VS Code miss configuration of VS Code and not impact building/uploading/etc
— Reply to this email directly, view it on GitHub https://github.com/OpenEVSE/ESP32_WiFi_V4.x/issues/708#issuecomment-1663071065, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5YNGRK5L7ZZJWIU2ZEXZTXTLK5RANCNFSM6AAAAAA3BRLBRU . You are receiving this because you authored the thread.Message ID: @.***>
jeremypoulter
commented
11 months ago Looks like you are using Windows, so could be an issue with that. Will take a look. You could also try installing Ubuntu via WSL and building via that?
matth-x
commented
11 months ago I had the same issue but assumed that it was due to my local PIO installation (also Windows). As a workaround, I added the following line into platformio.ini (e.g. line 50).
-D LittleFS=LITTLEFSIIRC LITTLEFS was the older version of LittleFS that was supplied as an external library. LittleFS is now included as part of the main ESP32 core and should use LittleFS
aaronwesel
commented
11 months ago Thank you! This was very helpful and resoled this issue. Thank you Jeremy and Matthew.
jeremypoulter
commented
11 months ago Let's keep this open till we have a proper solution for building on Windows
aaronwesel
commented
11 months ago I am still having other issues with the code compilation, a different issue. Should we discuss it here, or not?
In file included from C:/Users/techo/.platformio/lib/src/Wire.cpp:32:
C:/Users/techo/.platformio/lib/src/Wire.h:44:5: error: 'i2c_t' does not name a type; did you mean 'ino_t'?
i2c_t i2c;
^~~~~
ino_t
C:/Users/techo/.platformio/lib/src/Wire.h:64:5: error: 'i2c_err_t' does not name a type; did you mean 'esp_err_t'?
i2c_err_t last_error; // @stickBreaker from esp32-hal-i2c.h
^~~~~
esp_err_t
C:/Users/techo/.platformio/lib/src/Wire.h:87:5: error: 'i2c_err_t' does not name a type; did you mean 'esp_err_t'?
i2c_err_t writeTransmission(uint16_t address, uint8_t buff, uint16_t size, bool sendStop=true);
^~~~~
esp_err_t
C:/Users/techo/.platformio/lib/src/Wire.h:88:5: error: 'i2c_err_t' does not name a type; did you mean 'esp_err_t'?
i2c_err_t readTransmission(uint16_t address, uint8_t buff, uint16_t size, bool sendStop=true, uint32_t readCount=NULL);
^~~~~
esp_err_t
Compiling .pio\build\openevse_esp32-gateway-e_dev\FrameworkArduino\MD5Builder.cpp.o
Compiling .pio\build\openevse_esp32-gateway-e_dev\FrameworkArduino\Print.cpp.o
C:/Users/techo/.platformio/lib/src/Wire.cpp: In constructor 'TwoWire::TwoWire(uint8_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:39:6: error: class 'TwoWire' does not have any field named 'i2c'
,i2c(NULL)
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:48:6: error: class 'TwoWire' does not have any field named 'last_error'
,last_error(I2C_ERROR_OK)
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:48:17: error: 'I2C_ERROR_OK' was not declared in this scope
,last_error(I2C_ERROR_OK)
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In destructor 'virtual TwoWire::~TwoWire()':
C:/Users/techo/.platformio/lib/src/Wire.cpp:55:8: error: 'i2c' was not declared in this scope
if(i2c) {
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:56:9: error: 'i2cRelease' was not declared in this scope
i2cRelease(i2c);
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:56:9: note: suggested alternative: 'i2cRead'
i2cRelease(i2c);
^~~~~~
i2cRead
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'bool TwoWire::setPins(int, int)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:63:8: error: 'i2c' was not declared in this scope
if(i2c) {
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'bool TwoWire::begin(int, int, uint32_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:110:5: error: 'i2c' was not declared in this scope
i2c = i2cInit(num, sda, scl, frequency);
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'void TwoWire::setClock(uint32_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:138:21: error: 'i2c' was not declared in this scope
i2cSetFrequency(i2c, frequency);
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:138:5: error: 'i2cSetFrequency' was not declared in this scope
i2cSetFrequency(i2c, frequency);
^~~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:138:5: note: suggested alternative: 'getApbFrequency'
i2cSetFrequency(i2c, frequency);
^~~~~~~
getApbFrequency
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'size_t TwoWire::getClock()':
C:/Users/techo/.platformio/lib/src/Wire.cpp:143:28: error: 'i2c' was not declared in this scope
return i2cGetFrequency(i2c);
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:143:12: error: 'i2cGetFrequency' was not declared in this scope
return i2cGetFrequency(i2c);
^~~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:143:12: note: suggested alternative: 'getApbFrequency'
return i2cGetFrequency(i2c);
^~~~~~~
getApbFrequency
C:/Users/techo/.platformio/lib/src/Wire.cpp: At global scope:
C:/Users/techo/.platformio/lib/src/Wire.cpp:148:1: error: 'i2c_err_t' does not name a type; did you mean 'esp_err_t'?
i2c_err_t TwoWire::writeTransmission(uint16_t address, uint8_t buff, uint16_t size, bool sendStop)
^~~~~
esp_err_t
C:/Users/techo/.platformio/lib/src/Wire.cpp:154:1: error: 'i2c_err_t' does not name a type; did you mean 'esp_err_t'?
i2c_err_t TwoWire::readTransmission(uint16_t address, uint8_t buff, uint16_t size, bool sendStop, uint32_t *readCount)
^~~~~
esp_err_t
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'void TwoWire::beginTransmission(uint16_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:166:5: error: 'last_error' was not declared in this scope
last_error = I2C_ERROR_OK;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:166:5: note: suggested alternative: 'lastError'
last_error = I2C_ERROR_OK;
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:166:18: error: 'I2C_ERROR_OK' was not declared in this scope
last_error = I2C_ERROR_OK;
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'uint8_t TwoWire::endTransmission(bool)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:175:9: error: 'last_error' was not declared in this scope
last_error = writeTransmission(txAddress, &txBuffer[txQueued], txLength - txQueued, sendStop);
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:175:9: note: suggested alternative: 'lastError'
last_error = writeTransmission(txAddress, &txBuffer[txQueued], txLength - txQueued, sendStop);
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:175:22: error: 'writeTransmission' was not declared in this scope
last_error = writeTransmission(txAddress, &txBuffer[txQueued], txLength - txQueued, sendStop);
^~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:175:22: note: suggested alternative: 'beginTransmission'
last_error = writeTransmission(txAddress, &txBuffer[txQueued], txLength - txQueued, sendStop);
^~~~~
beginTransmission
C:/Users/techo/.platformio/lib/src/Wire.cpp:176:26: error: 'I2C_ERROR_CONTINUE' was not declared in this scope
if(last_error == I2C_ERROR_CONTINUE){
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:178:34: error: 'I2C_ERROR_OK' was not declared in this scope
} else if( last_error == I2C_ERROR_OK){
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:185:9: error: 'last_error' was not declared in this scope
last_error = I2C_ERROR_NO_BEGIN;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:185:9: note: suggested alternative: 'lastError'
last_error = I2C_ERROR_NO_BEGIN;
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:185:22: error: 'I2C_ERROR_NO_BEGIN' was not declared in this scope
last_error = I2C_ERROR_NO_BEGIN;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:185:22: note: suggested alternative: 'ESP_ERR_NO_MEM'
last_error = I2C_ERROR_NO_BEGIN;
^~~~~~
ESP_ERR_NO_MEM
C:/Users/techo/.platformio/lib/src/Wire.cpp:191:13: error: 'last_error' was not declared in this scope
return (last_error == I2C_ERROR_CONTINUE)?I2C_ERROR_OK:last_error; // Don't return Continue for compatibility.
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:191:13: note: suggested alternative: 'lastError'
return (last_error == I2C_ERROR_CONTINUE)?I2C_ERROR_OK:last_error; // Don't return Continue for compatibility.
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:191:27: error: 'I2C_ERROR_CONTINUE' was not declared in this scope
return (last_error == I2C_ERROR_CONTINUE)?I2C_ERROR_OK:last_error; // Don't return Continue for compatibility.
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:191:47: error: 'I2C_ERROR_OK' was not declared in this scope
return (last_error == I2C_ERROR_CONTINUE)?I2C_ERROR_OK:last_error; // Don't return Continue for compatibility.
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'uint8_t TwoWire::requestFrom(uint16_t, uint8_t, bool)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:205:9: error: 'last_error' was not declared in this scope
last_error = I2C_ERROR_MEMORY;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:205:9: note: suggested alternative: 'lastError'
last_error = I2C_ERROR_MEMORY;
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:205:22: error: 'I2C_ERROR_MEMORY' was not declared in this scope
last_error = I2C_ERROR_MEMORY;
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:210:5: error: 'last_error' was not declared in this scope
last_error = readTransmission(address, &rxBuffer[cnt], size, sendStop, &cnt);
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:210:5: note: suggested alternative: 'lastError'
last_error = readTransmission(address, &rxBuffer[cnt], size, sendStop, &cnt);
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:210:18: error: 'readTransmission' was not declared in this scope
last_error = readTransmission(address, &rxBuffer[cnt], size, sendStop, &cnt);
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:210:18: note: suggested alternative: 'endTransmission'
last_error = readTransmission(address, &rxBuffer[cnt], size, sendStop, &cnt);
^~~~
endTransmission
C:/Users/techo/.platformio/lib/src/Wire.cpp:215:23: error: 'I2C_ERROR_CONTINUE' was not declared in this scope
if( last_error != I2C_ERROR_CONTINUE){ // not a buffered ReSTART operation
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:221:22: error: 'I2C_ERROR_OK' was not declared in this scope
if(last_error != I2C_ERROR_OK){ // ReSTART on read does not return any data
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'virtual size_t TwoWire::write(uint8_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:232:13: error: 'last_error' was not declared in this scope
last_error = I2C_ERROR_MEMORY;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:232:13: note: suggested alternative: 'lastError'
last_error = I2C_ERROR_MEMORY;
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:232:26: error: 'I2C_ERROR_MEMORY' was not declared in this scope
last_error = I2C_ERROR_MEMORY;
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:240:5: error: 'last_error' was not declared in this scope
last_error = I2C_ERROR_NO_BEGIN; // no begin, not transmitting
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:240:5: note: suggested alternative: 'lastError'
last_error = I2C_ERROR_NO_BEGIN; // no begin, not transmitting
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp:240:18: error: 'I2C_ERROR_NO_BEGIN' was not declared in this scope
last_error = I2C_ERROR_NO_BEGIN; // no begin, not transmitting
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:240:18: note: suggested alternative: 'ESP_ERR_NO_MEM'
last_error = I2C_ERROR_NO_BEGIN; // no begin, not transmitting
^~~~~~
ESP_ERR_NO_MEM
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'virtual void TwoWire::flush()':
C:/Users/techo/.platformio/lib/src/Wire.cpp:288:14: error: 'i2c' was not declared in this scope
i2cFlush(i2c); // cleanup
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:288:5: error: 'i2cFlush' was not declared in this scope
i2cFlush(i2c); // cleanup
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:288:5: note: suggested alternative: 'flush'
i2cFlush(i2c); // cleanup
^~~~
flush
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'uint8_t TwoWire::lastError()':
C:/Users/techo/.platformio/lib/src/Wire.cpp:340:21: error: 'last_error' was not declared in this scope
return (uint8_t)last_error;
^~~~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:340:21: note: suggested alternative: 'lastError'
return (uint8_t)last_error;
^~~~~~
lastError
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'uint32_t TwoWire::setDebugFlags(uint32_t, uint32_t)':
C:/Users/techo/.platformio/lib/src/Wire.cpp:380:19: error: 'i2c' was not declared in this scope
return i2cDebug(i2c,setBits,resetBits);
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:380:10: error: 'i2cDebug' was not declared in this scope
return i2cDebug(i2c,setBits,resetBits);
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:380:10: note: suggested alternative: 'i2cRead'
return i2cDebug(i2c,setBits,resetBits);
^~~~
i2cRead
C:/Users/techo/.platformio/lib/src/Wire.cpp: In member function 'bool TwoWire::busy()':
C:/Users/techo/.platformio/lib/src/Wire.cpp:384:25: error: 'i2c' was not declared in this scope
return ((i2cGetStatus(i2c) & 16 )==16);
^~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:384:12: error: 'i2cGetStatus' was not declared in this scope
return ((i2cGetStatus(i2c) & 16 )==16);
^~~~
C:/Users/techo/.platformio/lib/src/Wire.cpp:384:12: note: suggested alternative: 'i2cGetClock'
return ((i2cGetStatus(i2c) & 16 )==16);
^~~~
i2cGetClock
*** [.pio\build\openevse_esp32-gateway-e_dev\lib359\src\Wire.cpp.o] Error 1
====================================================================================== [FAILED] Took 149.54 seconds ======================================================================================
Environment Status Duration
openevse_esp32-gateway-e_dev FAILED 00:02:29.545 ================================================================================= 1 failed, 0 succeeded in 00:02:29.545 =================================================================================
jeremypoulter
commented
11 months ago That file is auto generated by a python script, is using windows \ and breaking the build
matth-x
commented
11 months ago Update: #682 resolves the LITTLEFS issue.
matth-x
commented
9 months ago A further outstanding issue on Windows is the upload command in the platformio.ini (env:openevse_wifi_v1):
upload_command = curl -F firmware=@$SOURCE http://$UPLOAD_PORT/update --progress-bar | catThis only works on Linux. Since I prefer working with the Serial flasher anyway, I don't have a fix at hand.
jeremypoulter
commented
9 months ago A further outstanding issue on Windows is the upload command in the platformio.ini (env:openevse_wifi_v1):
upload_command = curl -F firmware=@$SOURCE http://$UPLOAD_PORT/update --progress-bar | catThis only works on Linux. Since I prefer working with the Serial flasher anyway, I don't have a fix at hand.
I would just use a different board for dev work, the OpenEVSE board is not great for dev work as it only has the one serial port exposed
matth-x
commented
9 months ago Good tip, the extra debug port would be very handy and I will change my dev setup then.
Apart from that line in the platformio.ini I did not face any further issues on Windows.
zerodur12
commented
7 months ago I have also some issue when compiling on window. My objective was to test a modification on the latest OpenEVSE WiFi firmware v5.0.2 to test some modification on the current_shaper.cpp to try to solve the shapper issue #762 by supressing line https://github.com/OpenEVSE/openevse_esp32_firmware/blob/e8219948309112c3fb3d73927b05120c058bfc60/src/current_shaper.cpp#L177C1-L179C3 re-compile and test.
But before changing any thing my first test was to verify that I was able to recompile the firmware
for that I'm working with Visual Studio Code under windows, I download https://github.com/OpenEVSE/openevse_esp32_firmware/releases/download/v5.0.2/openevse_wifi_v1.bin open the project and compile it with out any modification. It compile with success with some warning about GUI v2 file missing:
Verbose mode can be enabled via -v, --verbose option
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Firmware Revision: -D BUILD_TAG=local___modified -D BUILD_HASH=_modified
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html
PLATFORM: Espressif 32 (6.0.1) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
Environment Status Duration
openevse_wifi_v1 SUCCESS 00:00:22.034 ====================================================================== 1 succeeded in 00:00:22.034 ======================================================================
and I test the generated firmware.bin file by install it on my EmonEVSE WiFi Connected EV Charging Station (Type-2). After the OTA Download of the firmware everething seems to be ok and the interface was nominal. But if I switch off and then switch on the EmonEVSE the EmonEVSE stop at the 'initialisation phase' on the display and don't go further
downloading back v5.0.2 openevse_wifi_v1.bin file make the EmonEVSE work again
aaronwesel
commented
7 months ago For this you can just follow the instructions in the main readme file on how download and update the GUI. Other than this, are you have any other issues?
AW ᐧ
On Sun, Dec 3, 2023 at 7:21 AM zerodur12 @.***> wrote:
I have also some issue when compiling on window. My objective was to test a modification on the latest OpenEVSE WiFi firmware v5.0.2 https://github.com/OpenEVSE/openevse_esp32_firmware/releases/tag/v5.0.2 to test some modification on the current_shaper.cpp https://github.com/OpenEVSE/openevse_esp32_firmware/blob/master/src/current_shaper.cpp to try to solve the shapper issue #762 https://github.com/OpenEVSE/openevse_esp32_firmware/issues/762 by supressing line https://github.com/OpenEVSE/openevse_esp32_firmware/blob/e8219948309112c3fb3d73927b05120c058bfc60/src/current_shaper.cpp#L177C1-L179C3 re-compile and test.
But before changing any thing my first test was to verify that I was able to recompile the firmware
for that I'm working with Visual Studio Code under windows, I download https://github.com/OpenEVSE/openevse_esp32_firmware/releases/download/v5.0.2/openevse_wifi_v1.bin open the project and compile it with out any modification. It compile with success with some warning about GUI v2 file missing: Processing openevse_wifi_v1 (board: esp32dev; platform: @.***; framework: arduino)
Verbose mode can be enabled via -v, --verbose option fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Firmware Revision: -D BUILD_TAG=local___modified -D BUILD_HASH=_modified fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html PLATFORM: Espressif 32 (6.0.1) > Espressif ESP32 Dev Module HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa) PACKAGES:
- framework-arduinoespressif32 @ 3.20006.221224 (2.0.6)
- tool-esptoolpy @ 1.40400.0 (4.4.0)
toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5 LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf LDF Modes: Finder ~ chain, Compatibility ~ soft Found 48 compatible libraries Scanning dependencies... Dependency Graph |-- ArduinoJson @ 6.20.1 |-- ArduinoMongoose @ 0.0.18 |-- Micro Debug @ 0.0.5 |-- ConfigJson @ 0.0.5 |-- OpenEVSE @ 0.0.14 |-- ESPAL @ 0.0.3 |-- StreamSpy @ 0.0.1 |-- MicroTasks @ 0.0.3 |-- ArduinoOcpp @ 0.3.0 |-- ArduinoOcppMongoose @ 0.1.0 |-- Adafruit NeoPixel @ 1.11.0 |-- Adafruit MCP9808 Library @ 1.1.2 |-- EEPROM @ 2.0.0 |-- LittleFS @ 2.0.0 |-- Update @ 2.0.0 |-- ArduinoOTA @ 2.0.0 |-- WiFi @ 2.0.0 |-- DNSServer @ 2.0.0 |-- ESPmDNS @ 2.0.0 |-- Ethernet @ 2.0.0 |-- FS @ 2.0.0 |-- Wire @ 2.0.0 Building in release mode 10.2.4 Warning: GUI files not found, run 'git submodule update --init' (C:\Users\zerod\OneDrive\Documents\openEvse\openevse_esp32_firmware-5.0.2\openevse_esp32_firmware-5.0.2\gui-v2)
@.***;C:\Users\zerod.platformio\penv\Scripts;C:\Users\zerod.platformio\penv;C:\Users\zerod.platformio\python3;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Program Files\MATLAB\R2023b\bin;C:\Program Files\nodejs;C:\Program Files\Git\cmd;C:\Users\zerod\AppData\Local\Microsoft\WindowsApps;C:\Users\zerod\AppData\Local\Programs\Python\Python38-32\Scripts;C:\Users\zerod\AppData\Local\Programs\Python\Python38-32;C:\Program Files (x86)\Intel\Trace Analyzer and Collector\9.0.3.050\dll;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Users\zerod\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\zerod\AppData\Roaming\npm;C:\Users\zerod\AppData\Local\GitHubDesktop\bin Retrieving maximum program size .pio\build\openevse_wifi_v1\firmware.elf Checking size .pio\build\openevse_wifi_v1\firmware.elf Advanced Memory Usage is available via "PlatformIO Home > Project Inspect" RAM: [== ] 18.8% (used 61544 bytes from 327680 bytes) Flash: [========= ] 93.9% (used 1846321 bytes from 1966080 bytes)
[SUCCESS] Took 22.03 seconds
Environment Status Duration
openevse_wifi_v1 SUCCESS 00:00:22.034 ====================================================================== 1 succeeded in 00:00:22.034
and I test the generated firmware.bin file by install it on my EmonEVSE WiFi Connected EV Charging Station (Type-2). After the OTA Download of the firmware everething seems to be ok and the interface was nominal. But if I switch off and then switch on the EmonEVSE the EmonEVSE stop at the 'initialisation phase' on the display and don't go further
downloading back v5.0.2 openevse_wifi_v1.bin file make the EmonEVSE work again
— Reply to this email directly, view it on GitHub https://github.com/OpenEVSE/openevse_esp32_firmware/issues/708#issuecomment-1837464492, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5YNGXP2EW3KNKLMHQU7P3YHRVELAVCNFSM6AAAAAA3BRLBRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGQ3DINBZGI . You are receiving this because you modified the open/close state.Message ID: @.***>
alfredoanton82
commented
7 months ago Hi,
I've spend half afternoon trying to figure this LittleFS error with v2_gui tag until I saw it was an actual issue... XD, Thanks for the fix on the littleFS @matth-x!!
Found the development guide while investigating, (@zerodur12 link) it compiles nicely after installing node.js and build the GUI first... and uploads, directly from platformIO through OTA to an ESP32.
Although it is working as I can see the LCD and the RGB led, and I can connect via web to the openevse, the GUI is simply not shown, no error either... just nothing in the screen.
Any hint? Something I'm missing? Thanks in advance!
Thanks! Alfredo
zerodur12
commented
7 months ago @alfredoanton82 Hi I have also follow the development guide but there still some warning during compilation and if I upload the compiled firmware and like you "I can connect via web to the openevse, the GUI is simply not shown, no error either... just nothing in the screen."
Am I the only one having this issue? Wihtout any modification, if I download the Wifi files from github and try to compile it using pio I get an error "Littlefs" not found. What am I doing wrong?