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

PR #6887 generates execptions in Project Tasmota #7103

Closed
Jason2866 opened this issue Feb 22, 2020 · 3 comments · Fixed by #7096
Closed

PR #6887 generates execptions in Project Tasmota #7103

Jason2866 opened this issue Feb 22, 2020 · 3 comments · Fixed by #7096
Assignees
Milestone

Comments

@Jason2866
Copy link
Contributor

Jason2866 commented Feb 22, 2020

Platform

  • device |ESP01 ]
  • Core Version: [latest git]
  • Development Env: [Platformio]
  • Operating System: [Windows|Linux]

Settings in IDE

  • Module: [|Nodemcu|other]
  • Flash Mode: [DOUT]
  • Flash Size: [1MB]
  • lwip Variant: [v2 Lower Memory|Higher Bandwidth]
  • Reset Method: [|nodemcu]
  • Flash Frequency: [40Mhz]
  • CPU Frequency: [80Mhz]
  • Upload Using: [SERIAL]
  • Upload Speed: [115200] (serial upload only)

Problem Description

Tasmota does generate exceptions when using latest git.

Reverting #6887 does solve the issue.
Without this and using all other PR until to the latest Tasmota does not generate exceptions anymore.

@d-a-v
Copy link
Collaborator

d-a-v commented Feb 23, 2020

Can you give more details ?
When and what exceptions ?
Can you try with #7096 too ?

@Jason2866
Copy link
Contributor Author

@d-a-v exceptions 3 and 9 right after device comes up.

GOOD NEWS. Tried PR #7096 and this seems to solve. Test device now 5 minutes up.
no exception and responsive as it is with core 2.6.1

So the PR #7096 should be merged ASAP

@arendst
Copy link

arendst commented Feb 23, 2020

Verified too that #7096 fixes this issue.

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.

4 participants