EC168 support?!

EC168 support?!

[bloehei]

Hi,
I'm reading this list because I'm - like many others I guess - waiting for my 
EC168 based Sinovideo 3420b to be supported under linux. Now I've read this 
(https://www.dealextreme.com/forums/Default.dx/sku.8325~threadid.278942) post 
and was supprised that there already is some code that seems to be working 
for some other EC168 sticks. Sadly, it doesn't work for my device.
I want to thank Antti Palosaari for the work on the driver and suggest, that 
it should be communicated more clearly that there already is a code base for 
a driver.
Regards,
Jo

Re: EC168 support?!

[Antti Palosaari]

moi Jo!
bloehei wrote:
> Hi,
> I'm reading this list because I'm - like many others I guess - waiting for my 
> EC168 based Sinovideo 3420b to be supported under linux. Now I've read this 
> (https://www.dealextreme.com/forums/Default.dx/sku.8325~threadid.278942) post 
> and was supprised that there already is some code that seems to be working 
> for some other EC168 sticks. Sadly, it doesn't work for my device.
> I want to thank Antti Palosaari for the work on the driver and suggest, that 
> it should be communicated more clearly that there already is a code base for 
> a driver.

It is ugly few hour hack driver which I did when I tried to order Intel 
ce6230 based stick but got E3C ec168 one.
Anyhow, it seems to work with 8 MHz bandwidth. I think you have 6 or 7 
MHz? It is rather easy to add 6 and 7 too, just take usb-sniff and look 
registers programmed differently.
Are you using 6 or 7 MHz?

regards
Antti
-- 
http://palosaari.fi/

Re: EC168 support?!

[bloehei]

> moi Jo!
>
> bloehei wrote:
> > Hi,
> > I'm reading this list because I'm - like many others I guess - waiting
> > for my EC168 based Sinovideo 3420b to be supported under linux. Now I've
> > read this
> > (https://www.dealextreme.com/forums/Default.dx/sku.8325~threadid.278942)
> > post and was supprised that there already is some code that seems to be
> > working for some other EC168 sticks. Sadly, it doesn't work for my
> > device. I want to thank Antti Palosaari for the work on the driver and
> > suggest, that it should be communicated more clearly that there already
> > is a code base for a driver.
>
> It is ugly few hour hack driver which I did when I tried to order Intel
> ce6230 based stick but got E3C ec168 one.
> Anyhow, it seems to work with 8 MHz bandwidth. I think you have 6 or 7
> MHz? It is rather easy to add 6 and 7 too, just take usb-sniff and look
> registers programmed differently.
> Are you using 6 or 7 MHz?
>
> regards
> Antti

For me, the firmware doesn't get loaded, so I don't get that far. But I'm not 
posting because I expect this to be fixed for my stick now, I'm just happy 
that there is development going on at all, so that my device could be 
supported some day. I think it should be made known better, that there is 
some basic code, that's why I was posting.

If it is of interest, here's my system log:

> usb 1-1: new full speed USB device using uhci_hcd and address 2
> usb 1-1: configuration #1 chosen from 1 choice
> ec168_probe: interface:0
> ec168_identify_state:
> c0 01 00 00 01 00 01 00 <<< 00
> ec168_identify_state: reply:00
> dvb-usb: found a 'E3C EC168 DVB-T USB2.0 reference design' in cold state,
> will try to load a firmware usb 1-1: firmware: requesting dvb-usb-ec168.fw
> dvb-usb: downloading firmware from file 'dvb-usb-ec168.fw'
> ec168_download_firmware:
> 40 00 00 00 00 00 00 08 >>> 02 13 e4 02 0e d3 00 00 00 00 00 02 14 f7 00 00
> 00 <... cut ...>
> 40 00 00 00 40 08 00 08 >>> 12 0c 93 80 06 12 0d 43 74 83 f0 e5 48 30 e3 78
> 54 30 60 1d <... cut ...>
> 40 00 00 00 40 08 00 08 >>> 12 0c 93 80 06 12 0d 43 74 83 f0 e5 48 30 e3 78
> 54 30 60 1d 12 09 2d e0 12 0c 7f a3 f0 e5 48 <....cut....>
> 40 00 00 00 40 08 c5 03 >>> 12 0c 93 80 06 12 0d 43 74 83 f0 e5 48 30 e3 78
> 54 30 60 1d 12 09 2d e0 <...cut...>
> 40 01 00 00 01 00 00 00 >>>
> 40 04 01 00 08 00 00 00 >>>
> ec168_rw_udev: usb_control_msg failed :-75
> 40 04 00 00 06 02 00 00 >>>
> ec168_rw_udev: usb_control_msg failed :-71
> init failed :-71
> dvb_usb_ec168: probe of 1-1:1.0 failed with error -71
> ec168_probe: interface:1
> set interface failed
> ec168_identify_state:
> c0 01 00 00 01 00 01 00 <<< 00
> ec168_rw_udev: usb_control_msg failed :-71

If I can help with more informations or tests, just let me know.
Regards,
Jo

Re: EC168 support?!

[Antti Palosaari]

bloehei wrote:
>> 40 00 00 00 40 08 c5 03 >>> 12 0c 93 80 06 12 0d 43 74 83 f0 e5 48 30 e3 78
hmm, at least that last fw upload packet is wrong. It should look like
40 00 00 00 00 18 c5 03 >>> 49 9f f5

I did yesterday many changes and fixed one bad bug that could be behind 
that. Please test with latest tree at:
http://linuxtv.org/hg/~anttip/ec168/

regards
Antti
-- 
http://palosaari.fi/

Re: EC168 support?!

[bloehei]

> bloehei wrote:
> >> 40 00 00 00 40 08 c5 03 >>> 12 0c 93 80 06 12 0d 43 74 83 f0 e5 48 30 e3
> >> 78
>
> hmm, at least that last fw upload packet is wrong. It should look like
> 40 00 00 00 00 18 c5 03 >>> 49 9f f5
>
> I did yesterday many changes and fixed one bad bug that could be behind
> that. Please test with latest tree at:
> http://linuxtv.org/hg/~anttip/ec168/
>
> regards
> Antti

Hi,
GREAT! The firmware now gets uploaded and I can watch all channels in my 
region with the linux vdr. Thanks a lot! 
Here's my system log:

> ec168_module_init:
> usbcore: registered new interface driver dvb_usb_ec168
> usb 1-3: new high speed USB device using ehci_hcd and address 2
> usb 1-3: configuration #1 chosen from 1 choice
> ec168_probe: interface:0
> ec168_identify_state:
> c0 01 00 00 01 00 01 00 <<< 00
> ec168_identify_state: reply:00
> dvb-usb: found a 'E3C EC168 DVB-T USB2.0 reference design' in cold state,
> will try to load a firmware usb 1-3: firmware: requesting dvb-usb-ec168.fw
> dvb-usb: downloading firmware from file 'dvb-usb-ec168.fw'
> ec168_download_firmware:
> 40 00 00 00 00 00 00 08 >>> 02 13 e4 02 0e d3 00 00 00 00 00 02 14 f7 00 00
> 00 00 00 <---cut--->
> 40 00 00 00 00 08 00 08 >>> 4a 12 0c 5b 04 f0 02 08 4b 12 09 7f 12 0d 43 74
> 82 f0 12 <---cut--->
> 40 00 00 00 00 10 00 08 >>> 9d ec 98 40 05 fc ee 9d fe 0f d5 f0 e9 e4 ce fd
> 22 ed f8 <---cut--->
> 40 00 00 00 00 18 c5 03 >>> 49 9f f5 49 e5 48 94 00 f5 48 80 b3 e4 f5 24 f5
> 25 22 af <---cut--->
> 40 01 00 00 01 00 00 00 >>>
> 40 04 01 00 08 00 00 00 >>>
> ec168_rw_udev: usb_control_msg failed :-110
> 40 04 00 00 06 02 00 00 >>>
> dvb-usb: found a 'E3C EC168 DVB-T USB2.0 reference design' in warm state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer. DVB: registering new adapter (E3C EC168 DVB-T USB2.0 reference
> design) ec168_ec100_frontend_attach:
> DVB: registering adapter 0 frontend 0 (E3C EC100 DVB-T)...
> ec168_mxl5003s_tuner_attach:
> MXL5005S: Attached at address 0xc6
> dvb-usb: E3C EC168 DVB-T USB2.0 reference design successfully initialized
> and connected. ec168_probe: interface:1
> ec168_identify_state:
> c0 01 00 00 01 00 01 00 <<< 01
> ec168_identify_state: reply:01
> dvb-usb: found a 'E3C EC168 DVB-T USB2.0 reference design' in warm state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer. DVB: registering new adapter (E3C EC168 DVB-T USB2.0 reference
> design) ec168_ec100_frontend_attach:
> DVB: registering adapter 1 frontend 0 (E3C EC100 DVB-T)...
> ec168_mxl5003s_tuner_attach:
> MXL5005S: Attached at address 0xc6
> dvb-usb: E3C EC168 DVB-T USB2.0 reference design successfully initialized
> and connected.

USB-Id:  18b4:1689 
Card name: Sinovideo SV DVB-T 3420B

If I can help with testing, just let me know.

Regards,
Jo