[vdr] Re: CAM Aston 1.05 workaround

[Antonino Sergi <voyaser@tiscalinet.it>]

Is there anything I can do, study, learn to make this debugging?
I read CI specs...what else?

On Sat, 2003-08-02 at 15:39, Klaus Schmidinger wrote:
> Antonino Sergi wrote:
> > 
> > On Sat, 2003-07-26 at 15:28, Klaus Schmidinger wrote:
> > > Antonino Sergi wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm trying to understand why vdr can't make my CAM decrypt, when each
> > > > other operation (menu, getting CA_PMT....) works.
> > > >
> > > > I changed in cCiCaPmt::AddCaDescriptor CPCI_OK_DESCRAMBLING with
> > > > CPCI_QUERY to see if my CAM was able to understand the TPDU and answer
> > > > if descrambling was possible or not or whatever:
> > > > here there is the log for an encrypted channel
> > > >
> > > > --> 00 01 A0 32 01 90 02 00 03 9F 80 32 29 03 2D B9 01 00 14 03 09 11 01
> > > > 00 E5 20 00 70 FF 10 00 00 08 00 10 00 06 1A F4 00 00 A2 00 00 00 00 58
> > > > 00 00 00 00 59 00 00
> > > > <-- 00 01 80 02 01 00
> > > >     .  .  .  .  .  .
> > > > --> 00 01 A0 01 01
> > > > <-- 00 01 80 02 01 80
> > > >     .  .  .  .  .  .
> > > > --> 00 01 81 01 01
> > > > <-- 00 01 A0 82 00 10 01 90 02 00 03 9F 80 33 07 2D B9 01 81 00 08 00 80
> > > > 02 01 00
> > > >     .  .  .  .  .  .  .  .  .  .  .  .  .  3  .  -  .  .  .  .  .  .  .
> > > > .  .  .
> > > >
> > > > Because 2D B9 is the service id, if I understand correctly the Ci
> > > > specifications EN 50221, 01 81 after service ID means:
> > > > current_next_indicator set to 1
> > > > CA_enable_flag set to 1
> > > > CA_enable set to 01 (Descrambling Possible)
> > > >
> > > > But I have (reverting to the original source code:CPCI_OK_DESCRAMBLING)
> > > > no image and no sound.
> > > >
> > > > There is 1 thing that sounds strange (if what I have said is correct):
> > > > If I tune another encrypted channel I have no right to watch, I always
> > > > get 01 81 as before: this must imply I said something wrong...but what?
> > > >
> > > > I really do not know!
> > > >
> > > > Any idea?
> > >
> > > It's hard to tell what's going on without having the CAM here to test.
> > 
> > I can try to make any test for you; just tell me what
> 
> >From my experience with debugging the CiMAX problem I can say that
> it is almost impossible to remote-debug this stuff. You have to run
> tests, make changes, see what happens...
> 
> > > Can you try the driver with the '-icam' firmware (see DVB/driver/av7110/README-firmware)
> > > to see whether it works there?
> > >
> > > Also, make sure you use the latest DVB driver from CVS, because it contains a fixed
> > > firmware which now also works with CiMAX 2.0 chips.
> > >
> > > Klaus
> > 
> > I cvs co yesterday and I tried the '-icam' firmware but I get an error;
> > I had no time to try to understatnd why, maybe you know.
> > 
> > Jul 29 05:50:44 desktop kernel: Linux video capture interface: v1.00
> > Jul 29 05:50:48 desktop kernel: DVB: registering new adapter
> > (Technotrend/Hauppauge PCI rev2.1 or 2.2).
> > Jul 29 05:50:48 desktop kernel: PCI: Found IRQ 11 for device 00:09.0
> > Jul 29 05:50:50 desktop kernel: stv0299.c: setup for tuner BSRU6,
> > TDQB-S00x
> > Jul 29 05:50:50 desktop kernel: DVB: registering frontend 0:0
> > (STV0299/TSA5059/SL1935 based)...
> > Jul 29 05:50:52 desktop kernel: mt312_read: ret == -121
> > Jul 29 05:50:54 desktop kernel: DVB: AV7111(0) - firm f0240009, rtsl
> > b0250018, vid 71010068, app 0000261a
> > Jul 29 05:50:54 desktop kernel: DVB: AV7111(0) - no firmware support for
> > CI link layer interface
> > Jul 29 05:50:55 desktop kernel: OutCommand: timeout waiting for COMMAND
> > idle
> > Jul 29 05:50:55 desktop kernel: SOutCommand error
> > Jul 29 05:50:55 desktop kernel: outcom error
> 
> Looks like an ARM problem. I don't know whether that has anyting to
> do with your CAM not working. Just try again, maybe it's just temporary...
> 
> Klaus
-- 
Antonino Sergi <voyaser@tiscalinet.it>
Evolution Enterprises



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.