nRF52 CRCSTATUS

RE: nRF52 CRCSTATUS

Dmitry — Tue, 25 Aug 2020 12:48:13 GMT

Hi Hugh,

sorry, we're using Keil and clang, no experience with SES. I believe they use standard algorithm, the only things to adjust are polynomial, initial value and their endiannes.

RE: nRF52 CRCSTATUS

hmolesworth — Fri, 21 Aug 2020 16:01:03 GMT

Hi Dmitry, unrelated question, have you used BinaryFile.crc32() in Segger? script_class_BinaryFile.htm Looks like emScript allows calculation and placement of a 32-bit CRC. We currently use what looks like the same CRC32 but require a simple external tool to calculate and insert in the hex file rather than running the code then editing the project. srec_cat allows this, but gives a different hex CRC32.

srec_cat manuf_driver3-832.hex -i -crop 0 0x0158D0 -fill 0xFF 0 0x0158D0 -STM32_Little_Endian 0x0158D4 -o a1.hex -i

Worst-case we have to modify the code to match srec_cat calculation, but I'd rather use a SES script which runs on every build to populate the CRC vector. There is an example of build number increment on page 892 of the v4.52C manual, but time is short and I'd rather just copy something which already is tested ..

RE: nRF52 CRCSTATUS

Dmitry — Sat, 30 May 2020 18:38:37 GMT

Hi,

The probability of having a corrupted data with right CRC24 is 1/(2^24). It's not related to nRF52832, just mathematics. If you need better reliablilty, you have to use CRC32 implemented in software.