1 Answer
- Newest
- Most votes
- Most comments
0
Hi. MIC = Message Integrity Code. It's essentially a checksum performed over the MAC header and MAC payload of your message, and then compared with the MIC In the message. Given that AWS IoT Core LoRaWAN works with lots of devices, it's improbable that it's sending an incorrect MIC. It's more likely that your device has some problem with the MIC calculation.
Have you changed your fragment size? What region are you operating in? It's likely that the FUOTA fragments are the largest payload your device has to deal with, so I would suspect that the MIC failure is related to the large payload size.
Relevant content
- asked 2 years ago
- asked 4 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago
Hi, Operating region - US915, Max frag size = 232, Min frag size = 224. No, I haven't changed the frag size.
I meant what fragment size are you setting in the AWS console when creating the FUOTA task? Can you please add logging in your device firmware to get details about why your device determines there's a MIC failure?
fragment size in aws - 232 bytes fragment interval - 3s redundancy - 5