dsc_crc#
Overview#
The CRC Example project is a demonstration program that uses the KSDK software to generate checksums for an ASCII string. Several CRC protocols are implemented using the CRC driver API.
Running the demo#
Example output on terminal:
CRC Peripheral Driver Example.
Test same string base on different CRC protocol. test string: 123456789 1.CRC-16 CCIT FALSE: 0x29b1 2.CRC-16 KERMIT: 0x2189 3.CRC-16 MAXIM: 0x44c2 4.CRC-32: 0xcbf43926 5.CRC-32 POSIX: 0x765e7680
Test different string based on CRC-32 POSIX protocol. 1.test string: abcdefgh CRC-32 POSIX: 0x5024ec61 2.test string: abcd1234 CRC-32 POSIX: 0x3fbda0ab
Supported Boards#
MC56F80000-EVK
Hardware requirements
Micro USB cable
MC56F80000-EVK board
Personal Computer
Board hardware common setting
Power setting:
Connect J8 pin2 and pin3 Connect J6 pin1 and pin2 Connect J5 pin1 and pin2
Reset pin setting:
Connect J11 pin2 and pin3
Debugger setting:
Connect J13 pin 1-2, 3-4, 5-6, 7-8
Board settings
No special settings are required.
Prepare the Demo
Connect USB cable between the host PC and the J12 USB port on the target board. It setups Multilink and COM port in PC device manager.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board with Multilink debug configuration.
Launch the debugger in your IDE to begin running the demo.
Running the demo
The log below shows example output of the CRC driver demo in the terminal window:
CRC Peripheral Driver Example.
Test same string base on different CRC protocols.
test string: 123456789
1.CRC-16 CCIT FALSE: 0x29b1
2.CRC-16 KERMIT: 0x2189
3.CRC-16 MAXIM: 0x44c2
4.CRC-32: 0xcbf43926
5.CRC-32 POSIX: 0x765e7680
Test different strings based on CRC-32 POSIX protocol.
1.test string: abcdefgh
CRC-32 POSIX: 0x5024ec61
2.test string: abcd1234
CRC-32 POSIX: 0x3fbda0ab
MC56F81000-EVK
Hardware requirements
2 x Micro USB cable
MC56F81000-EVK board
Personal Computer
Board hardware common setting
Power setting:
Connect J8 pin2 and pin3 Connect J5 pin1 and pin2 Connect J6 pin1 and pin2
Onboard PnE U-MultiLink debugger setting:
Connet J11 pin2 and pin3 Connect J13 pin 1-2, 3-4, 5-6, 7-8, to setup onboard debugger PnE U-MultiLink. Note: when use external debugger(connected to J10), leave all J13 pins open.
Board settings
No special settings are required.
Prepare the Demo
Connect USB cable between the host PC and the USB(J26) port on the target board to setup USB to UART bridge.
Connect USB cable between the host PC and the USB(J12) port on the target baord to setup mulitlink debugger.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board with PnE U-MultiLink debug configuration.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo. Please be noted default FCF(flash configuration field) makes the MCU boot from flash.
Running the demo
The log below shows example output of the CRC driver demo in the terminal window:
CRC Peripheral Driver Example.
Test same string base on different CRC protocols.
test string: 123456789
1.CRC-16 CCIT FALSE: 0x29b1
2.CRC-16 KERMIT: 0x2189
3.CRC-16 MAXIM: 0x44c2
4.CRC-32: 0xcbf43926
5.CRC-32 POSIX: 0x765e7680
Test different strings based on CRC-32 POSIX protocol.
1.test string: abcdefgh
CRC-32 POSIX: 0x5024ec61
2.test string: abcd1234
CRC-32 POSIX: 0x3fbda0ab
MC56F83000-EVK
Hardware requirements
Micro USB cable
MC56F83000-EVK board
Personal Computer
Board hardware common setting
Power setting:
Connect J19 pin2 and pin3 Connect J12 pin1 and pin2 Connect J13 pin1 and pin2 Connect J15 pin1 and pin2 Connect J16 pin2 and pin3 Connect J17 pin1 and pin2
Onboard OSJTAG debugger setting:
Leave J5 open Leave J6 open Note: J6 is only used(connected) when firmware update for onboard debugger OSJTAG. Connect J11 pin 1-2, 3-4, 5-6, 7-8, to setup onboard debugger OSJTAG. Note: when use external debugger(connected to J10), leave all J11 pins open.
Board settings
No special settings are required.
Prepare the Demo
Connect USB cable between the host PC and the JM60 USB(J8) port on the target board. It setups OSJTAG and COM port in PC device manager.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board with OSJTAG debug configuration.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo. Please be noted that default FCF(flash configuration field) setting makes MCU boot from bootloader. So after reset button press, it will wait 5s(wait in bootloader) to run the application code.
Running the demo
The log below shows example output of the CRC driver demo in the terminal window:
CRC Peripheral Driver Example.
Test same string base on different CRC protocols.
test string: 123456789
1.CRC-16 CCIT FALSE: 0x29b1
2.CRC-16 KERMIT: 0x2189
3.CRC-16 MAXIM: 0x44c2
4.CRC-32: 0xcbf43926
5.CRC-32 POSIX: 0x765e7680
Test different strings based on CRC-32 POSIX protocol.
1.test string: abcdefgh
CRC-32 POSIX: 0x5024ec61
2.test string: abcd1234
CRC-32 POSIX: 0x3fbda0ab
TWR-MC56F8400
Hardware requirements
Mini USB cable
TWR-MC56F8400 board
Personal Computer
Board hardware common setting
Power setting:
Connect J11 pin1 and pin2 Connect J6 pin1 and J7 pin2
UART setting:
Connect J8 pin3 and pin4 Connect J9 pin3 and pin4
Onboard OSJTAG debugger setting:
Connect J20 pin1 and pin2. Leave J17 open. Note: J17 is only used(connected) when firmware update for onboard debugger OSJTAG. Connect J21 pin 1-2, 3-4, 5-6, 7-8, to setup onboard debugger OSJTAG. Note: when use external debugger(connected to J14), leave all J21 pins open
Board settings
No special settings are required.
Prepare the Demo
Connect USB cable between the host PC and the JM60 USB(J18) port on the target board. It setups OSJTAG and COM port in PC device manager.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board with OSJTAG debug configuration.
Launch the debugger in your IDE to begin running the demo.
Running the demo
The log below shows example output of the CRC driver demo in the terminal window:
CRC Peripheral Driver Example.
Test same string base on different CRC protocols.
test string: 123456789
1.CRC-16 CCIT FALSE: 0x29b1
2.CRC-16 KERMIT: 0x2189
3.CRC-16 MAXIM: 0x44c2
4.CRC-32: 0xcbf43926
5.CRC-32 POSIX: 0x765e7680
Test different strings based on CRC-32 POSIX protocol.
1.test string: abcdefgh
CRC-32 POSIX: 0x5024ec61
2.test string: abcd1234
CRC-32 POSIX: 0x3fbda0ab