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

• 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.3.3.5 Hashing Engine Control
This module is the control unit of the MDHA that is capable of computing the Secure Hash
Algorithm (SHA-1) and Message Digest 5 algorithm (MD5). This module keeps track of all
rounds and tells the rest of the module when the operation has been completed.
28.3.3.6 Status Interrupt
This block generates the error interrupt if the host performs an illegal operation. The cause of the
error is flagged in the MDISR
(MDISR and
core from continuing operation with invalid data.
28.4
28.4.1
28.4.2
The HMAC is done in three separate steps without the MACFULL bit. Each step requires the
reinitialization of the MDHA.
Freescale Semiconductor
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 algorithm initialization.
4. Write message data into the FIFO in longwords.
5. MDDSR register write. Load this register with the length of the message data (without
6. Set MDCMR[GO].
7. Wait for MDSR[INT] to be set or done interrupt to be triggered to indicate successful
8. If MDSR[DONE] is set or done interrupt is triggered, then read the message digest from
padding) in bytes.
completion (or failure).
the message digest registers.
Initialization/Application Information
Performing a Standard HASH Operation
Performing a HMAC Operation Without the MACFULL Bit
MDIMR)”). If an error occurs, the MDHA core engine is halted. This prevents the
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.
(Section 28.2.5, “MDHA Interrupt Status & Mask Registers
MCF5235 Reference Manual, Rev. 2
NOTE
Initialization/Application Information
28-15