Please note the added description above about input data. This could have resulted in the fact that the calculated CRC value of 0x01 differs to e.g. If a single string has more than eight digits, only the first eight digits are used.Ģ: Added the support for 64bit CRC calculation and for binary string input.ġ: Added the option to print the CRC lookup table 'reversed'.ħ: Fixed a bug: A hexadecimal value with more than two digits after the "0x" is not correctly parsed.
If a single string has less than eight digits, zeros are padded as prefix, so 100 is actually interpreted as 00000100. If the input data is defined as 'binary string', then the byte values shall be given as eight-digit binary strings, separated by a white space.Note that this means that "01" and "0001" are then NOT the same. So instead of "0x31 0x32", it's also possible to specify "3132". If no whitespace is detected, the "0x" prefix must be omitted and always two digits are taken for a character. If the input data is defined as 'bytes', then the byte values shall be given in hexadecimal notation beginning with a "0x" and separated by a white space, e.g "0x31 0x32".
This means that the CRC of input string "12" and byte input 0x31 0x32 is the same. the string "12" is converted to its ASCII respresentation.
0 kommentar(er)
