[linux-dvb] m920x device: Genius TVGo DVB-T02Q

Pere Blay pereblay at gmail.com
Fri Jun 15 08:23:34 CEST 2007


Hi,

At last i could get the firmware... I used Snoopypro in a computers
friend and later on at min  (with wine) in order to dump everything to
text

With the heap of logs that snoopypro kindly supplied me in some
ocassions i got an empty firmware and in some others a firmware with
size 1.1Kb, in all cases where i get a 1.1Kb firmware the command diff
told me that there are no differences between them... but i still
onder if it's the right firmware... is there some way to test it? I
send it attached (file named 'fw_v2'...)


when i use this firmware (in my system i named it like this:
'dvb-usb-t02q-2.fw'... don't ask me why this name, i just did it),
this is what i get from dmesg after plugging the device:

[50684.256000] usb 2-3: new high speed USB device using ehci_hcd and address 8
[50684.400000] usb 2-3: configuration #1 chosen from 1 choice
[50684.528000] dvb-usb: found a 'Genius TVGo DVB-T02Q' in cold state,
will try to load a firmware
[50684.544000] dvb-usb: downloading firmware from file 'dvb-usb-t02q-02.fw'
[50684.744000] usbcore: registered new interface driver dvb_usb_m920x
[50684.764000] usb 2-3: USB disconnect, address 8

The usb  dwarves of my kernel disconnect the device after loading the
driver, but the drivers is not unloaded it will reamin in my system
for ages if i didn't 'modprobe -r'

Of cource, i could not get output from 'lsusb' as the device gets
disconnected inmediately...

But... :O to my surprise this is what i found when i used a Megasky
firmware i found somewhere in the internet (dvb-usb-megasky-02.fw):

[51875.632000] usb 2-3: new high speed USB device using ehci_hcd and address 12
[51875.772000] usb 2-3: configuration #1 chosen from 1 choice
[51875.776000] dvb-usb: found a 'MSI Mega Sky 580 DVB-T USB2.0' in warm state.
[51875.776000] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[51875.776000] DVB: registering new adapter (MSI Mega Sky 580 DVB-T USB2.0).
[51876.012000] dvb-usb: no frontend was attached by 'MSI Mega Sky 580
DVB-T USB2.0'
[51876.012000] input: IR-receiver inside an USB DVB receiver as
/class/input/input9
[51876.012000] dvb-usb: schedule remote query interval to 100 msecs.
[51876.012000] dvb-usb: MSI Mega Sky 580 DVB-T USB2.0 successfully
initialized and connected.


Now the mt352 frontend is loaded, see in lsmod output:

mt352                   7556  0
dvb_usb_m920x          20484  0
dvb_usb                24972  1 dvb_usb_m920x
dvb_core               80808  1 dvb_usb
dvb_pll                15620  1 dvb_usb
i2c_core               22784  5 mt352,dvb_usb,dvb_pll,i2c_ec,i2c_nforce2
usbcore               134280  7
dvb_usb_m920x,dvb_usb,ndiswrapper,usbhid,ehci_hcd,ohci_hcd


and the /dev files are created:

/dev/dvb/adapter0/demux0  /dev/dvb/adapter0/dvr0  /dev/dvb/adapter0/net0

The 'lsusb -v' output is attached in a plain text file.

If i unplug the device i get this message:

[52963.688000] usb 2-3: USB disconnect, address 12
[52963.688000] dvb-usb: MSI Mega Sky 580 DVB-T USB2.0 successfully
deinitialized and disconnected.

But the drivers still have to be unloaded with 'modprobe -r'

I hope this all is usefull... willling to keep testing and trying!

Cheers,
Pere Blay



2007/6/11, Aapo Tahkola <aet at rasterburn.org>:
> On Fri, 8 Jun 2007 17:35:27 +0200
> "Pere Blay" <pereblay at gmail.com> wrote:
>
> > Hi!
> >
> > I recently purchased a Genius TVGo DVB-T02Q, a usb dvb-t device
> >
> >  i found in this mail list that this device belongs to the m920x
> > family. The
> >
> > windows INF file makes reference to the m9207 chip, as frontends,
> > someone pointed out in this mail list that it has got inside a
> > Zarlink ZL10353 and MT2060 chipsets, the windows INF file also makes
> > reference to QT1010 and MT352...
> >
> > I took a patch i also located in this mail list, but had to modify it
> > a bit to
> > make it up-to-date with the current mercury m920x branch of the
> > v4l-dvb project,... after modification i applied this patch to m920.c
> > file, i send attached the modified m920.c file.
> >
> > As a result i found out that the device is recognised by the system,
> > as stated
> > in the dmesg output:
> >
> > [  125.352000] usb 2-3: new high speed USB device using ehci_hcd and
> > address 4
> > [  125.496000] usb 2-3: configuration #1 chosen from 1 choice
> > [  125.700000] dvb-usb: found a 'Genius TVGo DVB-T02Q' in cold state,
> > will try
> >                                        to load a firmware
> > [  125.808000] dvb-usb: downloading firmware from file
> > 'dvb-usb-t02q-02.fw' [  125.812000] usbcore: registered new interface
> > driver dvb_usb_m920x
> >
> >
> > but the device did not work and the frontends were not loaded, here
> > you are the related modules automatically loaded when the usb device
> > is connected.
>
> It is unlikely you can use other device's firmware.
> See http://www.linuxtv.org/wiki/index.php/M920x_firmware on how to
> retrieve new firmware.
>
> Please include output from "lsusb -v" after firmware has been loaded.
> Once you have gotten m920x driver to load properly, you need to get
> some dumps so that we can identify which tuner you have. They are also
> important when adding support for mt2060 tuner to m920x. It might work
> out of the box if you have qt1010.
>
> Please post you changes as diffs. You can get one with command
> "hg diff" or with "diff -uNr original_dir modified_dir" .
>
> "
> >
> >
> > Module                  Size  Used by
> > dvb_usb_m920x          20484  0
> > dvb_usb                24972  1 dvb_usb_m920x
> > dvb_core               80808  1 dvb_usb
> > dvb_pll                15620  1 dvb_usb
> >
> > I think the patch only gets the device recognized but is not
> > configured properly to detect and load the frontends... if I unplug
> > the devive the modules won't be removed
> >
> > I'm wokring witha a 2.6.20-15 kernel in a kubuntu system.
> >
> > I'm willing to make this device work and help in the m920x branch,
> > i'm quite
> >
> > newbie in programming and then i will need some indications on how to
> > debuge
> >
> > to get more output from the code or how to try to 'communicate' with
> > the device (send it stuff and see what comes back).
> >
> > If anyone else has got some experience with this device, every
> > comment, suggestion are very wellcome (appart of giving it back and
> > buy a new one ;)... i'm very stubborn and won't stop trying untill i
> > get this one working)
>
> Great attitude!
> Once you got the proper firmware you can find out what codes have they
> used for your remote controller(assuming you have one). You can do this
> by printing(use printk) contents of rc_state[0] and rc_state[1] in
> function m920x_rc_query. This function gets called often so you want to
> only print output if hw registers key as pressed.
>
> --
> Aapo Tahkola
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fw_v2
Type: application/octet-stream
Size: 1120 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070615/68224fd9/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lsusb.output.with.mgsk.fw
Type: application/octet-stream
Size: 2709 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20070615/68224fd9/attachment-0003.obj 


More information about the linux-dvb mailing list