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

Fail in softAP mode #569

Open
VaclavVejrosta opened this issue Jan 25, 2021 · 8 comments
Open

Fail in softAP mode #569

VaclavVejrosta opened this issue Jan 25, 2021 · 8 comments

Comments

@VaclavVejrosta
Copy link

Hi,

since I have updated my mos to version 2.19 I can see a quite new bug. It happens during pairing of my "smart device". First of all the device creates an AP and I connect to it with my mobile. Then the device gets the data about the current wifi network and then it tries to connet to wifi. But when disconnecting the softAP mode an error occures and the device is restarted. However, the device is connected to wifi correctly after reboot.

Please see log:
Log.txt

The problem never occured with mos 2.18. By the way, how can I downgrade my mos back to 2.18? I used command mos update version 2.18.0 but it fails.

@DrBomb
Copy link
Collaborator

DrBomb commented Jan 25, 2021

Hi, although I cannot help you with the actual issue. You can add these lines to your mos.yml to pin the build to a specific version. Put 2.18.0 instead of ${mos.version}

@VaclavVejrosta
Copy link
Author

Hi, although I cannot help you with the actual issue. You can add these lines to your mos.yml to pin the build to a specific version. Put 2.18.0 instead of ${mos.version}

Fine, thank you!

@rojer
Copy link
Collaborator

rojer commented Jan 26, 2021

"Stack canary watchpoint triggered" - this suggests stack overflow, and that is a huge stack,indeed.
looks like you're sending logs to websocket, and that log entry is emitted from networking stack itself... i think the problem might be because between 2.18 and 2.19 we redirected IDF logging to the mos logging handler, and now it goes through all the other logging handlers.
try turning off fancy logging, does it still happen?

@VaclavVejrosta
Copy link
Author

I have disabled the ws logs and it helped. The problem disappeared. However I use the ws logs in my products so unfortunately this is not the solution for me.

@rojer
Copy link
Collaborator

rojer commented Jan 28, 2021

i see. i think the task mentioned is the timer task, can you increase CONFIG_FREERTOS_TIMER_TASK_STACK_DEPTH from 4096 to, say. 6144 and see if that helps?

build_vars:
  ESP_IDF_SDKCONFIG_OPTS: >
    ${build_vars.ESP_IDF_SDKCONFIG_OPTS}
    CONFIG_FREERTOS_TIMER_TASK_STACK_DEPTH=6144

@VaclavVejrosta
Copy link
Author

I tried to increase the value up to 16 384 and it didn't help.

@VaclavVejrosta
Copy link
Author

Have you got any other ideas?

@rojer
Copy link
Collaborator

rojer commented Feb 8, 2021

i might, let me think about it some more...

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

No branches or pull requests

3 participants