Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP gateway issues with factory config over serial #460

Closed
glynhudson opened this issue Oct 27, 2022 · 3 comments · Fixed by #533
Closed

ESP gateway issues with factory config over serial #460

glynhudson opened this issue Oct 27, 2022 · 3 comments · Fixed by #533
Assignees

Comments

@glynhudson
Copy link
Collaborator

The PR which added serial config seems to be causing an issue with ESP gateway #443. I've tested on Rev G using the new rev G environment. V4.1.5 works fine on the ESP gateway using the new rev G environment.

Could there be a serial port conflict?

OpenEVSE WiFI fe2c
Firmware: 4.1.5
Build date: Oct 27 2022 17:21:13
IDF version: v4.4.1-1-gb8050b365e
Free: 265712
[    76][E][vfs_api.cpp:104] open(): /littlefs/schedule.json does not exist, no permits for creation
[    77][E][esp32-hal-adc.c:180] __analogRead(): Pin 1 is not ADC pin!
AP IP Address: 192.168.4.1
E (10434) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10434) task_wdt:  - loopTask (CPU 1)
E (10434) task_wdt: Tasks currently running:
E (10434) task_wdt: CPU 0: IDLE
E (10434) task_wdt: CPU 1: IDLE
E (10434) task_wdt: Aborting.

abort() was called at PC 0x4012f4cc on core 0


Backtrace:0x400836e9:0x3ffbee1c |<-CORRUPTED
@jeremypoulter
Copy link
Collaborator

@glynhudson can you try with the debug enabled? You can see the required changes in the openevse_esp32-gateway-e_dev env

@glynhudson
Copy link
Collaborator Author

ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x1a (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:2
load:0x3fff0030,len:1184
load:0x40078000,len:12784
load:0x40080400,len:3032
entry 0x400805e4

OpenEVSE WiFI fe2c
Firmware: 4.1.5
Build date: Oct 27 2022 18:00:05
IDF version: v4.4.1-1-gb8050b365e
Free: 265764
Got 65535 � from EEPROM @ 0x0c00
No JSON config found
Got 65535 � from EEPROM @ 0x0000
No JSON config found
No JSON config found, trying v1 settings
Loading config
Got '' 255 == 128 @ 575:32
Got '' 255 == 128 @ 0:32
Got '' 255 == 128 @ 32:64
Got '' 255 == 128 @ 542:33
Got '' 255 == 128 @ 128:45
Got '' 255 == 128 @ 173:32
Got '' 255 == 128 @ 438:60
Got '' 255 == 128 @ 732:96
Got '' 255 == 128 @ 205:45
Got '' 255 == 128 @ 250:32
Got '' 255 == 128 @ 282:32
Got '' 255 == 128 @ 314:64
Got '' 255 == 128 @ 378:30
Got '' 255 == 128 @ 408:30
Got 'ffffff'  255 == 127 @ 828:4
Got '' 255 == 128 @ 498:15
Got '' 255 == 128 @ 513:15
Got '' 255 == 128 @ 528:10
Got 'ffffff'  255 == 127 @ 538:4
Got '' 255 == 128 @ 607:45
Got '' 255 == 128 @ 652:80
After config_load_settings: 263656
[   120][E][vfs_api.cpp:104] open(): /littlefs/schedule.json does not exist, no permits for creation
[   124][E][esp32-hal-adc.c:180] __analogRead(): Pin 1 is not ADC pin!
Starting AP
(WIFI_MODE_AP == (WiFi.getMode() & WIFI_MODE_AP)) = 0
(WIFI_MODE_STA == (WiFi.getMode() & WIFI_MODE_STA)) = 0
Got Network event ARDUINO_EVENT_WIFI_READY
Got Network event ARDUINO_EVENT_WIFI_AP_START
Set host name to openevse-fe2c
Got Network event ARDUINO_EVENT_WIFI_AP_STOP
Got Network event ARDUINO_EVENT_WIFI_AP_START
Set host name to openevse-fe2c
AP IP Address: 192.168.4.1
E (10576) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10576) task_wdt:  - loopTask (CPU 1)
E (10576) task_wdt: Tasks currently running:
E (10576) task_wdt: CPU 0: IDLE
E (10576) task_wdt: CPU 1: IDLE
E (10576) task_wdt: Aborting.

abort() was called at PC 0x401a9ee0 on core 0


Backtrace:0x400836e9:0x3ffbee1c |<-CORRUPTED




ELF file SHA256: 0000000000000000

@jeremypoulter
Copy link
Collaborator

@glynhudson Do you have the ethernet connected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants