RTL2832U + R820T bulk DTV stick teardownThat stick is Realtek RTL2832U reference design with Rafael Micro R820T RF tuner . USB ID is 0bda:2832, which is chipset default reference design ID. Why there is still eeprom?
Linux support has been added since the Kernel 3.10.
unbranded RTL2832U + R820T
|unbranded RTL2832U + R820T stick|
Key components:Realtek RTL2832U
Rafael Micro R820T
|RTL2832U + R820T stick PCB|
All components are assembled to that side of the PCB. Very standard RTL2832U stuff with nothing extra. Main components from left to right are: power LED, IR-receiver, MCX antenna connector, A7 - BAV99 diode, R820T RF tuner, 28.800 MHz crystal, 24C02 serial eeprom, RTL2832U DVB-T USB interface + demodulator, FS1117 voltage regulator and type A USB connector.
28.800 MHz clock is shared with RTL2832U and R820T - saving one component. BAV99 diode is used for ESD protection. It protects RF tuner possible ESD coming from antenna connector. RTL2832U devices having that RF tuner are very popular currently, especially in SDR usage.
There is not much to explain as I have already teardowned two devices build upon RTL2832U, but having different RF tuner. Look these first:
Naked hardware #6: ezcap USB 2.0 DVB-T Stick
Naked hardware #7: TerraTec Cinergy T Stick Black
R820T RF tunerThat RF tuner is quite new as it appeared devices less than one year ago. It is the latest tuner added to the RTL2832U reference designs until now (what I know).
Tuner is designed for digital terrestrial standards. Frequency range is from 42 to 1002 MHz, but it is said to to perform far more over that. Wide frequency range makes this tuner interesting, otherwise it is rather similar than typical DTV RF tuners nowadays. Everything but crystal is integrated, which mean less external components. No need for external LNA nor SAW filters (SAW filters are not needed since 1st generation silicon RF tuners, QT1010, MT2060, etc.).
R820T differs from the trend seen during last few years as it is not direct conversion aka zero IF tuner. That tuner is so called low-IF tuner, which means it uses intermediate frequency (IF) 5 MHz or less. Over the years, IFs used by DTV tuners has gone down from the ~50 MHz to few MHz or even zero (baseband). Compared to traditional superheterodyne architecture, direct conversion has many advantages like simpler architecture, lower power consumption and no harmful image frequency. Whilst direct conversion has many advantages it has some disadvantages too, most notable DC offset.
R820T power consumptionAs this RF tuner has different architecture than all the other modern tuners used with the RTL2832U I decided to take some measurements to see how much more power it consumes than those which are based of direct conversion architecture. I used live 634 MHz DVB-T signal which has 8MHz bandwidth. That is very typical DVB-T transmission condition.
Here are the results, measured from the USB, nominal voltage 5V:
Architecture complexity has a price. It seems to drain around 135mA more current than Zero-IF tuners compared. I could assume it is pretty much same for all the the other low-IF tuners too that are designed during last 3 years or so.
PCB bottom side is empty
|a lot of room for components|
I have one of these. I am using SDRsharp S/WReplyDelete
It clearly has a dc offset. About -200uV on both I and Q channels.
Why is this?
This chipset is meant to use a low IF rather than zero IF.
Could it be that SDRsharp is not configuring the down conversion frequency correctly.
I know the offset voltage from looking at recorded time domain data having calibrated with a known amplitude signal.
When I look at the data in the time domain I can see the dc offset.
(Also, when I look at the spectrum in SDRsharp the dc spike appears at about +47.6kHz which is weird. I have no frequency offsets set.)
I have one of these on order. I am looking to put it in an enclosure. Any chance you could publish dimensions of the PCB?ReplyDelete
Device case is very easy to open. Usually you will break some brackets when opening such device, but that one opens without any damage.Delete
78.5 * 25.0 mm. Whole device. Including USB-connector and antenna connector, but without case.
63.2 * 22.1 mm. PCB only. That is dimensions of plain PCB. Imagine it like all components are removed.
Maximum thickness is 9.3 mm. It is measured from only LED visible.
Do you guys know if this dongle works with linux ?ReplyDelete
Yes it works.Delete
" Linux support has been added since the Kernel 3.10."
This comment has been removed by the author.ReplyDelete
I have just a small problem with this one. SDR# works great and so othe rprograms, but I also wish to use the infrared receiver. Blazedvd works (with original drivers) but I can't seem to get IR keys/data from any other program. Any clues?ReplyDelete
Remote controller should be work, but I haven't tested it still. Remote controller keytable is not load automatically as device uses chipset default USB ID and due to that it is impossible to map correct keytable (many different devices and remote controllers used by same ID). So you have to load keytable manually. That remote controller looks very popular, there is likely correct keytable already, but I don't know name :-)Delete
Found /sys/class/rc/rc0/ (/dev/input/event16) with:
Driver dvb_usb_rtl28xxu, table rc-empty
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Name: Realtek RTL2832U reference desig
bus: 3, vendor/product: 0bda:2832, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms
Could someone else point command to load correct keytable for this device?
I have a problem with usb tunner RTL2832u R820T, ID 0bda:2832 .
Problem is in the read signal and quality with femon.
Ubuntu 14.04, kernel 3.13.
Problem retrieving frontend information: Operation not supported
status SCVYL | signal 0% | snr 0% | ber 0 | unc 1 | FE_HAS_LOCK
Tunner testing with Ubuntu 12.04, kernel 3.2 with driver from:
Problem retrieving frontend information: Operation not supported
status SCVYL | signal 40% | snr 100% | ber 0 | unc 1 | FE_HAS_LOCK
Please fix the driver for rtl2832 in media_tree.
I have recently bought a device 0bda:2832 (lsusb -vvd reports the same output than the one you have posted here). It's a RTL2832U with a R820T (the chassis is similar, but not equal to the one I've seen in your photo).
Under Ubuntu 14.04 with Kernel 3.13.0-37 it seems to be properly recognized however w_scan will never find any signal ("ERROR: Sorry - i couldn't get any working frequency/transponder").
I'm now built the latest media_build (2014-09-29) and I can still see the card recognized as we can see from dmesg:
[ 23.961723] usb 3-2: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[ 24.023401] usb 3-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 24.023407] DVB: registering new adapter (Realtek RTL2832U reference design)
[ 24.023604] i2c i2c-9: Added multiplexed i2c bus 10
[ 24.026207] i2c i2c-9: Added multiplexed i2c bus 11
[ 24.026209] usb 3-2: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[ 24.186333] r820t 9-001a: creating new instance
[ 24.201835] r820t 9-001a: Rafael Micro r820t successfully identified
[ 24.270227] usb 3-2: Registered as swradio0
[ 24.270229] i2c i2c-9: rtl2832_sdr: Realtek RTL2832 SDR attached
[ 24.270230] usb 3-2: rtl2832_sdr: SDR API is still slightly experimental and functionality changes may follow
[ 24.276612] Registered IR keymap rc-empty
[ 24.276659] input: Realtek RTL2832U reference design as /devices/pci0000:00/0000:00:14.0/usb3/3-2/rc/rc0/input15
[ 24.276730] rc0: Realtek RTL2832U reference design as /devices/pci0000:00/0000:00:14.0/usb3/3-2/rc/rc0
[ 24.278884] usb 3-2: dvb_usb_v2: schedule remote query interval to 400 msecs
[ 24.290063] usb 3-2: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected
[ 24.290084] usbcore: registered new interface driver dvb_usb_rtl28xxu
[ 24.348367] IR JVC protocol handler initialized
[ 24.348530] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input16
[ 24.348925] IR MCE Keyboard/mouse protocol handler initialized
[ 24.348931] IR NEC protocol handler initialized
[ 24.348942] IR RC5(x/sz) protocol handler initialized
[ 24.349139] IR RC6 protocol handler initialized
[ 24.349144] IR SANYO protocol handler initialized
[ 24.349148] IR Sharp protocol handler initialized
[ 24.349152] IR Sony protocol handler initialized
[ 24.349193] IR XMP protocol handler initialized
[ 24.350953] lirc_dev: IR Remote Control driver registered, major 248
[ 24.351630] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
[ 24.351630] IR LIRC bridge handler initialized
lsmod | grep dvb reports:
dvb_usb_rtl28xxu 30421 0
rtl2830 18804 1 dvb_usb_rtl28xxu
rtl2832 19784 2 dvb_usb_rtl28xxu
dvb_usb_v2 36107 1 dvb_usb_rtl28xxu
dvb_core 125880 3 rtl2830,rtl2832,dvb_usb_v2
rc_core 27389 14 ir_sharp_decoder,ir_xmp_decoder,lirc_dev,ir_lirc_codec,dvb_usb_rtl28xxu,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,ir_mce_kbd_decoder,ir_jvc_decoder,dvb_usb_v2,ir_rc6_decoder,ir_sanyo_decode
modinfo rtl2832xxu doesn't report any parameter that I could use for debug...
Is there anything that I can check to understand if this card is supposed to be supported or if there is anything missing?
Thank you very much...
Please send me copy of eprom this dongle,ReplyDelete
My dongle damaged because of remoçõa in use.
if possible send me binary file contained in 24C02.
This comment has been removed by a blog administrator.ReplyDelete