Beiträge von raton_craquero

  • at what point is the CSA descrambling done?

    this is not clear from the linux dvb api, so i've done some tests and it appears that once the CSA keys are set to the proper PIDs in the CA device (CA_SET_DESCR to /dev/dvb/card0/ca0), those PIDS already appear descrambled when demuxing them from the frontend device. if that's the case, is there any way to use the CSA descrambler device on arbitrary user data (such a pre-recorded stream), instead of just descrambling what's coming through frontend?


    i hope i've made myself clear.

  • Help needed: Possible bug in DM7025 hardware demux drivers?

    i've stumbled across a very strange problem that, as far as i can tell, occurs only on the DM7025:


    Below is a dvbsnoop log of 1 raw ECM.


    the first ECM was captured in a DM7020 and the second one is *the same* ECM but captured on a DM7025 simultaneously (as you can see in the timestamps, they are a few seconds apart but they are the same ECM).


    Raw ECM captured on a DM7020



    Same raw ECM captured on a DM7025



    if you look closely, you'll see that the 6th byte of the ECM captured on the DM7025 gets corrupted. in this case the correct 6th byte is 0x99, but it's 0x88 in the DM7025 ECM.


    All other models (tested it on DM500/DM7000/DM7020) show consitently identical ECM's, except for the DM7025 which corrupts this byte *sporadically*.


    i've taken the time to observe the pattern of corruption and i've come to the following conclusion: whenever bits 8 and 7 of the byte are 1 and 0 respectively, bits 6 and 5 are always set to zero on the DM7025, here are some examples:


    Code
    DM7020		DM7025
(correct)	(corrupt)


0x98		0x88
0xA7		0x87
0xB0		0x80


    i've tried serveral tricks and workarounds, such as stoping and re-starting the demux filter on each ECM... adding timing delays after reading the demux output after starting it, skipping the first ECM's in the sequence and reading, say, the second or third... i've seen some improvement with some of these techniques (specially stopping and re-starting the demux filter on each ECM) but none have solved the problem.


    i'm at my wit's end and cannot see how this can be happening unless it's a hardware driver problem. i'm hoping someone has come across this problem and maybe know of a work-around for the situation.


    any help is appreciated, thanks.

  • Error building the DM7025 toolchain

    thanks for your help pcd, i deleted the object files but that didn't work, tried doing a clean also and no use, however i found the problem... turns out i didn't notice i was using gcc/g++ 3.3 ... since this is not the newest debian distribution...


    i upgraded to gcc/g++ 4.1 and the problem went away...


    thanks again

  • Error building the DM7025 toolchain

    Hi, i'm trying to build the DM7025 toolchain. I'm using the Makefile-opendreambox makefile.


    make -f Makefile-dreambox image


    i'm using GNU Debian 3.1 in x86 machine, monotone 0.31


    i'm getting an error while it's building/installing ipkg-native-0.99.163-r1


    here's the error:


    looking at the log at /dm7025/build/tmp/work/ipkg-native-0.99.163-r1/temp/log.do_in
    tall.14718, it contains the following:



    any suggestions? thanks.