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

[SX126x][SX128x][LR11x0] Don't report CRC mismatch if valid header received #1203

Merged
merged 4 commits into from
Sep 1, 2024

Conversation

GUVWAF
Copy link
Contributor

@GUVWAF GUVWAF commented Sep 1, 2024

Fixes #1202.

Tested this based on #1190 already using an SX1262 radio. I was able to catch a packet where indeed the HEADER_ERR IRQ was set, but also HEADER_VALID and the payload CRC was OK, and the payload could be decrypted and parsed successfully.

Copy link
Owner

@jgromes jgromes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wow, you're fast :D as discussed in the linked issue, this solution works for me - @StevenCellist I don't think this should have any negative effects on the work you're doing at the LoRaWAN stack, but please confirm.

@StevenCellist
Copy link
Collaborator

Nope, the LoRaWAN stack doesn't touch any Header IRQ, so good to go.

@jgromes jgromes merged commit eda4ec2 into jgromes:master Sep 1, 2024
30 checks passed
@jgromes
Copy link
Owner

jgromes commented Sep 1, 2024

Merged - @GUVWAF thank you for another contribution, it is greatly appreciated!

@GUVWAF
Copy link
Contributor Author

GUVWAF commented Sep 1, 2024

Also thanks to you both for the quick review!

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 this pull request may close these issues.

SX126x reports CRC mismatch upon previously received corrupted header
3 participants