Smart Plus: Difference between revisions
Jump to navigation
Jump to search
m (Fixed a link) |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Image:Smart Plus device.jpg|right|thumb|200px|Labeled as Smart Plus. Has an antenna connector at the back.]] |
|||
TODO: Upload another image |
|||
[[Image:Kworld_ATSC_115_front.jpg|right|thumb|200px|Example Image: Add a good overall image of what the device looks like here and perhaps a very brief description]] |
|||
An [[ISDB-T USB Devices|ISDB-T USB Device]] [[Siano]] Chipset. |
An [[ISDB-T USB Devices|ISDB-T USB Device]] [[Siano]] Chipset. |
||
The Smart Plus device |
The Smart Plus device is also called USV926 or even YS-926TV. |
||
It has been tested under Linux kernel 3.1.8, and does not work. |
|||
| Line 14: | Line 14: | ||
===Components Used=== |
===Components Used=== |
||
* Siano Mobile Silicon (according to Linux kernel) |
|||
* USB 2.0 ISDB-T Stick, model UTV926 (according to the manual) |
* USB 2.0 ISDB-T Stick, model UTV926 (according to the manual) |
||
* The chip is labeled as: Siano Mobile Silicon SMS1140 G3B086.1 D0 E39305 A0 1024 S |
|||
===Other Images=== |
===Other Images=== |
||
''Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:''<br> |
|||
TODO: add more images |
|||
<gallery perrow=5> |
<gallery perrow=5> |
||
Image: |
Image:Smart Plus box.jpg|Smart Plus box |
||
Image: |
Image:Smart Plus box contents.jpg|Smart Plus box contents |
||
Image:Smart Plus CD.jpg|Smart Plus CD |
|||
Image:Smart Plus circuit top.jpg|Smart Plus circuit top |
|||
Image:Smart Plus circuit bottom.jpg|Smart Plus circuit bottom |
|||
</gallery> |
</gallery> |
||
| Line 101: | Line 100: | ||
==Making it Work== |
==Making it Work== |
||
I could not make it work. No device is created at ''/dev/dvb/*'', even after the driver uploads the firmware. Maybe it is the wrong driver, or it does not work with this device. |
|||
I make a diffrent brand, same chipset work by **manually** loading the smsdvb kernel module (# modprobe smsdvb). Then the dvb device is configured successfully[[User:Vdragon|...(Vdragon)]] 02:40, 31 December 2012 (CET) |
|||
===Firmware=== |
===Firmware=== |
||
The Windows driver will install the firmware at ''C:\Windows\system32\drivers\isdbt_nova_12mhz_b0.inp''. You can copy and use this file to your linux firmware folder (ex. /lib/firmware). |
The Windows driver will install the firmware at ''C:\Windows\system32\drivers\isdbt_nova_12mhz_b0.inp''. You can copy and use this file to your linux firmware folder (ex. /lib/firmware). |
||
However, the driver from 2.6.38 |
However, the driver from 2.6.38 and 3.1.8 kernels looks for the firmware named ''dvb_nova_12mhz_b0.inp'', so you must either rename the firmware file, or create a symlink. |
||
===Drivers=== |
===Drivers=== |
||
Both ''SMS_SIANO_MDTV'' and ''SMS_USB_DRV'' are required. They are already available in Linux kernel |
Both ''SMS_SIANO_MDTV'' and ''SMS_USB_DRV'' are required. They are already available in main Linux kernel. |
||
===Sample Kernel Output=== |
===Sample Kernel Output=== |
||
<pre> |
<pre> |
||
# dmesg |
# dmesg |
||
[ |
[ 174.346772] usb 2-4: new high speed USB device number 5 using ehci_hcd |
||
[ |
[ 174.470852] usb 2-4: New USB device found, idVendor=187f, idProduct=0202 |
||
[ |
[ 174.470860] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 |
||
[ |
[ 174.470866] usb 2-4: Product: MDTV Receiver |
||
[ |
[ 174.470871] usb 2-4: Manufacturer: MDTV Receiver |
||
[ |
[ 175.190058] smscore_set_device_mode: firmware download success: dvb_nova_12mhz_b0.inp |
||
[ 175.190325] usbcore: registered new interface driver smsusb |
|||
</pre> |
</pre> |
||
Latest revision as of 22:17, 1 July 2013
An ISDB-T USB Device Siano Chipset.
The Smart Plus device is also called USV926 or even YS-926TV.
It has been tested under Linux kernel 3.1.8, and does not work.
Overview/Features
- USB interface
- Inputs: Antenna, Remote
Components Used
- USB 2.0 ISDB-T Stick, model UTV926 (according to the manual)
- The chip is labeled as: Siano Mobile Silicon SMS1140 G3B086.1 D0 E39305 A0 1024 S
Other Images
Smart Plus box
Smart Plus box contents
Smart Plus CD
Smart Plus circuit top
Smart Plus circuit bottom
Identification
# lsusb -v
Bus 002 Device 007: ID 187f:0202 Siano Mobile Silicon Nice
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x187f Siano Mobile Silicon
idProduct 0x0202 Nice
bcdDevice 0.06
iManufacturer 1 MDTV Receiver
iProduct 2 MDTV Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Making it Work
I could not make it work. No device is created at /dev/dvb/*, even after the driver uploads the firmware. Maybe it is the wrong driver, or it does not work with this device.
I make a diffrent brand, same chipset work by **manually** loading the smsdvb kernel module (# modprobe smsdvb). Then the dvb device is configured successfully...(Vdragon) 02:40, 31 December 2012 (CET)
Firmware
The Windows driver will install the firmware at C:\Windows\system32\drivers\isdbt_nova_12mhz_b0.inp. You can copy and use this file to your linux firmware folder (ex. /lib/firmware).
However, the driver from 2.6.38 and 3.1.8 kernels looks for the firmware named dvb_nova_12mhz_b0.inp, so you must either rename the firmware file, or create a symlink.
Drivers
Both SMS_SIANO_MDTV and SMS_USB_DRV are required. They are already available in main Linux kernel.
Sample Kernel Output
# dmesg [ 174.346772] usb 2-4: new high speed USB device number 5 using ehci_hcd [ 174.470852] usb 2-4: New USB device found, idVendor=187f, idProduct=0202 [ 174.470860] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 174.470866] usb 2-4: Product: MDTV Receiver [ 174.470871] usb 2-4: Manufacturer: MDTV Receiver [ 175.190058] smscore_set_device_mode: firmware download success: dvb_nova_12mhz_b0.inp [ 175.190325] usbcore: registered new interface driver smsusb
Remote Control Support
Not tested.