PEF82912FV14XP Lantiq, PEF82912FV14XP Datasheet - Page 62

• Manufacturer Part Number: PEF82912FV14XP
• Manufacturer: Lantiq

Specifications of PEF82912FV14XP

• Number Of Line Interfaces: 1
• Control Interface: HDLC
• Lead Free Status / Rohs Status: Supplier Unconfirmed

2.3.3.3
The master mode is selected by default if one of the microcontroller interfaces is
selected. The monitor data is written by the microcontroller in the MOX register and
transmitted via IOM -2 DD(DU) line to the programmed/controlled device e.g. ARCOFI-
BA PSB 2161. The transfer of the commands in the MON channel is regulated by the
handshake protocol mechanism with MX, MR.
2.3.3.4
MONITOR slave mode can be selected by pinstrapping the microcontroller interface pins
according to
MONITOR time slot on the IOM -2 and is transferred to the MOR register. The transfer
of the commands in the MON channel is regulated by the handshake protocol
mechanism with MX, MR which is described in the previous
The first byte of the MONITOR message must contain in the higher nibble the MONITOR
channel address code which is ’1000’ for the Q-SMINT I. The lower nibble distinguishes
between a programming command and an identification command.
Identification Command
In order to be able to identify unambiguously different hardware designs of the Q-
SMINT I by software, the following identification command is used:
DU 1st byte value
DU 2nd byte value
The Q-SMINT I responds to this identification sequence by sending a identification
sequence:
DD 1st byte value
DD 2nd byte value
DESIGN: six bit code, specific for each device in order to identify differences in operation
(see
This identification sequence is usually done once, when the Q-SMINT I is connected for
the first time. This function is used so that the software can distinguish between different
possible hardware configurations. However this sequence is not compulsory.
Programming Sequence
The programming sequence is characterized by a ’1’ being sent in the lower nibble of the
received address code. The data structure after this first byte is equivalent to the
structure of the serial control interface described in chapter
Data Sheet
“ID - Identification Register” on Page
MONITOR Channel Programming as a Master Device
MONITOR Channel Programming as a Slave Device
Table
4. All programming data required by the device is received in the
1
0
1
0
0
0
0
0
0
0
0
0
0
0
48
164).
DESIGN
0
0
0
0
0
0
0
0
0
Chapter
0
0
0
Functional Description
Chapter
<IDENT>
PEF 82912/82913
2.3.3.1.
2.1.1.
2001-03-30