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.

Sign up for GitHub

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

Jump to bottom

LMIC can get stuck with OP_TXRXPENDING if FSK is allowed for region #434

Closed
terrillmoore opened this issue Sep 9, 2019 · 0 comments
Closed

LMIC can get stuck with OP_TXRXPENDING if FSK is allowed for region #434

terrillmoore opened this issue Sep 9, 2019 · 0 comments
Assignees
@terrillmoore
Labels
bug
Projects
Pass pre-compliance tests

Comments

@terrillmoore
Copy link
Member

v3.0.99 compliance gets stuck during the EU RX Timing Setup Request (test 13.1).

Although it looked like a missing interrupt, a long and painful investigation revealed that the function LMICbandplan_isFSK() was returning TRUE based on LMIC.rxsyms rather than LMIC.dndr. Sometimes LMIC.rxsyms was accidentally the wrong value, and we took the FSK path. The FSK path has a bug that causes it not to schedule the RX properly -- but even if it were bug free, that's the wrong path.
@terrillmoore terrillmoore self-assigned this Sep 9, 2019
@terrillmoore terrillmoore added this to To do in Pass pre-compliance tests via automation Sep 9, 2019
Pass pre-compliance tests automation moved this from To do to Done Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@terrillmoore terrillmoore

Labels
bug
Projects
Pass pre-compliance tests
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terrillmoore