[GH-ISSUE #1002] Fatal exception 28(LoadProhibitedCause) Multiple Parameters #855

Open
opened 2026-02-28 01:27:21 +03:00 by kerem · 16 comments
Owner

Originally created by @rodri16 on GitHub (Jan 31, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1002

Hardware

WiFimanager Branch/Release:

  • OTA

Esp8266/Esp32:

  • ESP8266

ESP Core Version: 2.4.0, staging

  • 2.4.0

Hi, I have a problem (OTA Branch on esp8266ex), using multiple parameters. My parameters are

char mqtt_server[40] = "monitor.com"; 
char mqtt_port[6] = "80";
char TimeZone[5] = "-3.0";
char NumDisp[5] = "17";
char mult_V[12] = "448128.6";
char mult_I[12] = "16591.2";
char mult_P[13] = "12136999.39";

After full erase flash, everything is ok, but when booting again and finding the file config.jsn it crashes after the 5th parameter. Do you know why?

After full erase

*WM: [3] allocating params bytes: 20
*WM: [2] Added Parameter: server
*WM: [2] Added Parameter: port
*WM: [2] Added Parameter: TimeZone
*WM: [2] Added Parameter: NumDisp
*WM: [2] Added Parameter: mult_V
*WM: [3] Updated _max_params: 10
*WM: [3] re-allocating params bytes: 40
*WM: [2] Added Parameter: mult_I
*WM: [2] Added Parameter: mult_P
*WM: [2] Starting Config Portal 

On reboot:

SDK:2.2.2-dev(38a443e)/Core:2.6.3=20603000/lwIP:STABLE-2_1_2_RELEASE/glue:1.2-16-ge23a07e/BearSSL:89454af
mounting FS...
reading config file
{"mqtt_server":"monitor.com","mqtt_port":"80","TimeZone":"-3.0","mult_V":"448128.6","mult_I":"16591.2","mult_P":"12136999.39","NumDisp":"16","ip":"192.168.1.231","gateway":"192.168.1.254","subnet":"255.255.255.0"}
parsed json
Fatal exception 28(LoadProhibitedCause):

changed to 10 MAX_PARAMS but nothing changed,

#define WIFI_MANAGER_MAX_PARAMS 10

If I use less parameters everything is OK

Originally created by @rodri16 on GitHub (Jan 31, 2020). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1002 #### Hardware **WiFimanager Branch/Release:** - OTA **Esp8266/Esp32:** - ESP8266 **ESP Core Version: 2.4.0, staging** - 2.4.0 Hi, I have a problem (OTA Branch on esp8266ex), using multiple parameters. My parameters are ``` char mqtt_server[40] = "monitor.com"; char mqtt_port[6] = "80"; char TimeZone[5] = "-3.0"; char NumDisp[5] = "17"; char mult_V[12] = "448128.6"; char mult_I[12] = "16591.2"; char mult_P[13] = "12136999.39"; ``` After full erase flash, everything is ok, but when booting again and finding the file config.jsn it crashes after the 5th parameter. Do you know why? After full erase ``` *WM: [3] allocating params bytes: 20 *WM: [2] Added Parameter: server *WM: [2] Added Parameter: port *WM: [2] Added Parameter: TimeZone *WM: [2] Added Parameter: NumDisp *WM: [2] Added Parameter: mult_V *WM: [3] Updated _max_params: 10 *WM: [3] re-allocating params bytes: 40 *WM: [2] Added Parameter: mult_I *WM: [2] Added Parameter: mult_P *WM: [2] Starting Config Portal ``` On reboot: ``` SDK:2.2.2-dev(38a443e)/Core:2.6.3=20603000/lwIP:STABLE-2_1_2_RELEASE/glue:1.2-16-ge23a07e/BearSSL:89454af mounting FS... reading config file {"mqtt_server":"monitor.com","mqtt_port":"80","TimeZone":"-3.0","mult_V":"448128.6","mult_I":"16591.2","mult_P":"12136999.39","NumDisp":"16","ip":"192.168.1.231","gateway":"192.168.1.254","subnet":"255.255.255.0"} parsed json Fatal exception 28(LoadProhibitedCause): ``` changed to 10 MAX_PARAMS but nothing changed, ``` #define WIFI_MANAGER_MAX_PARAMS 10``` If I use less parameters everything is OK
Author
Owner

@tablatronix commented on GitHub (Feb 1, 2020):

Usually running out of memory, we are working on it, see the other issues some hints were to allocate memory for http page variable output to prevent fragmentation

<!-- gh-comment-id:581057968 --> @tablatronix commented on GitHub (Feb 1, 2020): Usually running out of memory, we are working on it, see the other issues some hints were to allocate memory for http page variable output to prevent fragmentation
Author
Owner

@rodri16 commented on GitHub (Feb 4, 2020):

Maybe increasing DynamicJsonDocument json(1024);??
Still couldn't make it work

<!-- gh-comment-id:581905608 --> @rodri16 commented on GitHub (Feb 4, 2020): Maybe increasing DynamicJsonDocument json(1024);?? Still couldn't make it work
Author
Owner

@tablatronix commented on GitHub (Feb 4, 2020):

No its memory in wm theres a issue about it

<!-- gh-comment-id:581906516 --> @tablatronix commented on GitHub (Feb 4, 2020): No its memory in wm theres a issue about it
Author
Owner

@rodri16 commented on GitHub (Feb 4, 2020):

So removing PROGMEM could be a solution according to https://github.com/tzapu/WiFiManager/issues/931

<!-- gh-comment-id:581947409 --> @rodri16 commented on GitHub (Feb 4, 2020): So removing PROGMEM could be a solution according to [https://github.com/tzapu/WiFiManager/issues/931](url)
Author
Owner

@tablatronix commented on GitHub (Feb 4, 2020):

Actually I was thinking of another issue , I forgot about that one. Are you using progmem strings in your params?

<!-- gh-comment-id:581949064 --> @tablatronix commented on GitHub (Feb 4, 2020): Actually I was thinking of another issue , I forgot about that one. Are you using progmem strings in your params?
Author
Owner

@rodri16 commented on GitHub (Feb 4, 2020):

Actually not in params but in strings_en.h

<!-- gh-comment-id:581952182 --> @rodri16 commented on GitHub (Feb 4, 2020): Actually not in params but in strings_en.h
Author
Owner

@tablatronix commented on GitHub (Feb 4, 2020):

No those should be fine, we are talking about stack memory

<!-- gh-comment-id:582040867 --> @tablatronix commented on GitHub (Feb 4, 2020): No those should be fine, we are talking about stack memory
Author
Owner

@rodri16 commented on GitHub (Feb 10, 2020):

https://github.com/tzapu/WiFiManager/issues/901?? I still don't get what to change to support multiple params

<!-- gh-comment-id:584121202 --> @rodri16 commented on GitHub (Feb 10, 2020): [https://github.com/tzapu/WiFiManager/issues/901](url)?? I still don't get what to change to support multiple params
Author
Owner

@rodri16 commented on GitHub (Feb 17, 2020):

I have another weird problem, in config portal after connecting WiFi "Credential saved. Trying.." page doesn't appear, is it because of lack of memory?
Also when calling captive portal sometimes I have to reload captive portal page many times till I see the WM menu

<!-- gh-comment-id:586982814 --> @rodri16 commented on GitHub (Feb 17, 2020): I have another weird problem, in config portal after connecting WiFi "Credential saved. Trying.." page doesn't appear, is it because of lack of memory? Also when calling captive portal sometimes I have to reload captive portal page many times till I see the WM menu
Author
Owner

@tablatronix commented on GitHub (Feb 17, 2020):

I was having this issue also, let me se if that is a new bug i introduced

<!-- gh-comment-id:586992488 --> @tablatronix commented on GitHub (Feb 17, 2020): I was having this issue also, let me se if that is a new bug i introduced
Author
Owner

@rodri16 commented on GitHub (Feb 18, 2020):

Solved after clicking save. Thanks @marcovanoord!
But still cannot always connect directly to configportal... HTTP root not always appearing

*WM: [3] setupConfigPortal 
*WM: [1] Starting Web Portal 
*WM: [3] dns server started with ip:  10.0.1.1
*WM: [2] HTTP server started 
*WM: [2] WiFi Scan completed in 1583 ms
*WM: [2] Config Portal Running, blocking, waiting for clients... 
*WM: [2] Portal Timeout In 116 seconds
*WM: [3] -> connectivitycheck.gstatic.com 
*WM: [2] <- Request redirected to captive portal 
*WM: [2] Portal Timeout In 86 seconds

So i have to go back and launch again config portal and then portal opens (sometimes) successfully

*WM: [2] <- Request redirected to captive portal 
*WM: [3] -> connectivitycheck.gstatic.com 
*WM: [2] <- Request redirected to captive portal 
*WM: [2] <- HTTP Root 
*WM: [3] -> 10.0.1.1 
*WM: [3] lastconxresult: WL_CONNECTED
*WM: [2] WiFi Scan completed in 1585 ms
*WM: [3] -> 10.0.1.1 
*WM: [3] -> connectivitycheck.gstatic.com 
<!-- gh-comment-id:587445580 --> @rodri16 commented on GitHub (Feb 18, 2020): Solved after clicking save. Thanks @marcovanoord! But still cannot always connect directly to configportal... HTTP root not always appearing ``` *WM: [3] setupConfigPortal *WM: [1] Starting Web Portal *WM: [3] dns server started with ip: 10.0.1.1 *WM: [2] HTTP server started *WM: [2] WiFi Scan completed in 1583 ms *WM: [2] Config Portal Running, blocking, waiting for clients... *WM: [2] Portal Timeout In 116 seconds *WM: [3] -> connectivitycheck.gstatic.com *WM: [2] <- Request redirected to captive portal *WM: [2] Portal Timeout In 86 seconds ``` So i have to go back and launch again config portal and then portal opens (sometimes) successfully ``` *WM: [2] <- Request redirected to captive portal *WM: [3] -> connectivitycheck.gstatic.com *WM: [2] <- Request redirected to captive portal *WM: [2] <- HTTP Root *WM: [3] -> 10.0.1.1 *WM: [3] lastconxresult: WL_CONNECTED *WM: [2] WiFi Scan completed in 1585 ms *WM: [3] -> 10.0.1.1 *WM: [3] -> connectivitycheck.gstatic.com ```
Author
Owner

@tablatronix commented on GitHub (Feb 18, 2020):

what device?

<!-- gh-comment-id:587706101 --> @tablatronix commented on GitHub (Feb 18, 2020): what device?
Author
Owner

@rodri16 commented on GitHub (Feb 19, 2020):

I am using SonOff Pow (r1) Esp8266

<!-- gh-comment-id:588130962 --> @rodri16 commented on GitHub (Feb 19, 2020): I am using SonOff Pow (r1) Esp8266
Author
Owner

@tablatronix commented on GitHub (Feb 19, 2020):

What client device is not pulling up captive portal or web page. Might be a cached issue or a dns issue, try forgetting ap

<!-- gh-comment-id:588211850 --> @tablatronix commented on GitHub (Feb 19, 2020): What client device is not pulling up captive portal or web page. Might be a cached issue or a dns issue, try forgetting ap
Author
Owner

@rodri16 commented on GitHub (Feb 19, 2020):

Oh sorry, it's an Android v10. Ok I'll test

<!-- gh-comment-id:588340048 --> @rodri16 commented on GitHub (Feb 19, 2020): Oh sorry, it's an Android v10. Ok I'll test
Author
Owner

@tablatronix commented on GitHub (Feb 19, 2020):

I just merged dev into ota, it should be up to date now, might be your problem

<!-- gh-comment-id:588386436 --> @tablatronix commented on GitHub (Feb 19, 2020): I just merged dev into ota, it should be up to date now, might be your problem
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#855
No description provided.