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

• 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

Freescale Semiconductor
27–24
22–19
Bits
31
30
29
28
23
Name
FEND
MDIS
HLTF
STF
—
—
—
Force end. Assertion terminates any current running thread as if an END instruction had
been executed. For more information, refer to the eTPU User’s Manual.
0 Normal operation.
1 Ends any ongoing threads.
This bit is self-clearing when the thread ends. If the microengine is in TST, halted, stopped,
or idle (no thread executing), setting FEND has no effect and the bit stays cleared.
Low power module disable bit. When MDIS is set, the engine shuts down its internal
clocks. TCR1 and TCR2 cease to increment, and input sampling stops. The engine asserts
the stop flag (STF) bit to indicate that it has stopped. However, the BIU continues to run,
and the host can access all registers except for the channel registers (see Note). More
information on channel registers may be found in
and Control
channel registers is not meaningful, a bus error is issued, and writes are unpredictable.
When the MDIS bit is set while the microcode is executing, the eTPU will stop when the
thread is complete.
0 eTPU engine runs.
1 Commands engine to stop its clocks.
Stop completes on the next system clock after the stop condition is valid. The MDIS bit is
write-protected when ETPU_MCR[VIS]=1.
Note: The timebase registers can still be read in stop mode, but writes are unpredictable
and a bus error is issued. Global channel registers and SDM can be accessed normally.
Reserved.
Stop flag bit. The engine asserts its stop flag (STF) to indicate that it has stopped. Only
then the host can assume that the engine has actually stopped. In case of the MCF5235
device being placed in Stop mode, the eTPU system responds with a stop acknowledge
only after any ongoing thread is complete.
0 The engine is operating.
1 The engine has stopped (after the local MDIS bit has been asserted).
Reserved.
Halt mode flag. If eTPU engine entered halt state, this flag is asserted. The flag remains
asserted while the microengine is in halt state, even during a single-step or forced
instruction execution. Refer to the eTPU User’s Manual. for further details about entering
halt mode.
0 eTPU engine is not halted.
1 eTPU engine is halted
Reserved.
Table 20-6. ETPU_ECR Field Descriptions
MCF5235 Reference Manual, Rev. 2
Registers.” After MDIS is set, even before STF asserts, data read from the
Description
Section 20.6.2.4, “Channel Configuration
Memory Map/Register Definition
20-21