The principle and implementation method of CRC check

Publisher:innovator8Latest update time:2021-07-13 Source: eefocus Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

1. Introduction to CRC Check

        Cyclic Redundancy Check (CRC) is a commonly used checksum with error detection and correction capabilities. It is widely used in early communications. Cyclic Redundancy Check is often used for data verification of external storage and computer synchronous communication. Cyclic Redundancy Check establishes the agreed relationship between data bits and check bits through some mathematical operations.


        Different from parity check, sum check, XOR check and other verification methods, the calculation process of CRC check is relatively complicated.


2. Introduction to Modulo 2 Division

        Although the CRC check principle seems complicated, it is not difficult to understand. The basic idea is to first append a number to the frame to be sent, generate a new frame and send it to the receiving end. Of course, this additional number is not random. It must make the generated new frame divisible by a specific number selected by the sending and receiving ends. Here, binary division is not directly used, but a method called "modulo 2 division" is used. After reaching the receiving end, the received new frame is divided by the selected divisor (also using "modulo 2 division"). Because the sender has added a number before sending the data frame, the "remainder removal" process has been performed, so the result should have no remainder and the result can be divided by the divisor. If there is a remainder, it means that an error has occurred in the transmission process of the frame.


        Here, in order to have a deeper understanding of CRC verification, let's introduce modulo 2 division. It is similar to "arithmetic division", but it does not borrow from the upper bit, nor does it compare the values ​​of the same bits of the divisor and dividend. As long as the same number of bits is used for division, it will be fine. Modulo 2 subtraction is actually a bitwise XOR operation. That is, after comparison, if the corresponding bits of the two are the same, the result is "0", and if they are different, the result is "1". As shown in the figure below, the binary number 1010101 is divided by 1001, and the result is 1011, and the remainder is 110.

3. CRC verification principle

        Above we have briefly introduced CRC verification. Now let’s take a look at how CRC verification is implemented.


       First, in order to perform CRC check, the sender and receiver must agree on a divisor, which is usually expressed in a polynomial form, and this polynomial is also called a "generator polynomial". For example, the commonly used polynomial x4 + x + 1 represents a divisor of 10011, and the polynomial x16 + x15 + x2 + 1 represents a divisor of 110000000000000101. The following table lists the commonly used divisor polynomial formulas.


CRC algorithm name Polynomial formula Width Polynomial Initial value Result XOR value Input inversion Output inversion

CRC-4/ITU x4 + x + 1 4 03 00 00 true true

CRC-5/EPC x5 + x3 + 1 5 09 09 00 false false

CRC-5/ITU x5 + x4 + x2 + 1 5 15 00 00 true true

CRC-5/USB x5 + x2 + 1 5 05 1F 1F true true

CRC-6/ITU x6 + x + 1 6 03 00 00 true true

CRC-7/MMC x7 + x3 + 1 7 09 00 00 false false

CRC-8 x8 + x2 + x + 1 8 07 00 00 false false

CRC-8/ITU x8 + x2 + x + 1 8 07 00 55 false false

CRC-8/ROHC x8 + x2 + x + 1 8 07 FF 00 true true

CRC-8/MAXIM x8 + x5 + x4 + 1 8 31 00 00 true true

CRC-16/IBM x16 + x15 + x2 + 1 16 8005 0000 0000 true true

CRC-16/MAXIM x16 + x15 + x2 + 1 16 8005 0000 FFFF true true

CRC-16/USB x16 + x15 + x2 + 1 16 8005 FFFF FFFF true true

CRC-16/MODBUS x16 + x15 + x2 + 1 16 8005 FFFF 0000 true true

CRC-16/CCITT x16 + x12 + x5 + 1 16 1021 0000 0000 true true

CRC-16/CCITT-FALSE x16 + x12 + x5 + 1 16 1021 FFFF 0000 false false

CRC-16/X25 x16 + x12 + x5 + 1 16 1021 FFFF FFFF true true

CRC-16/XMODEM x16 + x12 + x5 + 1 16 1021 0000 0000 false false

CRC-16/DNP x16 + x13 + x12 + x11 + x10 + x8 + x6 + x5 + x2 + 1 16 3D65 0000 FFFF true true

CRC-32 x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 32 04C11DB7 FFFFFFFF FFFFFFFF true true

CRC-32/MPEG-2 x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 32 04C11DB7 FFFFFFFF 00000000 false false

        After selecting the divisor, you need to add k-1 "0" bits after the data to be sent, where k is the number of digits of the divisor. Then divide the new number with k-1 "0" bits added (a total of m+k-1 bits) by the divisor in the "modulo 2 division" method, and the remainder is the CRC check code of the data. However, it should be noted that the number of digits of the remainder must be one less than the number of digits of the divisor, even if the first digit is 0, or even all 0 (when it is divisible), it cannot be omitted.


        Finally, the check code is appended to the original data to construct a new frame and send it to the receiving end. Finally, the receiving end divides the new frame by the previously selected divisor using "modulo 2 division". If there is no remainder, it indicates that there was no error in the transmission of the frame, otherwise an error occurred.


        Next, we use an example to illustrate the calculation process of CRC check.


       Suppose we calculate the CRC checksum of the hexadecimal number 0xBB, and the generator polynomial we use is x4 + x + 1. The number to be calculated is represented by the binary bit 1011 1011, and the divisor is 10011. Since the number of bits of the generator polynomial is 5, according to the above introduction, the number of bits of the CRC checksum is 4 (the number of bits of the checksum is 1 less than the number of bits of the generator polynomial). Therefore, add 4 more zeros after the original data to get 1011 1011 0000, and then divide this number by the generator polynomial in the "modulo 2 division" method, and the remainder (i.e. CRC code) is 1111, as shown in the figure below.

        Replace the four "0"s after the original frame 1011 1011 0000 with the CRC check 1111 calculated in the previous step to get the new frame 1011 1011 1111. Then send this new frame to the receiving end. When the above new frame arrives at the receiving end, the receiving end will divide the new frame with the divisor 10011 selected above in the "modulo 2 division" mode to verify whether the remainder is 0. If it is 0, it proves that there is no error in the transmission process of the frame data, otherwise there is an error.


4. CRC check c code implementation

        The calculation process of CRC check is relatively complicated, and the general code implementation adopts the table lookup method. The following code is the code for CRC16 check implementation, the corresponding CRC algorithm is CRC-16/MODBUS, and the generated polynomial is x16 + x15 + x2 + 1.


#include

 

const unsigned char chCRCHTalbe[] = //CRC high byte value table

{

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41,

0x00, 0xC1, 0x81, 0x40

};

 

const unsigned char chCRCLTalbe[] = //CRC low byte value table

{

0x00, 0xC0, 0xC1, 0x01, 0xC3, 0x03, 0x02, 0xC2, 0xC6, 0x06, 0x07, 0xC7,

0x05, 0xC5, 0xC4, 0x04, 0xCC, 0x0C, 0x0D, 0xCD, 0x0F, 0xCF, 0xCE, 0x0E,

0x0A, 0xCA, 0xCB, 0x0B, 0xC9, 0x09, 0x08, 0xC8, 0xD8, 0x18, 0x19, 0xD9,

0x1B, 0xDB, 0xDA, 0x1A, 0x1E, 0xDE, 0xDF, 0x1F, 0xDD, 0x1D, 0x1C, 0xDC,

0x14, 0xD4, 0xD5, 0x15, 0xD7, 0x17, 0x16, 0xD6, 0xD2, 0x12, 0x13, 0xD3,

0x11, 0xD1, 0xD0, 0x10, 0xF0, 0x30, 0x31, 0xF1, 0x33, 0xF3, 0xF2, 0x32,

0x36, 0xF6, 0xF7, 0x37, 0xF5, 0x35, 0x34, 0xF4, 0x3C, 0xFC, 0xFD, 0x3D,

0xFF, 0x3F, 0x3E, 0xFE, 0xFA, 0x3A, 0x3B, 0xFB, 0x39, 0xF9, 0xF8, 0x38,

0x28, 0xE8, 0xE9, 0x29, 0xEB, 0x2B, 0x2A, 0xEA, 0xEE, 0x2E, 0x2F, 0xEF,

0x2D, ​​0xED, 0xEC, 0x2C, 0xE4, 0x24, 0x25, 0xE5, 0x27, 0xE7, 0xE6, 0x26,

0x22, 0xE2, 0xE3, 0x23, 0xE1, 0x21, 0x20, 0xE0, 0xA0, 0x60, 0x61, 0xA1,

0x63, 0xA3, 0xA2, 0x62, 0x66, 0xA6, 0xA7, 0x67, 0xA5, 0x65, 0x64, 0xA4,

0x6C, 0xAC, 0xAD, 0x6D, 0xAF, 0x6F, 0x6E, 0xAE, 0xAA, 0x6A, 0x6B, 0xAB,

0x69, 0xA9, 0xA8, 0x68, 0x78, 0xB8, 0xB9, 0x79, 0xBB, 0x7B, 0x7A, 0xBA,

0xBE, 0x7E, 0x7F, 0xBF, 0x7D, 0xBD, 0xBC, 0x7C, 0xB4, 0x74, 0x75, 0xB5,

0x77, 0xB7, 0xB6, 0x76, 0x72, 0xB2, 0xB3, 0x73, 0xB1, 0x71, 0x70, 0xB0,

0x50, 0x90, 0x91, 0x51, 0x93, 0x53, 0x52, 0x92, 0x96, 0x56, 0x57, 0x97,

0x55, 0x95, 0x94, 0x54, 0x9C, 0x5C, 0x5D, 0x9D, 0x5F, 0x9F, 0x9E, 0x5E,

0x5A, 0x9A, 0x9B, 0x5B, 0x99, 0x59, 0x58, 0x98, 0x88, 0x48, 0x49, 0x89,

0x4B, 0x8B, 0x8A, 0x4A, 0x4E, 0x8E, 0x8F, 0x4F, 0x8D, 0x4D, 0x4C, 0x8C,

0x44, 0x84, 0x85, 0x45, 0x87, 0x47, 0x46, 0x86, 0x82, 0x42, 0x43, 0x83,

0x41, 0x81, 0x80, 0x40

};

 

unsigned short CRC16(unsigned char* pchMsg, unsigned short wDataLen)

[1] [2]
Reference address:The principle and implementation method of CRC check

Previous article:A simple microcontroller serial port assistant program implemented in Python
Next article:MC9S12X Series Dual-core MCU Coprocessor (Xgate) Study Notes

Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号