[linux-dvb] DiBcom 3000P clone device

Florin Mihut mihut at t-online.de
Thu Jun 22 00:41:25 CEST 2006


Hi Patrick,

    It is exactly what I have done before.
    I changed the dibusb-mc.c and dvb-usb-ids.h by adding the usb-ids
there. In dibusb-mc.c I added a new entry in the table to match my
defined IDs.

    Now, to be sure, I changed the value of USB_VID_DIBCOM to 0x1584 and
the values of USB_PID_DIBCOM_MOD3001_COLD / USB_PID_DIBCOM_MOD3001_WARM
to 0x60ff / 0x6000. I know is bad and stupid but I wanted just to be
sure that I did not made a mistake before. The same result - everything
looks ok, but the w_scan won't find a thing:

[17179765.004000] usb 3-2: new high speed USB device using ehci_hcd and
address 6
[17179765.136000] dvb-usb: found a 'DiBcom USB2.0 DVB-T reference design
(MOD3000P)' in cold state, will try to load a firmware
[17179765.208000] dvb-usb: downloading firmware from file
'dvb-usb-dibusb-6.0.0.8.fw'
[17179765.268000] usb 3-2: USB disconnect, address 6
[17179765.268000] dvb-usb: generic DVB-USB module successfully
deinitialized and disconnected.
[17179767.272000] usb 3-2: new high speed USB device using ehci_hcd and
address 7
[17179767.416000] dvb-usb: found a 'DiBcom USB2.0 DVB-T reference design
(MOD3000P)' in warm state.
[17179767.416000] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[17179767.424000] DVB: registering new adapter (DiBcom USB2.0 DVB-T
reference design (MOD3000P)).
[17179767.424000] dib3000: Found a DiBcom 3000P.
[17179767.428000] DVB: registering frontend 1 (DiBcom 3000P/M-C
DVB-T)...
[17179767.428000] input: IR-receiver inside an USB DVB receiver
as /class/input/input4
[17179767.428000] dvb-usb: schedule remote query interval to 150 msecs.
[17179767.428000] dvb-usb: DiBcom USB2.0 DVB-T reference design
(MOD3000P) successfully initialized and connected.

The same behavior the LED is turned on for like a second (it looks like
the fw is downloaded there), then is turned off again. Can be that this
device requires a special fw? If you thing will help I can try to
"extract" the fw the win SYS files, if provided with the information how
to do it.

However I did not understood what you mean by v4l-dvb.stk3000p ... I
just grep'ed for STK and I found an unused define
USB_PID_DIBCOM_STK7700. ????

Another short question ... if my device has been identified from kernel
and the respective drivers have been loaded, shouldn't the device name
be visible in the lsusb?

Cold:
Bus 003 Device 007: ID 1584:60ff
Warm
Bus 003 Device 007: ID 1584:6000

But no name is present there, is this ok?

Anyway I thank you very much,
Gruss,
Florin

On Sun, 2006-06-18 at 15:35 +0200, Patrick Boettcher wrote:

> Hi Florian,
> 
> Can you try this device with v4l-dvb.stk3000p (by adding the usb-ids to 
> dibusb-mc.c)?
> 
> regards,
> Patrick.
> 
> --
>   Mail: patrick.boettcher at desy.de
>   WWW:  http://www.wi-bw.tfh-wildau.de/~pboettch/
> 
> On Fri, 9 Jun 2006, Florin Mihut wrote:
> 
> > Hi,
> > 
> > 	Thank you for your attention and your support!
> > 
> > cold state - lsusb output:
> > Bus 004 Device 004: ID 08ec:0015 M-Systems Flash Disk Pioneers 
> > Bus 004 Device 002: ID 1584:60ff  
> > Bus 004 Device 001: ID 0000:0000  
> > Bus 001 Device 001: ID 0000:0000  
> > Bus 003 Device 001: ID 0000:0000  
> > Bus 002 Device 001: ID 0000:0000  
> > 
> > 
> > I attached 2 photos and the INF files. On the second chip I could not
> > read the indications. It is a DibCom, a Dib3000-P device. The question
> > is why it is not working ... :)
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxtv.org/pipermail/linux-dvb/attachments/20060622/9ea07fdb/attachment-0001.htm


More information about the linux-dvb mailing list