Arduino Library for Adler-32, Adler-16 and Adler-64 checksum.

This library provides an Adler32 checksum of a data block, typical an array of bytes. The library also supports an Adler16 (0.2.0) and Adler64 (0.3.0) implementation.

This Adler16 is often faster as it uses a smaller checksum than the Adler32. The price is that Adler16 is less sensitive for error detection than Adler32 as less possible checksums are possible. Still it will have its niches where it will be useful.

The Adler64 is much slower as uint64 is not (seldom) supported on Arduino alike boards in hardware. Furthermore the checksum, in HEX notation does look similar to the Adler32 value. So only for big files (dozens to hundreds of MB's) the Adler64 shows its value.

0.2.0 is a breaking change, file names have been changed to be more in line with the CRC library.

• Adler.h for the static functions
• Adler32.h for the Adler32 class
• Adler16.h for the Adler16 class.

0.3.0 supports experimental 64 bit.

• Adler64.h for the Adler64 class.
• performance is low due to emulation of 64 bit

Feedback as always is welcome.

• https://en.wikipedia.org/wiki/Adler-32
• https://github.com/RobTillaart/Adler
• https://github.com/RobTillaart/CRC
• https://github.com/RobTillaart/Fletcher
• https://github.com/RobTillaart/LUHN

Tested on Arduino UNO and ESP32 (except 64 bit).

#include "Adler32.h"
// or 
#include "Adler16.h"

The interface for the Adler16 and Adler64 class is very similar.

• Adler32() Constructor, initializes internals.
• void begin(uint32_t s1 = 1, uint32_t s2 = 0) resets the internals. optional setting start values for s1 and s2. Note this is not part of the standard. These parameters allows a restart from a specific index in a buffer.

• void add(uint8_t value) add a single value to the checksum.
• uint32_t add(uint8_t * array, uint16_t length) add an array of values to the checksum. Returns the current checksum.
• uint32_t addFast(uint8_t * array, uint16_t length) add an array of values to the checksum. Is faster by trading PROGMEM for performance. Returns the current checksum.

The class is typically used for streaming very large blocks of data, optional with intermediate checksum tests (e.g after every 256 bytes)

Wrappers exist for adding char and char array. Functional identical to above.

• void add(char value)
• uint32_t add(char * array, uint16_t length)
• uint32_t addFast(char * array, uint16_t length)

• uint32_t getAdler() get the current checksum.
• uint32_t count() get the number of items added. Merely a debugging feature, can overflow without affecting checksum.

Only tested on UNO and ESP32 yet. If you have data of other platforms, please let me know.

Numbers measured with Adler32_performance.ino.

The add(value) adds one byte and does a subtraction instead of a modulo.

The add(array, length) is a straightforward loop over the array and has a small footprint.

Note: add() is about 6.6 us per byte.

The addFast(array, length) is faster than the reference add(array, length) and uses 108 bytes more (UNO). So the function has a larger footprint. Depending on your needs, choose performance or footprint.

See Adler32_performance_addFast.ino

Note: addFast() is less than 2 us per byte.

Only tested on UNO and ESP32 yet. If you have data of other platforms, please let me know.

Numbers measured with Adler16_performance.ino.

The add(value) adds one byte and does a subtraction instead of a modulo.

The per byte performance of the Adler16 (on UNO) is faster than the Adler32 add(value). The reason is that a 16 bit subtraction on an UNO is faster than a 32 bit subtraction.

The add(array, length) is a straightforward loop over the array and has a small footprint.

Note: add() is about 6.6 us per byte.

The addFast(array, length) is faster than the reference add(array, length).

The gain of the faster 16 bit modulo meets the frequency of doing the modulo more often.

Experimental

Only tested on UNO R3. If you have data of other platforms, please let me know.

Numbers measured with Adler64_performance.ino.

The performance of Adler64 class is much slower than Adler32. Reason is that the uint64_t is not supported in hardware and is emulated.

TODO: detailed numbers (?).

#include "Adler.h"

The static functions are typically used for an in memory buffer to calculate the checksum once. Think of packets in a network, records in a database, or a checksum for an configuration in EEPROM.

The functions are straightforward. Length is in bytes (8 bits).

• uint64_t adler64(uint8_t *data, uint16_t length, uint64_t s1 = 1, uint64_t s2 = 0)
• uint32_t adler32(uint8_t *data, uint16_t length, uint32_t s1 = 1, uint32_t s2 = 0)
• uint16_t adler16(uint8_t *data, uint16_t length, uint16_t s1 = 1, uint16_t s2 = 0)

Three wrapper functions added in 0.2.4 for char array's (convenience).

• uint64_t adler64(char *data, uint16_t length, uint64_t s1 = 1, uint64_t s2 = 0)
• uint32_t adler32(char *data, uint16_t length, uint32_t s1 = 1, uint32_t s2 = 0)
• uint16_t adler16(char *data, uint16_t length, uint16_t s1 = 1, uint16_t s2 = 0)

Note the 64 bit version is experimental.

Only tested on UNO and ESP32 yet. If you have data of other platforms, please let me know.

Numbers measured with Adler_performance.ino.

Lorem Ipsum text = 868 bytes.

The performance of the adler64 is slow as the UNO does not support 64 bit in hardware (emulation). If one does not use the Adler64 in a sketch, the performance figures of 0.2.0 "return".

Adler32 average 1116 / 868 = 1.29 us per byte. Adler16 average 1736 / 868 = 2.00 us per byte. (~1.5x slower !)

Adler16 does more often the modulo math as it reaches halfway uint16_t faster than Adler32 reaches halfway uint32_t.

As the Adler16 is less performant as the Adler32 (on all tested platforms), Adler32 is often the best choice to use the 32 bit version.

See examples.

• improve documentation
• redo performance testing
  • next major upgrade(0.3.0)
  • other platforms?
• extend unit tests
  • s1 s2 parameter static functions
  • Adler64 unit tests?

• optimize performance of adler64 by doing math in 32 bit (partially)?
• void add(String str);?

• do the string wrappers need strlen() ? parameter.
  • yes, as string can be processed partially.
• no return value for add(value)
  • would create too much overhead for repeated calls.

If you appreciate my libraries, you can support the development and maintenance. Improve the quality of the libraries by providing issues and Pull Requests, or donate through PayPal or GitHub sponsors.

Thank you,