12
T90FJR
Rev. A – 25-Oct-01
Appendix C: Out of Band connection
When used in OpenCable™ compliant Host designs, the CIMaX™ requires additional
glue logic to handle the Point-Of-Deployment (POD) module interface. Hardware differ-
ences between a standard DVB Common Interface implementation and an OpenCa-
ble™ implementation consist in the following:
1. Particular care must be taken for MOCLKA and MOCLKB connections to module
slots. According to [6], MOCLKA/B are connected to pin 14 while they are con-
nected to pin 57 in [2].
2. An OpenCable™ receiver shall control the PCMCIA CE2# pin to enable the
Extended Channel, as defined by SCTE DVS 131.
3. An OpenCable™ receiver shall include a DES-ECB descrambler and be able to
simultaneously store one 64-bit key pair, as defined by the NRSS Part B Copy
Protection Framework (EIA 679 Part B proposed revision -679BrAv5).
4. An OpenCable™ receiver shall include, as defined by SCTE DVS 131, both the
OOB RF transmitter and receiver blocks, and manage the connection between
these blocks and the POD module across the PCMCIA interface, if it wants to
take advantage of the POD Out-of-band PHY and MAC capability.
The CIMaX™ has built-in capability to address Point 2. It doesn't include any crypto-
graphic function and as such a separate descrambler must be inserted between the TS
output of the last CIMaX™ in the daisy chain and the demultiplexer to address Point 2.
This application note doesn't intend to describe how the descrambler shall be connected
to the CIMaX™, however provisions shall be made to ensure that this descrambler
could be driven by the CI Driver™ software stack.
Concerning Point 3 and the OOB Channel, this application note describes how to route
the six I/Os of the OOB RF transmitter and receiver blocks to two PCMCIA connectors.
Additional glue logic is used to multiplex these six OOB signals with Host address sig-
nals A4 to A9, as required by SCTE DVS 131. This implementation adds two static con-
trol signals OOBEN (activation control of OOB mode) and OOBSEL (selection of which
one of the 2 modules is connected to the OOB transceiver) that shall be directly driven
by the Host Processor and the CI Driver software stack
OOBEN OOBSEL Comment
0 0 OOB I/Os are not routed
0 1 OOB I/Os are not routed
1 0 OOB I/Os are routed to slot A
1 1 OOB I/Os are routed to slot B