dingo35 / SmartEVSE-3.5

Smart Electric Vehicle Charging Station (EVSE)
MIT License
44 stars 20 forks source link

Smart EVSE is not booting #19

Closed 2pjnl closed 7 months ago

2pjnl commented 7 months ago

From the start I have had problems with stability and the Smart EVSE crashes regularly. After flashing Release v3.5.0-RC1, this seemed to go better. On my workbench it worked for a few hours without crashing. I then mounted it back in the enclosure and charging went well for a few hours until it crashed again. After a power cycle it would not start again, the screen only flashed once.

After disassembling and connecting via USB-C it would boot, but it crashed again after 9-10 seconds. Now it no longer boots via USB-C. I initially think of a software problem. Is it possible to flash it via USB-C?

dingo35 commented 7 months ago

https://github.com/dingo35/SmartEVSE-3.5/blob/master/docs/configuration.md

Last paragraph, "building the firmware" tells you how to upload via USB-C

2pjnl commented 7 months ago

Installation was fairly easy, but Git was not in the PATH. After this was fixed, compiling went without any problems, but uploading does not work. I have changed the port to COM3 in platformio.ini, but I get the message below:

Building in release mode Retrieving maximum program size .pio\build\release\firmware.elf Checking size .pio\build\release\firmware.elf Advanced Memory Usage is available via "PlatformIO Home > Project Inspect" RAM: [== ] 16.0% (used 52584 bytes from 327680 bytes) Flash: [======= ] 67.0% (used 1185621 bytes from 1769472 bytes) Configuring upload protocol... AVAILABLE: cmsis-dap, esp-bridge, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa CURRENT: upload_protocol = esptool Looking for upload port... Using manually specified: COM3 Uploading .pio\build\release\firmware.bin esptool.py v4.5.1 Serial port COM3 Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received. For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html *** [upload] Error 2 ============================================= [FAILED] Took 17.98 seconds =============================================

dingo35 commented 7 months ago

If you're sure that COM3 is the right port, and you have a good USB cable, and it is plugged in correctly.... then I don't know what the problem is.....

"2pjnl" @.***> schreef op 26 februari 2024 om 15:57:

Installation was fairly easy, but Git was not in the PATH. After this was fixed, compiling went without any problems, but uploading does not work. I have changed the port to COM3 in platformio.ini, but I get the message below:

`Building in release mode

Retrieving maximum program size .pio\build\release\firmware.elf

Checking size .pio\build\release\firmware.elf

Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"

RAM: [== ] 16.0% (used 52584 bytes from 327680 bytes)

Flash: [======= ] 67.0% (used 1185621 bytes from 1769472 bytes)

Configuring upload protocol...

AVAILABLE: cmsis-dap, esp-bridge, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa

CURRENT: upload_protocol = esptool

Looking for upload port...

Using manually specified: COM3

Uploading .pio\build\release\firmware.bin

esptool.py v4.5.1

Serial port COM3

Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received.

For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

*** [upload] Error 2

============================================= [FAILED] Took 17.98 seconds =============================================

`

Reply to this email directly, view it on GitHub https://github.com/dingo35/SmartEVSE-3.5/issues/19#issuecomment-1965252341 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOSIX5K3NC43WJUH6QSSNDYVTZKJAVCNFSM6AAAAABD23HGXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGI2TEMZUGE .

You are receiving this because you modified the open/close state.