Häufig gestellte Fragen
- M051-Base-Serie(95)
- M0518-Serie(97)
- M0519-Serie(43)
- M0564-Serie(1)
- Mini51-Base-Serie(90)
- Nano100/102-Base-Serie(101)
- Nano103-Base-Serie(10)
- Nano110/112-LCD-Serie(100)
- Nano120-USB-Serie(111)
- Nano130-Advanced-Serie(110)
- NUC029-Serie(94)
- NUC100/200-Advanced-Serie(102)
- NUC120/122/123/220-USB-Serie(116)
- NUC121/125-Serie(1)
- NUC126-USB-Serie(2)
- NUC130/230-CAN-Serie(103)
- NUC131-NUC1311-CAN-Serie(98)
- NUC140/240-Konnektivität-Serie(114)
- M451-Base-Serie(118)
- M451M-Serie(117)
- M452-USB-Serie(130)
- M4521 USB Serie(1)
- M453-CAN-Serie(128)
- M463 CAN FD/USB HS Series(1)
- M467 Ethernet/Crypto Series(1)
- M471 Series(1)
- M479 Motor Control Series(1)
- M481-Base-Serie(4)
- M482-USB-FS-OTG-Serie(4)
- M483-CAN-Serie(4)
- M484-USB-HS-OTG-Serie(4)
- M485-Crypto-Serie(4)
- M487-Ethernet-Serie(4)
- M4TK-Touch-Key-Serie(25)
- NUC442/472-Serie(130)
- NUC472 Series(1)
- NUC505-Serie(138)
FAQ
Why is the M480 AES sample output different from the network tool? http://testprotect.com/appendix/AEScalc Issue Date:2018-11-27
In the case of a network tool:
Key: 000102030405060708090a0b0c0d0e0f
Plaintext: 00112233445566778899aabbccddeeff
Ciphertext: 69c4e0d86a7b0430d8cdb78070b4c55a
The key input corresponding to the AES register:
CRYPTO_AESn_KEY0 = 0x00010203
CRYPTO_AESn_KEY1 = 0x04050607
CRYPTO_AESn_KEY2 = 0x08090a0b
CRYPTO_AESn_KEY3 = 0x0c0d0e0f
Input data:
CRYPTO_AES_DATIN = { 0x00112233, 0x44556677, 0x8899aabb, 0xccddeeff }
The obtained output data:
CRYPTO_AES_DATOUT = { 0x69c4e0d8, 0x6a7b0430, 0x d8cdb780, 0x70b4c55a }
It should be noted that the data processing of AES is handled by the variable type of WORD. There are different LSBs and MSBs from the variable type of BYTE.
Products: | Microcontrollers ,Arm Cortex-M4 MCUs ,M481 Base Series ,M482 USB FS OTG Series ,M483 CAN Series ,M484 USB HS OTG Series ,M485 Crypto Series ,M487 Ethernet Series |
---|---|
Applications: | |
Function: |