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

New errror: wifi noTIM!! (IDFGH-804) #3204

Closed
ammaree opened this issue Mar 19, 2019 · 3 comments
Closed

New errror: wifi noTIM!! (IDFGH-804) #3204

ammaree opened this issue Mar 19, 2019 · 3 comments

Comments

@ammaree
Copy link

ammaree commented Mar 19, 2019

Environment

  • Development Kit: [none]
  • Kit version (for WroverKit/PicoKit/DevKitC): [n/a]
  • Module or chip used: [ESP32-WROOM-32]
  • IDF version (run git describe --tags to find it): latest as of today 2019/3/19
  • Build System: [Make|CMake]
  • Compiler version (run xtensa-esp32-elf-gcc --version to find it): v5.2.0
  • Operating System: [Windows]
  • Power Supply: [external 3.3V]

Problem Description

At random times and without and identifiable set of preceding events the error message appears. Have searched the web for the error message but very little available other than an explanation that it normally indicates the absence of Traffic Indication Map info.
https://en.wikipedia.org/wiki/Traffic_indication_map

Expected Behavior

No error message and no loss of communications

Actual Behavior

Get error message and sometimes loss of communications requiring a reboot

Steps to reproduce

Cannot reproduce at all.

Code to reproduce this issue

Debug Logs

Other items if possible

@github-actions github-actions bot changed the title New errror: wifi noTIM!! New errror: wifi noTIM!! (IDFGH-804) Mar 19, 2019
@ammaree
Copy link
Author

ammaree commented Mar 19, 2019

The noTIM!! error message is often followed by another unknown new/error being:
wifi wifi state wrong txa_flags=9

Any chance of shedding some light on these failures?

@liuzfesp
Copy link
Contributor

HI @ammaree , "wifi wifi state wrong txa_flags=9" doesn't indicate a bug, it means ESP32 has sent the AddBA request to AP but AP doesn't reply AddBA response within specified time (1 second). Maybe we should remove the log in future.

I think "sometimes loss of communications requiring a reboot" should have no relationship with the log, it also has no relationship with TIM.

Need more detailed description about the problem before we can investigate it, e.g.:

  • Does "sometimes loss of communications requiring a reboot" mean WiFi disconnect or socket disconnect?
  • log

@ammaree
Copy link
Author

ammaree commented May 3, 2019

I think we can close this issue. The errors have gone away, not sure whether as a result of the AP reconfiguration or the latest Wifi libraries.

@ammaree ammaree closed this as completed May 3, 2019
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

2 participants