Guidance around recovering from mDot FOTA Failures.

[Ajay K]

I am wondering how do you recover from FOTA failures such as the one called out below. Once the mDot seems to get these series of errors when processing the inbound FOTA packets, the mDot never recovers from these even after a reset of the mDot and always thinks FOTA is still in progress and doesn’t break out from Class C Mode back to the original Mode it was in i.e. Class A Mode. The only thing that seems to potentially help is a Conduit reboot in most cases and then a mDot reset. This process would be impossible to manage in the field.

We are using mDot libMdot Library: 4.0.0 and the conduit firmware version is 5.2.5.

The main error I see is this:

[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000002
[INFO] Received packet was not valid: invalid MIC, or corrupted Data

Here is brief version of the firmware processing FOTA Packets.

[INFO] Multicast group setup; id: 0 addr: f0da3dcd
[ERROR] RX data rate 0 invalid
[INFO] Multicast class C session; time to start 24, time to end 4125, dr 12, freq 923300000
[INFO] Multicast session 0 starting in 24 seconds
[INFO] Sending Multicast Response
[INFO] Preparing frame
[INFO] Adjust PowerMax to 21
[INFO] Configure radio for TX
[DEBUG] mDotEvent – TxStart
[DEBUG] mDotEvent – TxDone
[INFO] Rx Window 1
[INFO] RxDone 24 bytes RSSI: -27 dB SNR: 65 cB
[INFO] Packet for 017a6257
[INFO] Packet Received : Port: 201 FCnt: 00000007 Size: 11 ACK: 0 DUP: 0
[DEBUG] mDotEvent – PacketRx ADDR: 017a6257
[DEBUG] Rx 11 bytes
[DEBUG] Received Fragment setup packet on Port: 201 is [02 01 64 00 83 00 2c 04 fa ce bd]
[INFO] Fragmentation Padding Bytes Length: 44 bytes, Is Device Central Firmware: Yes!

[INFO] Packet RSSI: -27 dB SNR: 65 cB
[DEBUG] mDotEvent – RxDone
[ERROR] SPIFFS_remove failed -10002
[INFO] NumberOfFragments: 100
[INFO] FragmentSize: 131
[INFO] Padding: 44
[INFO] Sending Fragmentation Response
[INFO] Preparing frame
[INFO] Adjust PowerMax to 21
[INFO] Configure radio for TX
[DEBUG] mDotEvent – TxStart
[DEBUG] mDotEvent – TxDone
[INFO] Rx Window 1
[DEBUG] mDotEvent – RxTimeout on Slot 1
[INFO] Rx Window 2
[DEBUG] mDotEvent – RxTimeout on Slot 2
[WARNING] Link: ResetState
[DEBUG] mDotEvent – BeaconLost
[INFO] Switched to class C for up to 4101 seconds (dr: 12 freq: 923300000)
[INFO] RxDone 147 bytes RSSI: -119 dB SNR: -140 cB
[INFO] Packet for Multicast f0da3dcd
[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000002
[INFO] Received packet was not valid: invalid MIC, or corrupted Data
[INFO] Packet RSSI: -119 dB SNR: -140 cB
[DEBUG] mDotEvent – RxDone
[INFO] RxDone 147 bytes RSSI: -119 dB SNR: -145 cB
[INFO] Packet for Multicast f0da3dcd
[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000003
[INFO] Received packet was not valid: invalid MIC, or corrupted Data
[INFO] Packet RSSI: -119 dB SNR: -145 cB
[DEBUG] mDotEvent – RxDone
[INFO] RxDone 147 bytes RSSI: -112 dB SNR: -127 cB
[INFO] Packet for Multicast f0da3dcd
[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000004
[INFO] Received packet was not valid: invalid MIC, or corrupted Data
[INFO] Packet RSSI: -112 dB SNR: -127 cB
[DEBUG] mDotEvent – RxDone
[INFO] RxDone 147 bytes RSSI: -119 dB SNR: -145 cB
[INFO] Packet for Multicast f0da3dcd
[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000005
[INFO] Received packet was not valid: invalid MIC, or corrupted Data
[INFO] Packet RSSI: -119 dB SNR: -145 cB
[DEBUG] mDotEvent – RxDone
[INFO] RxDone 147 bytes RSSI: -118 dB SNR: -142 cB
[INFO] Packet for Multicast f0da3dcd
[WARNING] Invalid MIC Addr: f0da3dcd FCnt: 00000007
[INFO] Received packet was not valid: invalid MIC, or corrupted Data

Thanks,
Ajay

[Author]

Posts