Difference between revisions of "Asus U3100 Mini plus DVB-T"

From LinuxTVWiki
Jump to: navigation, search
 
(21 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This is just some thoughts and rambling about the Asus U3100 based on the AF9035 instead of the previous DiB models.
+
There is now kernel support for the demodulator and the USB bridge (af9035 chip) and for the tuner (FC2580).
  
[[EzCap_DVB_T_Stick]] is the guide to be followed to get this stick working. Read both articles thoroughly and it should be able to get it working.
+
Glue code to support the Asus U3100 Mini plus has now landed in the current staging tree and has been pull-requested for 3.7.
  
A [http://www.ubuntu-hr.org/forum/index.php?topic=5668.0 hungarian forum post]. They link an [http://www.linux-cam.com/downloads/MiniTV_For_Linux.rar archive] with an installer in it.
+
http://git.linuxtv.org/media_tree.git/tree/staging/for_v3.7
  
When running the shell script in this archive, setup is called which extracts data to /tmp. If the setup is canceled in any way, the temporary directory gets removed. Whats interesting is, that in this directory, is the full source for various tuners and for the af9035.
 
  
To get the Asus U3100 working with this source package, a few things need to be modified. Firstly, there is a syntax error. The defines (commented):
+
{{Device List Full Detail/Header
<pre>#define CRYSTAL_19.2_MHZ
+
| content =
#define CRYSTAL_20.48_MHZ</pre>
+
{{USB_Device_Data|renderwith=Device_List_Full_Detail/Row
cannot have dots in them. Remove the dots with a find and replace to something without one, such like:
+
|selatt1=did
<pre>#define CRYSTAL_19_MHZ
+
|selval1=asus-my-cinema-u3100-mini-plus}}
#define CRYSTAL_20_MHZ</pre>
+
}}
  
Then the USB ID for the U3100plus needs to be added to the kernels in drivers/media/dvb/dvb-usb/dvb-usb-ids.h
+
Image of the tuner and USB Bridge/Demodulator.
Such like:
+
[[image:Asus_U3100_Mini_plus_DVB-T_02.JPG|120px]] [[image:Asus_U3100_Mini_plus_DVB-T_03.JPG|120px]]
<pre>
+
#define USB_PID_ASUS_U3100MINI                  0x1779
+
</pre>
+
  
Then, the af903x driver needs to be told about this ID. This is done in af903x-devices.c
+
Image of the other side of the V2
Find the struct af903x_usb_id_table and add the ID's:
+
[[image:Dvb-t_asus_u3100mini_plus_v2_2.JPG|120px]]
<pre>
+
struct usb_device_id af903x_usb_id_table[] = {
+
                { USB_DEVICE(0x15A4,0x1000) },
+
                { USB_DEVICE(0x15A4,0x1001) },
+
                { USB_DEVICE(0x15A4,0x1002) },
+
                { USB_DEVICE(0x15A4,0x1003) },
+
                { USB_DEVICE(0x15A4,0x9035) },
+
                { USB_DEVICE(USB_VID_ASUS, USB_PID_ASUS_U3100MINI) },
+
                { 0},          /* Terminating entry */
+
};
+
</pre>
+
And finally, add the struct to the device section listing the devices.
+
<pre>
+
                .num_device_descs =1,
+
                .devices =  {
+
                        {      "ITEtech USB2.0 DVB-T Recevier",
+
                                { &af903x_usb_id_table[0], &af903x_usb_id_table[1],&af903x_usb_id_table[2],
+
                                &af903x_usb_id_table[3], &af903x_usb_id_table[4], &af903x_usb_id_table[5], NULL},
+
                                { NULL },
+
                        },
+
                        {NULL},
+
  
                }
+
USB Quircks should no longer be needed for this device. For the time being still listed here.
</pre>
+
&af903x_usb_id_table[5], is all that has been added. I guess a second device section can be added to have the U3100plus identified separably, I'll update after I got the device working :)
+
 
+
USB Quircks are also needed for this device.
+
 
<pre>options usbhid quirks=0x0b05:0x1779:0x0004</pre>
 
<pre>options usbhid quirks=0x0b05:0x1779:0x0004</pre>
 +
 +
The original rare drivers v9.08.14.1 had been uploaded to http://ubuntuforums.org/showpost.php?p=10176778&postcount=20
 +
 +
Compiling v9.08.14.1 may be very adventurous. I have made some pathology to original driver :) and reduce it only to ASUS_U3100_mini device and fix various incompatibilities. Minimum additional modification are needed to installing. Works well for kernel < 2.6.35.
 +
 +
This old driver currently still lives in my git repository for the [http://git.schinagl.nl/AF903x_SRC.git AF903x] and keep pushing changes I receive until 3.7 is released.
 +
 +
'''09.07.2013'''
 +
The device does not seem to work.
 +
Seems to be a problem with I2C communication between frontend and tuner.
 +
The error is
 +
dvb_usb_v2: 'Asus U3100Mini Plus' error while loading driver (-19)
 +
dvb_usb_v2: 'Asus U3100Mini Plus' successfully deinitialized and disconnected
 +
 +
'''19.07.2013'''
 +
Ubuntu 13.04, kernel 3.11.0-999-generic #201307180423 x86_64, firmware http://palosaari.fi/linux/v4l-dvb/firmware/af9035/dvb-usb-af9035-02.fw_f71efe295151ba76cac2280680b69f3f_11.5.9.0_5.17.9.1.
 +
In circa 1 case of 50 is the device successfully identified by i2c and working:
 +
Jul 18 22:08:22 thinkpad kernel: [ 2249.356481] i2c i2c-6: af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1
 +
Jul 18 22:08:22 thinkpad kernel: [ 2249.360331] usb 1-1: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
 +
Jul 18 22:08:22 thinkpad kernel: [ 2249.412901] i2c i2c-6: fc2580: FCI FC2580 successfully identified
 +
Jul 18 22:08:22 thinkpad kernel: [ 2249.424688] usb 1-1: dvb_usb_v2: 'Asus U3100Mini Plus' successfully initialized and connected
 +
 +
Otherwise it throws the "error while loading driver (-19)" mention above. Full part of syslog and file contents I have collected from /sys/bus/i2c/devices/i2c-6/device/ for debugging can be found here: http://ubuntuone.com/5u0sfwtb2HZihFScRGsaPR .
 +
 +
--[[User:SignElSoft|SignElSoft]] 22:04, 20 February 2014 (CET)<br>
 +
I have seen the same problem.<br>
 +
I have made a little change on the /usr/src/linux/drivers/media/tuners/fc2580.c file, and compiled a new fc2580.ko module, and it works fine.
 +
<br><br>
 +
struct dvb_frontend *fc2580_attach(struct dvb_frontend *fe,
 +
struct i2c_adapter *i2c, const struct fc2580_config *cfg)<br>
 +
{<br>
 +
...<br>
 +
<br>
 +
 +
/* check if the tuner is there */<br>
 +
ret = fc2580_rd_reg(priv, 0x01, &chip_id);<br>
 +
/* *************** COMMENT OUT THIS PART *****************************<br>
 +
if (ret < 0)<br>
 +
goto err;<br>
 +
<br>
 +
dev_dbg(&priv->i2c->dev, "%s: chip_id=%02x\n", __func__, chip_id);<br>
 +
<br>
 +
switch (chip_id) {<br>
 +
case 0x56:<br>
 +
case 0x5a:<br>
 +
break;<br>
 +
default:<br>
 +
goto err;<br>
 +
}<br>
 +
*/<br>
 +
...<br>

Latest revision as of 21:04, 20 February 2014

There is now kernel support for the demodulator and the USB bridge (af9035 chip) and for the tuner (FC2580).

Glue code to support the Asus U3100 Mini plus has now landed in the current staging tree and has been pull-requested for 3.7.

http://git.linuxtv.org/media_tree.git/tree/staging/for_v3.7


did vendor device standard supported pic url hostinterface usbid hw tuner demodulator usbbridge fw comment E
asus-my-cinema-u3100-mini-plus ASUS My Cinema U3100 Mini Plus DVBT Tuner DVB-T Yes, Yes, in kernel since 3.7 Asus U3100 Mini plus DVB-T 01.JPG [1] USB2.0 0b05:1779 Afatech AF9035 FCI2580 af9033 af9035 [2] There's an older device by almost the same name (without the "plus"), which is dib7xxx based and works out of the box. Jump to the place where you can edit this entry
asus-my-cinema-u3100-mini-plus-v2 ASUS My Cinema U3100 Mini Plus V2 DVB-T Yes Dvb-t asus u3100mini plus v2.JPG [3] USB2.0 1b80:d393 Afatech DVB-T receiver [RTL2832U] Jump to the place where you can edit this entry

Image of the tuner and USB Bridge/Demodulator. Asus U3100 Mini plus DVB-T 02.JPG Asus U3100 Mini plus DVB-T 03.JPG

Image of the other side of the V2 Dvb-t asus u3100mini plus v2 2.JPG

USB Quircks should no longer be needed for this device. For the time being still listed here.

options usbhid quirks=0x0b05:0x1779:0x0004

The original rare drivers v9.08.14.1 had been uploaded to http://ubuntuforums.org/showpost.php?p=10176778&postcount=20

Compiling v9.08.14.1 may be very adventurous. I have made some pathology to original driver :) and reduce it only to ASUS_U3100_mini device and fix various incompatibilities. Minimum additional modification are needed to installing. Works well for kernel < 2.6.35.

This old driver currently still lives in my git repository for the AF903x and keep pushing changes I receive until 3.7 is released.

09.07.2013 The device does not seem to work. Seems to be a problem with I2C communication between frontend and tuner. The error is

dvb_usb_v2: 'Asus U3100Mini Plus' error while loading driver (-19)
dvb_usb_v2: 'Asus U3100Mini Plus' successfully deinitialized and disconnected

19.07.2013 Ubuntu 13.04, kernel 3.11.0-999-generic #201307180423 x86_64, firmware http://palosaari.fi/linux/v4l-dvb/firmware/af9035/dvb-usb-af9035-02.fw_f71efe295151ba76cac2280680b69f3f_11.5.9.0_5.17.9.1. In circa 1 case of 50 is the device successfully identified by i2c and working:

Jul 18 22:08:22 thinkpad kernel: [ 2249.356481] i2c i2c-6: af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1
Jul 18 22:08:22 thinkpad kernel: [ 2249.360331] usb 1-1: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
Jul 18 22:08:22 thinkpad kernel: [ 2249.412901] i2c i2c-6: fc2580: FCI FC2580 successfully identified
Jul 18 22:08:22 thinkpad kernel: [ 2249.424688] usb 1-1: dvb_usb_v2: 'Asus U3100Mini Plus' successfully initialized and connected

Otherwise it throws the "error while loading driver (-19)" mention above. Full part of syslog and file contents I have collected from /sys/bus/i2c/devices/i2c-6/device/ for debugging can be found here: http://ubuntuone.com/5u0sfwtb2HZihFScRGsaPR .

--SignElSoft 22:04, 20 February 2014 (CET)
I have seen the same problem.
I have made a little change on the /usr/src/linux/drivers/media/tuners/fc2580.c file, and compiled a new fc2580.ko module, and it works fine.

struct dvb_frontend *fc2580_attach(struct dvb_frontend *fe, struct i2c_adapter *i2c, const struct fc2580_config *cfg)
{
...

/* check if the tuner is there */
ret = fc2580_rd_reg(priv, 0x01, &chip_id);
/* *************** COMMENT OUT THIS PART *****************************
if (ret < 0)
goto err;

dev_dbg(&priv->i2c->dev, "%s: chip_id=%02x\n", __func__, chip_id);

switch (chip_id) {
case 0x56:
case 0x5a:
break;
default:
goto err;
}

*/

...