Trust nothing: adding a CRC to BLE payloads
BLE already checks each packet. We still add CRC-16/ARC to every message, and here is why.
Surendra — Tejvon
Senior Android & BLE Engineer
BLE checks every packet at the link layer, so it is fair to ask why an application would add its own checksum on top. The answer is that the link layer protects packets, and we care about messages.
A message that has been split into many chunks can go wrong in ways no single packet reveals. A chunk can be missing, duplicated or reassembled in the wrong position because of a bug on either side. Every packet arrived intact, and the message is still wrong.
So each complete payload in our serial stack carries a CRC-16/ARC checksum. The sender computes it over the whole message. The receiver recomputes it after reassembly and discards the message if the two do not match.
We chose CRC-16/ARC because it is a well-known standard that firmware teams already have tested implementations of. A checksum both sides can implement identically on day one is worth more than a stronger one that takes a week to agree on.
The practical effect is that corruption becomes a clear, logged event: checksum failed, message dropped, sender retries. Without it, bad data flows into the app and shows up later as a wrong value on a screen, far from its cause.
Topics
Working on a similar challenge?
Let's discuss the architecture before you build.
BLE system design, OTA reliability, and connected product engineering — this is what TEJVON does every day.
Book a Technical Consultation