Re: TT S2-3200 + CI Extension

[Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>]

Roger James wrote:

Werner Hauger wrote:

Hi Guys

What is the hardware revision of your CI board (printed on the bottom
of the PCB just above the PCI connector)?

I have a Rev 1.1 on my TT S2-3200 which requires polling, as well a
Rev 1.0 on an old NOVA-S card which provides an interrupt, both of
which work with the current driver. The version testing code was added
to the driver to handle these two boards. Maybe there is a new
revision out that the driver does not yet cater for.

A working CI and CAM combination should produce the following output
when the driver loads:

Linux video capture interface: v2.00
saa7146: register extension 'dvb'.
saa7146: register extension 'budget_ci dvb'.
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (level,
low) -> IRQ 5
saa7146: found saa7146 @ mem d8ae8000 (revision 1, irq 5) (0x13c2,0x1019).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (TT-Budget S2-3200 PCI)
adapter has MAC addr = 00:d0:5c:64:ba:14
input: Budget-CI dvb ir receiver saa7146 (0) as
/devices/pci0000:00/0000:00:09.0/input/input6
budget_ci: CI interface initialised
stb0899_get_dev_id: Device ID=[8], Release=[2]
stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1]
stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
stb0899_attach: Attaching STB0899
stb6100_attach: Attaching STB6100
dvb_ca adapter 0: DVB CAM detected and initialised successfully
DVB: registering frontend 0 (STB0899 Multistandard)...

  

508     if ((ci_version & 0xa0) != 0xa0) {
509             result = -ENODEV;
510             goto error;
511     }

      

Martin, have you tried commenting out this test to see if you then can
get the 'CI interface initialised' message?

  

Sorry I cannot offer any direct help. But I thought you might like to
know you are not the only one fighting with this piece of hardware :-)

Roger
    

Roger, in your other message you said your CI board reports the
version as 0xa0 which the driver expects to generate interrupts, which
clearly it doesn't. Have you tried changing the code so that the
driver uses polling for your CI version?

Werner

  

Werner,

Thank you for the suggestions. All help is gratefully received.

The board does generate interrupts for CAM insertion and removal. But I did try it with polling, no change. The flags coming back from the CI stay at 0x09 (CICONTROL_CAMDETECT_|CICONTROL_RESET), and the read of byte 0 of the atrribute memory returns 0x00 so the slot never goes into ready state. I will follow your suggestion and check out the board versions though!

I am waiting for the delivery an AstonCrypt CAM (I found one cheap one ebay) to see if that will initialise. As far as I can see, in my case the DEBI interface between the TT-3200 and the CI board is working, but I cannot ascertain if the CI interface on the daughter board is working properly or the CAM I am using (T.Rex/Dragon) is incompatible with the budget-ci driver. I know the Dragon CAM will work in TT-3200+CI installations on windows using the TT drivers because a number of people have reported success with it. The particular CAM I have also works with the CI emulator in my CAS-3 programmer so I don't think it is faulty.

In Martin's set up the DEBI interface may not be working as he does not see any difference if the CAM is present or not.

Do you ( or anyone) know of any source of information on the software interface to these boards? The guys who wrote the original code must have had some. Is Andrew de Quincey still active on the list?

Roger

Hooray,

I have got it working. I took out the TT3200 and the CI board to check their versions. Before putting them back in I cleaned and reseated the DEBI interface cable connections. Whilst I was playing with some more diagnostics I noticed I was getting back a 0x1d (CISTPL_DEVICE_OA) code from the call the read_attribute_memory in the call to ciintf_poll_status I had put into the "PC card not responding" path. I put back the change to use polling mode for firmware version 0xa0 that I had tried and failed with before, and lo and behold it all burst into life. Well at least it appears to have intiailised, whether it will decrypt is for another day.

Here is the dmesg output now for information.

saa7146: register extension 'budget_ci dvb'.
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
saa7146: found saa7146 @ mem e0a42000 (revision 1, irq 12) (0x13c2,0x1019).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (TT-Budget S2-3200 PCI)
adapter has MAC addr = 00:d0:5c:68:34:04
input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input9
budget_ci: Slot status d587c000 set to NONE 3 ci_version a0
budget_ci: Slot status d587c000 set to PRESENT
dvb_ca_en50221_init
budget_ci: CI interface initialised
dvb_ca_en50221_thread
budget_ci: Slot status d587c000 set to RESET
budget_ci: Slot status d587c000 set to READY
budget_ci: read_attribute 1d
TUPLE type:0x1d length:4
  0x00: 0x00 .
  0x01: 0x61 a
  0x02: 0x00 .
  0x03: 0xff .
TUPLE type:0x1c length:4
  0x00: 0x00 .
  0x01: 0xd3 .
  0x02: 0x00 .
  0x03: 0xff .
TUPLE type:0x15 length:27
  0x00: 0x05 .
  0x01: 0x00 .
  0x02: 0x54 T
  0x03: 0x2d -
  0x04: 0x52 R
  0x05: 0x45 E
  0x06: 0x58 X
  0x07: 0x58 X
  0x08: 0x00 .
  0x09: 0x54 T
  0x0a: 0x52 R
  0x0b: 0x45 E
  0x0c: 0x58 X
  0x0d: 0x20
  0x0e: 0x43 C
  0x0f: 0x41 A
  0x10: 0x4d M
  0x11: 0x00 .
  0x12: 0x52 R
  0x13: 0x45 E
  0x14: 0x56 V
  0x15: 0x00 .
  0x16: 0x32 2
  0x17: 0x2e .
  0x18: 0x32 2
  0x19: 0x00 .
  0x1a: 0xff .
TUPLE type:0x20 length:4
  0x00: 0xc9 .
  0x01: 0x02 .
  0x02: 0x01 .
  0x03: 0x01 .
TUPLE type:0x1a length:21
  0x00: 0x01 .
  0x01: 0x39 9
  0x02: 0x00 .
  0x03: 0x02 .
  0x04: 0x03 .
  0x05: 0xc0 .
  0x06: 0x0e .
  0x07: 0x41 A
  0x08: 0x02 .
  0x09: 0x44 D
  0x0a: 0x56 V
  0x0b: 0x42 B
  0x0c: 0x5f _
  0x0d: 0x43 C
  0x0e: 0x49 I
  0x0f: 0x5f _
  0x10: 0x56 V
  0x11: 0x31 1
  0x12: 0x2e .
  0x13: 0x30 0
  0x14: 0x30 0
TUPLE type:0x1b length:42
  0x00: 0xf9 .
  0x01: 0x04 .
  0x02: 0x09 .
  0x03: 0x7f .
  0x04: 0x55 U
  0x05: 0xcd .
  0x06: 0x19 .
  0x07: 0xd5 .
  0x08: 0x19 .
  0x09: 0x3d =
  0x0a: 0x9e .
  0x0b: 0x25 %
  0x0c: 0x26 &
  0x0d: 0x54 T
  0x0e: 0x22 "
  0x0f: 0xc0 .
  0x10: 0x09 .
  0x11: 0x44 D
  0x12: 0x56 V
  0x13: 0x42 B
  0x14: 0x5f _
  0x15: 0x48 H
  0x16: 0x4f O
  0x17: 0x53 S
  0x18: 0x54 T
  0x19: 0x00 .
  0x1a: 0xc1 .
  0x1b: 0x0e .
  0x1c: 0x44 D
  0x1d: 0x56 V
  0x1e: 0x42 B
  0x1f: 0x5f _
  0x20: 0x43 C
  0x21: 0x49 I
  0x22: 0x5f _
  0x23: 0x4d M
  0x24: 0x4f O
  0x25: 0x44 D
  0x26: 0x55 U
  0x27: 0x4c L
  0x28: 0x45 E
  0x29: 0x00 .
TUPLE type:0x14 length:0
END OF CHAIN TUPLE type:0xff
Valid DVB CAM detected MANID:2c9 DEVID:101 CONFIGBASE:0x200 CONFIGOPTION:0x39
dvb_ca_en50221_set_configoption
Set configoption 0x39, read configoption 0x39
DVB CAM validated successfully
dvb_ca_en50221_link_init
dvb_ca_en50221_wait_if_status
dvb_ca_en50221_wait_if_status succeeded timeout:0
dvb_ca_en50221_read_data
Received CA packet for slot 0 connection id 0x0 last_frag:0 size:0x2
Chosen link buffer size of 255
dvb_ca_en50221_wait_if_status
dvb_ca_en50221_wait_if_status succeeded timeout:0
dvb_ca_en50221_write_data
Wrote CA packet for slot 0, connection id 0x0 last_frag:0 size:0x2
dvb_ca adapter 0: DVB CAM detected and initialised successfully
stb0899_attach: Attaching STB0899
stb6100_attach: Attaching STB6100
DVB: registering frontend 0 (STB0899 Multistandard)...

Roger

_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb