MOD5234-100IR NetBurner Inc, MOD5234-100IR Datasheet - Page 603

• Manufacturer Part Number: MOD5234-100IR
• Description: MOD5234 10/100 ETHERNET MODULE
• Manufacturer: NetBurner Inc
• Type: Controllers & Processorsr

Specifications of MOD5234-100IR

• Interface: I²C, SPI, UART
• Voltage - Supply: 2.5V
• Mounting Type: Surface Mount
• Package / Case: Module
• Product: Modules
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Data Format: -
• Baud Rates: -
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: Q4483564

28.4.2.3 HMAC Hash
28.4.3
EHMAC can only be performed with the SHA-1 algorithm. The Enhanced HMAC requires the
keys to be hashed with IPAD and OPAD prior to the step below. The IPAD and OPAD step can be
Freescale Semiconductor
10. If MDSR[DONE] is set or done interrupt is triggered, then read the message digest and the
1. Reset the MDHA using the MDCMR[SWR] bit.
2. MDCR register write. Enable the interrupts. (optional)
3. MDMR register write. Select algorithm, data padding, and HMAC.
4. MDMDS register write. Load this register with the length of the message from the OPAD
5. Direct context load of (OPAD XOR key) into MDx1 registers from the OPAD step in the
6. Direct context load of (IPAD XOR key) into MDx0 registers from the IPAD step.
7. Direct context load of MDMDS register from the IPAD step (this should be 64 bytes).
8. Fill data FIFO with message to be hashed.
9. MDDSR register write. Load this register with the length of the message data (without
10. MDHA does the required algorithm’s auto padding of the message.
11. Set the MDCMR[GO] bit.
12. Wait for MDSR[INT] to be set or done interrupt to be triggered to indicate successful
13. If MDSR[DONE] is set or done interrupt is triggered, then read the message digest from
message digest count from the message digest registers.
step.
previous section.
padding) in bytes.
completion (or failure).
the message digest registers.
Performing a SHA-1 EHMAC
You will need to provide a time-out feature in your interrupt handler.
The MDHA will stall with no response if it is waiting for message
data. This will most likely occur if the MDDSR write is not received
or auto-padding is disabled and a partial message block is provided.
You will need to provide a time-out feature in your interrupt handler.
The MDHA will stall with no response if it is waiting for message
data. This will most likely occur if the MDDSR write is not received
or auto-padding is disabled and a partial message block is provided.
MCF5235 Reference Manual, Rev. 2
NOTE
NOTE
Initialization/Application Information
28-17