osmocom-sdr October 2017

osmocom-sdr@lists.osmocom.org

12 participants
11 discussions

Start a nNew thread

gr-osmosdr: add clock_source= parameter
by Michael Loeffler 25 Mar '21

25 Mar '21

Hello, the attached patch allows to set the clock_source on uhd devices in programs like gqrx. Bye

1 1

[PATCH] Revert "lib: fix direction bit in GPIO code"
by Marcus Müller 07 Nov '17

07 Nov '17

This reverts commit ba64a7459a43652354990855176a7d8dad5b9d54. The mentioned commit leads to nonfunctionality of Fitipower FC0012 dongles (tested by a small horde of students) and doesn't increase functionality on my "RTL-SDR.com" branded R820T-based dongle. --- src/librtlsdr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/librtlsdr.c b/src/librtlsdr.c index b369a5d..6c079a5 100644 --- a/src/librtlsdr.c +++ b/src/librtlsdr.c @@ -570,7 +570,7 @@ void rtlsdr_set_gpio_output(rtlsdr_dev_t *dev, uint8_t gpio) gpio = 1 << gpio; r = rtlsdr_read_reg(dev, SYSB, GPD, 1); - rtlsdr_write_reg(dev, SYSB, GPD, r & ~gpio, 1); + rtlsdr_write_reg(dev, SYSB, GPO, r & ~gpio, 1); r = rtlsdr_read_reg(dev, SYSB, GPOE, 1); rtlsdr_write_reg(dev, SYSB, GPOE, r | gpio, 1); } -- 2.13.6

5 6

Want to do paid work on Osmocom? sysmocom is hiring
by Harald Welte 31 Oct '17

31 Oct '17

Dear Osmocom community, I would like to point out that at sysmocom, we're currently (again) hiring [1]. If you happen to have an interest in open source cellular communications and are fluent in C language development, we would love to hear from you. sysmocom probably doesn't need any introduction here, but just in case: The company was founded by Holger Freyther and Harald Welte, two of the leading OpenBSC and Osmocom developers from the very early days of the project. Today we are responsible for by far the largest number of commits to the Osmocom GSM/3G infrastructure related git repositories. Among our current priorities are automatic testing for the GPRS PCU, generalization of the OsmoMGW media gateway, support for load-based hand-over, inter-BSC hand-over as well as various improvements on the lower layers of the GPRS protocol stack. We're very dedicated to the cause in furthering the capabilities of open source cellular infrastructure from 2G to 4G. We believe in working upstream, no open core or dual licensing. If you have an interest working with an enthusiastic, strong technical and dedicated team of Osmocom hackers, please don't hesitate to let me know, best by e-mail to jobs(a)sysmocom.de Thanks, Harald p.s.: I hope this kind of message is not disturbing to anyone. I think it is important to the Osmocom project to have more paid people working on the stack, so it is justified. The positions we are seeking to fill will work [almost exclusively] on Osmocom, so it's not a random job ad but in the very interest of Osmocom, and hence on-topic for this list. [1] https://www.sysmocom.de/jobs/ -- - Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

gr-osmosdr and the compile flag -std=gnu++11
by Cinaed Simson 30 Oct '17

30 Oct '17

Hi - I presume since I'm receiving a number of these types of errors while compiling /opt/gnuradio/src/gr-oot/gr-osmosdr/lib/rtl_tcp/rtl_tcp_source_c.cc:307:7: warning: extended initializer lists only available with -std=c++11 or -std=gnu++11 cmd = { 0x0a, htonl(offset_tune) }; i.e., complaining about -std=gnu++11, that I should probably be compiling gr-osmosdr with the -std=gnu++11 flag. Typically, I fall asleep at the wheel during the build - so I don't know which version these warning started. If it wasn't for my dog's wet nose pressing against my elbow, I'd still be sleeping. I'm using the following git pulls for rtl-sdr: commit 18bf26989c926a5db4fca29e7d859af42af1437c Author: hayati ayguen <h_ayguen(a)web.de> Date: Sun Jun 11 00:18:53 2017 +0200 gr-osmosdr: commit c653754dde5e2cf682965e939cc016fbddbd45e4 Merge: b7aab45 cf95494 Author: Dimitri Stolnikov <horiz0n(a)gmx.net> Date: Mon Jun 12 00:04:36 2017 +0200 and I have somewhat recent git pulls for libosmocore and libosmo-dsp. Should I be compiling the programs rtl-sdr and gr-osmosdr with -std=gnu++11? How about libosmocore and libosmo-dsp? -- Cinaed

1 0

searching osmocom-sdr archives
by vempati Sarma 25 Oct '17

25 Oct '17

I am having difficulty in searching archives as the search page does not have search window. How do I specific topic or problem? I am trying to use DAB+FM+DVB-T dongle in gnuradio-companion installed with latest pre-built package on Windows 10 OS. But, it is throwing error as follows: QUOTE Generating: 'C:\\Users\\vsrks_000\\Documents\\top_block.py' Executing: C:\GNURadio-3.7\gr-python27\python.exe -u C:\Users\vsrks_000\Documents\top_block.py Win32; Microsoft Visual C++ version 14.0; Boost_106000; UHD_003.010.001.001-0-unknown gr-osmosdr ae686c46 (0.1.5git) gnuradio 3.7.11 built-in source types: file osmosdr fcd rtl rtl_tcp uhd hackrf bladerf airspy redpitaya Using device #0 Generic RTL2832U OEM usb_open error -12 FATAL: Failed to open rtlsdr device. Trying to fill up 1 missing channel(s) with null source(s). This is being done to prevent the application from crashing due to gnuradio bug #528. gr::pagesize: no info; setting pagesize = 4096 UNQUOTE Can you please suggest a solution. -- Best Regards, vsrk sarma

1 0

rtl-sdr: gba64a74 breaks _my_ FC0012-based dongle
by Marcus Müller 25 Oct '17

25 Oct '17

Hi folks, something wasn't quite right with current git master of rtl-sdr, since it wouldn't detect the Fitipower FC0012 tuner on a couple (dozen) of my dongles. So, I had a quick git-bisect session that basically went: git checkout master git bisect start [build] [connect dongle] build/src/rtl_eeprom | grep "Found Fitipower" then git bisect good else git bisect bad [disconnect dongle] jump back to build, rinse, repeat turns out, when you _initialize_ the dongle with an older version, it works, even with the newer revisions (hence my un- and replugging exercises). The (reproducibly) offending commit is the GPO/GPD register swap in ba64a74 : librtlsdr.c, l. 570, - rtlsdr_write_reg(dev, SYSB, GPO, r & ~gpio, 1); + rtlsdr_write_reg(dev, SYSB, GPD, r & ~gpio, 1); Now, that commit's msg mentions http://lea.hamradio.si/~s57uuu/mischam/rtlsdr/ports.html and I don't want to break their application, but I can't get my dongles to run :( How to proceed from here? I'm not quite sure what I'd break if I just reverted that commit; _my_ R820T dongle continues to work if I revert, but I'm sure this commit didn't come out of thin air. Best regards, Marcus

1 0

Re: New SDR dongle received but cannot get it to work
by John 23 Oct '17

23 Oct '17

Cinead, My apologies for this and thanks for your clarification. I have followed thorough with the suggestions made by yourself and Marcus, including installing the provided ruleset and checking the device power usage. I have also tried another USB cable and another computer. However I did miss the point you made about leaving off the '-t' in the detail of your original response. Also, I have been responding to the messages I received from the mailing list thinking that I was responding to the mailing list, but it seems that I have actually been responding directly to individuals. This was unintentional and I apologise, but the e-mail 'From:' header on the messages I have received from the list shows the e-mail address of the individual who sent the message rather than the mailing list address which seems rather unusual. It means I have to manually copy in the 'osmocom-sdr(a)lists.osmocom.org' address into the 'To:' header each time I reply, as I have done in this case. So this is what I get with just rtl_test: $ rtl_test Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 00000001 Using device 0: Generic RTL2832U OEM usb_claim_interface error -5 Failed to open rtlsdr device #0. Its the same whether I run it as user or with root privileges. I don't see the dvb_usb_rtl28xxu kernel driver being loaded in the output of lsmod. > > Okay, if you send another email with output of > > rtl_test -t > > I'm going to blacklist your email address. > > Use > > rtl_test > > to run the test for a 2832. > > Use > > rtl_test -t > > to run the test for a 2838. > > Type > > rtl_test --help > > It clearly indicates the -t flag in rtl_test is for the E4000. > > The system claims you have a 2832 - and not a 2838 or E4000 - so get > over it. > > Clear enough? > > >> Found 1 device(s): >> 0: Realtek, RTL2838UHIDIR, SN: 00000001 >> >> Using device 0: Generic RTL2832U OEM >> Found Rafael Micro R820T tuner > > This is your device: > > Using device 0: Generic RTL2832U OEM > Found Rafael Micro R820T tuner > > It clearly states it's a RTL2832 device with a Rafael Micro R820T tuner. > > >> r82xx_write: i2c wr failed=-1 reg=1a len=7 >> r82xx_write: i2c wr failed=-1 reg=0c len=1 >> r82xx_init: failed=-1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 >> 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 >> 43.4 43.9 44.5 48.0 49.6 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> r82xx_write: i2c wr failed=-1 reg=0a len=1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> WARNING: Failed to set sample rate. >> No E4000 tuner found, aborting. > > No E4000 tuner found, aborting. > > This statement clearly indicates your device is NOT a E4000 - or a 2838. > >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_write_reg failed with -1 >> > > Did you remove the your home brewed file from /etc/udev/rules.d? If not > then remove it and reboot. > > Send me a listing of > > /etc/modprobe.d > > and the contents of the file you're using to blacklist the RTL devices. > > Also, update your system listing and install the following > > apt-get update > apt-get install librtlsdr-dev > apt-get install libusb-1.0-0-dev > > What type of computer are you using? If you're using a computer with > more than 1 USB port, try plugging the dongle into another port. > > It's possible the RTL dongle is bad or you have problems with your USB > ports - but you need to eliminate system possible system software issues > first. > > -- Cinaed > > >>> Cinaed Simson<mailto:cinaed.simson@gmail.com> >>> 22 October 2017 03:53 >>> On 10/21/2017 09:08 AM, John wrote: >>>> Hello, >>>> >>>> I am new to this list and to SDR radio. I have purchased an SDR dongle >>>> but am having trougble getting it to work. The dongle was described as >>>> an RTL8232U/R820T2 device. I am running on Linux MINT version 18.2 and >>>> lsusb detects the device as follows: >>>> >>>> Bus 002 Device 051: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T >>>> >>>> Is it an RTL2832U or an RTL2838? I'm not really sure. >>>> >>>> > From research it seems that It seems like the fist order of business is >>>> to blacklist the kernel driver? So I have done this by adding a >>>> backlist-rtl.conf file to /etc/modprobe.d and rebooted the computer. I >>>> have also added a rules file to /etc/udev/rules.d with the following >>>> content: >>>> >>>> # Realtek Semiconductor Corp. RTL2838 DVB-T >>>> SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", >>>> MODE:="0666", GROUP="adm", SYMLINK+="rtl_sdr" >>>> >>>> I can now access the device in user mode without permission errors so I >>>> assume that this is working OK. >>>> >>>> So my next step was to run rtl_test -t. The output I got contained >>>> errors.If I then try to run any sdr software such as rtl_fm or gqrx, the >>>> device is reset and the application fails to run. Subsequentlly running >>>> 'rtl_test -t' gives: >>>> >>>> No supported devices found. >>>> >>>> Even running rtl_test-t sometimes does the same so i'm not sure whether >>>> the device is 'dropping out' of its own accord. >>>> >>>> I am wondering whether the current crop of devices are supported? Or is >>>> this a configuration problem? >>>> >>>> >>>> The output from rtl_test: >>>> >>>> rtl_test -t >>> The output from rtl_test indicates it's a "2832" - but your home brewed >>> rule is probing for a "2838" which is the E4000. >>> >>> I recommend you install the enclosed udev rules. >>> >>> After you copy them to /etc/udev/rules.d, try >>> >>> udevadm control --reload >>> udevadm trigger >>> >>> If that doesn't work, reboot. >>> >>> The correct rules should have been installed when you installed the >>> sofware - so you may have other problems. >>> >>> And use >>> >>> rtl_test >>> >>> The command >>> >>> rtl_test -t >>> >>> is for the E4000 - and your enclosed error message indicates it's not E4000. >>> >>> -- Cinaed >>> >>>> Found 1 device(s): >>>> 0: Realtek, RTL2838UHIDIR, SN: 00000001 >>>> >>>> Using device 0: Generic RTL2832U OEM >>>> Found Rafael Micro R820T tuner >>>> r82xx_write: i2c wr failed=-1 reg=13 len=7 >>>> r82xx_write: i2c wr failed=-1 reg=0c len=1 >>>> r82xx_init: failed=-1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 >>>> 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 >>>> 43.4 43.9 44.5 48.0 49.6 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> r82xx_write: i2c wr failed=-1 reg=0a len=1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> WARNING: Failed to set sample rate. >>>> No E4000 tuner found, aborting. >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_demod_write_reg failed with -1 >>>> rtlsdr_demod_read_reg failed with -1 >>>> rtlsdr_write_reg failed with -1 >>>> >>>> >>>> >>> John<mailto:subs@qcontinuum.plus.com> >>> 21 October 2017 17:08 >>> Hello, >>> >>> I am new to this list and to SDR radio. I have purchased an SDR dongle >>> but am having trougble getting it to work. The dongle was described as >>> an RTL8232U/R820T2 device. I am running on Linux MINT version 18.2 and >>> lsusb detects the device as follows: >>> >>> Bus 002 Device 051: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 >>> DVB-T >>> >>> Is it an RTL2832U or an RTL2838? I'm not really sure. >>> >>> From research it seems that It seems like the fist order of business >>> is to blacklist the kernel driver? So I have done this by adding a >>> backlist-rtl.conf file to /etc/modprobe.d and rebooted the computer. I >>> have also added a rules file to /etc/udev/rules.d with the following >>> content: >>> >>> # Realtek Semiconductor Corp. RTL2838 DVB-T >>> SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", >>> MODE:="0666", GROUP="adm", SYMLINK+="rtl_sdr" >>> >>> I can now access the device in user mode without permission errors so >>> I assume that this is working OK. >>> >>> So my next step was to run rtl_test -t. The output I got contained >>> errors.If I then try to run any sdr software such as rtl_fm or gqrx, >>> the device is reset and the application fails to run. Subsequentlly >>> running 'rtl_test -t' gives: >>> >>> No supported devices found. >>> >>> Even running rtl_test-t sometimes does the same so i'm not sure >>> whether the device is 'dropping out' of its own accord. >>> >>> I am wondering whether the current crop of devices are supported? Or >>> is this a configuration problem? >>> >>> >>> The output from rtl_test: >>> >>> rtl_test -t >>> Found 1 device(s): >>> 0: Realtek, RTL2838UHIDIR, SN: 00000001 >>> >>> Using device 0: Generic RTL2832U OEM >>> Found Rafael Micro R820T tuner >>> r82xx_write: i2c wr failed=-1 reg=13 len=7 >>> r82xx_write: i2c wr failed=-1 reg=0c len=1 >>> r82xx_init: failed=-1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 >>> 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 >>> 43.4 43.9 44.5 48.0 49.6 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> r82xx_write: i2c wr failed=-1 reg=0a len=1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> WARNING: Failed to set sample rate. >>> No E4000 tuner found, aborting. >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_demod_write_reg failed with -1 >>> rtlsdr_demod_read_reg failed with -1 >>> rtlsdr_write_reg failed with -1 >>> >>> >>> >> -- >> John > > John <mailto:subs@qcontinuum.plus.com> > 22 October 2017 17:02 > Cinead, > > Thank you for this information and the ruleset. I have been looking > for an 'official' ruleset to try, but couln't find one. For whatever > reason a ruleset was not automatically installed. However, I installed > the software from the repository via apt-get rtl-sdr rather than > downloading and compiling. > > I have now removed the file I created and installed the one you > provided. Unfortunately it made no difference. I initially used just > the two udev commands to re-initialise udev, but then also rebooted > for good measure. > > You observation is interesting however, as this device identifies > itself as vendorID '0bda' and deviceID '2838' in lsusb: > > Bus 002 Device 012: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T > > and likewise in dmesg: > > [ 622.683133] usb 2-1.6: new high-speed USB device number 12 using > ehci-pci > [ 622.787405] usb 2-1.6: New USB device found, idVendor=0bda, > idProduct=2838 > [ 622.787410] usb 2-1.6: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 622.787413] usb 2-1.6: Product: RTL2838UHIDIR > [ 622.787415] usb 2-1.6: Manufacturer: Realtek > [ 622.787417] usb 2-1.6: SerialNumber: 00000001 > > As you point out however, it has an R820T tuner, which has now been > visually confirmed by the markings on the IC, so if RTL and other > programs are expecting an E4000 then this is probably not going to > work. I expect that the device will always match the second rule in > the ruleset and it seems that it is possible to access the device in > user mode. However I'm not sure how to get around the expectations of > the driver? Curiously the second rule refers to 'Newsky TV28T > (E4000/R820T)' which mentions both radios for the same product ID, so > then one might expect that the driver looks for either and tries to > determine which it is? > > rtl_test seemed to identify it correctly - 'Found Rafael Micro R820T > tuner' but then then also fails to find an E4000 radio 'No E4000 tuner > found, aborting.' so my assumption was that it was trying to determine > which one was present, but then I am not familiar with the code. > > So the question in my mind is whether rtl_test is indeed making a > determination and the errors are due to a problem communicating with > the device, or whether it is looking for E4000 hardware as you say and > failing because it is sending inappropriate commands. If the latter, > then is there a way to fool it, e.g. by temporarily changing the > device ID or forcing the driver to communicate with an RT820T radio? > > I did find the -d flag and tried rtl_test -d0 but this yielded a > similar response, although it did not identify any tuner and simply > returned 'No supported tuner found'. > > The full output is below: > > $ rtl_test -t > Found 1 device(s): > 0: Realtek, RTL2838UHIDIR, SN: 00000001 > > Using device 0: Generic RTL2832U OEM > Found Rafael Micro R820T tuner > r82xx_write: i2c wr failed=-1 reg=1a len=7 > r82xx_write: i2c wr failed=-1 reg=0c len=1 > r82xx_init: failed=-1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 > 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 > 43.4 43.9 44.5 48.0 49.6 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > r82xx_write: i2c wr failed=-1 reg=0a len=1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > WARNING: Failed to set sample rate. > No E4000 tuner found, aborting. > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_write_reg failed with -1 > > > > > > Cinaed Simson <mailto:cinaed.simson@gmail.com> > 22 October 2017 03:53 > On 10/21/2017 09:08 AM, John wrote: >> Hello, >> >> I am new to this list and to SDR radio. I have purchased an SDR dongle >> but am having trougble getting it to work. The dongle was described as >> an RTL8232U/R820T2 device. I am running on Linux MINT version 18.2 and >> lsusb detects the device as follows: >> >> Bus 002 Device 051: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T >> >> Is it an RTL2832U or an RTL2838? I'm not really sure. >> >> From research it seems that It seems like the fist order of business is >> to blacklist the kernel driver? So I have done this by adding a >> backlist-rtl.conf file to /etc/modprobe.d and rebooted the computer. I >> have also added a rules file to /etc/udev/rules.d with the following >> content: >> >> # Realtek Semiconductor Corp. RTL2838 DVB-T >> SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", >> MODE:="0666", GROUP="adm", SYMLINK+="rtl_sdr" >> >> I can now access the device in user mode without permission errors so I >> assume that this is working OK. >> >> So my next step was to run rtl_test -t. The output I got contained >> errors.If I then try to run any sdr software such as rtl_fm or gqrx, the >> device is reset and the application fails to run. Subsequentlly running >> 'rtl_test -t' gives: >> >> No supported devices found. >> >> Even running rtl_test-t sometimes does the same so i'm not sure whether >> the device is 'dropping out' of its own accord. >> >> I am wondering whether the current crop of devices are supported? Or is >> this a configuration problem? >> >> >> The output from rtl_test: >> >> rtl_test -t > > The output from rtl_test indicates it's a "2832" - but your home brewed > rule is probing for a "2838" which is the E4000. > > I recommend you install the enclosed udev rules. > > After you copy them to /etc/udev/rules.d, try > > udevadm control --reload > udevadm trigger > > If that doesn't work, reboot. > > The correct rules should have been installed when you installed the > sofware - so you may have other problems. > > And use > > rtl_test > > The command > > rtl_test -t > > is for the E4000 - and your enclosed error message indicates it's not E4000. > > -- Cinaed > >> Found 1 device(s): >> 0: Realtek, RTL2838UHIDIR, SN: 00000001 >> >> Using device 0: Generic RTL2832U OEM >> Found Rafael Micro R820T tuner >> r82xx_write: i2c wr failed=-1 reg=13 len=7 >> r82xx_write: i2c wr failed=-1 reg=0c len=1 >> r82xx_init: failed=-1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 >> 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 >> 43.4 43.9 44.5 48.0 49.6 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> r82xx_write: i2c wr failed=-1 reg=0a len=1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> WARNING: Failed to set sample rate. >> No E4000 tuner found, aborting. >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_demod_write_reg failed with -1 >> rtlsdr_demod_read_reg failed with -1 >> rtlsdr_write_reg failed with -1 >> >> >> > > John <mailto:subs@qcontinuum.plus.com> > 21 October 2017 17:08 > Hello, > > I am new to this list and to SDR radio. I have purchased an SDR dongle > but am having trougble getting it to work. The dongle was described as > an RTL8232U/R820T2 device. I am running on Linux MINT version 18.2 and > lsusb detects the device as follows: > > Bus 002 Device 051: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 > DVB-T > > Is it an RTL2832U or an RTL2838? I'm not really sure. > > From research it seems that It seems like the fist order of business > is to blacklist the kernel driver? So I have done this by adding a > backlist-rtl.conf file to /etc/modprobe.d and rebooted the computer. I > have also added a rules file to /etc/udev/rules.d with the following > content: > > # Realtek Semiconductor Corp. RTL2838 DVB-T > SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", > MODE:="0666", GROUP="adm", SYMLINK+="rtl_sdr" > > I can now access the device in user mode without permission errors so > I assume that this is working OK. > > So my next step was to run rtl_test -t. The output I got contained > errors.If I then try to run any sdr software such as rtl_fm or gqrx, > the device is reset and the application fails to run. Subsequentlly > running 'rtl_test -t' gives: > > No supported devices found. > > Even running rtl_test-t sometimes does the same so i'm not sure > whether the device is 'dropping out' of its own accord. > > I am wondering whether the current crop of devices are supported? Or > is this a configuration problem? > > > The output from rtl_test: > > rtl_test -t > Found 1 device(s): > 0: Realtek, RTL2838UHIDIR, SN: 00000001 > > Using device 0: Generic RTL2832U OEM > Found Rafael Micro R820T tuner > r82xx_write: i2c wr failed=-1 reg=13 len=7 > r82xx_write: i2c wr failed=-1 reg=0c len=1 > r82xx_init: failed=-1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 > 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 > 43.4 43.9 44.5 48.0 49.6 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > r82xx_write: i2c wr failed=-1 reg=0a len=1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > WARNING: Failed to set sample rate. > No E4000 tuner found, aborting. > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_demod_write_reg failed with -1 > rtlsdr_demod_read_reg failed with -1 > rtlsdr_write_reg failed with -1 > > > -- John

2 1

New SDR dongle received but cannot get it to work
by John 21 Oct '17

21 Oct '17

Hello, I am new to this list and to SDR radio. I have purchased an SDR dongle but am having trougble getting it to work. The dongle was described as an RTL8232U/R820T2 device. I am running on Linux MINT version 18.2 and lsusb detects the device as follows: Bus 002 Device 051: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Is it an RTL2832U or an RTL2838? I'm not really sure. From research it seems that It seems like the fist order of business is to blacklist the kernel driver? So I have done this by adding a backlist-rtl.conf file to /etc/modprobe.d and rebooted the computer. I have also added a rules file to /etc/udev/rules.d with the following content: # Realtek Semiconductor Corp. RTL2838 DVB-T SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", MODE:="0666", GROUP="adm", SYMLINK+="rtl_sdr" I can now access the device in user mode without permission errors so I assume that this is working OK. So my next step was to run rtl_test -t. The output I got contained errors.If I then try to run any sdr software such as rtl_fm or gqrx, the device is reset and the application fails to run. Subsequentlly running 'rtl_test -t' gives: No supported devices found. Even running rtl_test-t sometimes does the same so i'm not sure whether the device is 'dropping out' of its own accord. I am wondering whether the current crop of devices are supported? Or is this a configuration problem? The output from rtl_test: rtl_test -t Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 00000001 Using device 0: Generic RTL2832U OEM Found Rafael Micro R820T tuner r82xx_write: i2c wr failed=-1 reg=13 len=7 r82xx_write: i2c wr failed=-1 reg=0c len=1 r82xx_init: failed=-1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 r82xx_write: i2c wr failed=-1 reg=0a len=1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 WARNING: Failed to set sample rate. No E4000 tuner found, aborting. rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_demod_write_reg failed with -1 rtlsdr_demod_read_reg failed with -1 rtlsdr_write_reg failed with -1 -- John

3 2

build-gnuradio
by Martin McCormick 19 Oct '17

19 Oct '17

I am running Debian 7 on a system and Debian 8 on two other PC's and a raspberry PI and having no luck on running the build-gnuradio script. All the Debian 8 systems get as far as stating that the version is unsupported and that's it. The Debian 7 system (wheezy) goes through a number of tests before bombing on not being able to execute certain processes but it appears to get farther than any of the Debian 8 (jessie) systems so it appears that Debian 7 is closest. Is there any place in the script to find a version number so as to be sure that this script is the latest version? I would like to try to receive DMR transmissions as well as try some of the other interesting decoding possibilities but so far, nothing but failure to launch. Thanks for any constructive ideas. Martin McCormick

2 2

Planning for OsmoCon + OsmoDevCon
by Harald Welte 14 Oct '17

14 Oct '17

[cross-post to many lists, please follow-up-to openbsc(a)lists.osmocom.org] Dear all, time is flying, and I would like to start early with discussions and planning about OsmoCon and OsmoDevCon in 2018. It helps to start early. Side note: We have some pending issues about the events from last year at http://osmocom.org/projects/osmo-dev-con/issues - I've incorporated them in the text below. == OsmoDevCon == For OsmoDevCon, I think it's easy: We keep it as-is. Same procedure as every year, which means: * same venue, same catering options * same concept of 'anyone contributing to Osmocom can apply for registration until all seats are taken' * same idea of inviting some few speaker[s] doing other FOSS mobile communications work to join us The parts that we need to change, IMHO: * don't reduce from 4 to 3 days like last year. Have full 4 days again * sort topics per day / half-day, i.e. have "GSM/UMTS Cellular Infrastructure" days for BTS/BSC/NITB/MSC/HLR/SGSN/GGSN & Co, but then have other days for other projects. This would enable people not interested in the [continued evolvement] of the cellular projects be able to skip those days, or to simply meet in an adjacent room for parallel hacking sessions/discussions * try to be a bit more structured with the schedule in general. The existing approach works for people who attend all the event all day long, but not so well for people with other plans / limited time Any further change requests or topics to discuss? Please note that Pablo Neira has offered to kindly host an OsmoDevCon in Seville (Spain). I've attended a number of netfilter workshops he organized there, and he's doing a great job! However, given the large number of attendees from Berlin (and Germany in general), I think this would make things more complicated, and more expensive for most attendees. If you disagree with that assessment: I'm open for having the discussion, I just thought it's more practical/economic to do it in Berlin. === 10 year Anniversary Party === Given that 2018 marks the 10 year anniversary of Dieter and me hacking with the Siemens BS-11 in 2008, I think the 2018 incarnation deserves some special celebration of some form. I have no concrete idea yet, but for sure we should so something, and it should be at/around OsmoDevCon. And for sure we should have a BS-11 around :) == OsmoCon == The public OsmoCon was welcomed and was a success. However, let's start this discussion with a review of last years event. === Registration === * Registrations came in way too late. Two weeks ahead of the event, we were considering to cancel it. And then within the last few days, we had to turn people down due to limited seating capacity * To make planning more reliable, we see on other option but to significantly raise the registration fee combined with an equally significant discount for early booking === Duration === * Many people requested multiple days rather than just one, in order to make more out of (long distance) travels. This is obvious, but as we had no idea how many people would attend at all (or if we have to cancel due to lack of attendance), planning multiple days in the first incarnation would have been high risk and a multitude of work * I would suggest to expand to two or even three days this week, possibly one days with tutorials and the other day with tech talks * Slightly less crammed schedule due to multiple days === Venue === We recognize this yearso venue was not the best option, due to * Bad ventilation in the basemenet * Difficult to find * No space next to the conference room where people can meet / hang out in parallel to talks (not everyone attends every talk) I still like the "understatement" of the venue. I'd prefer any hostel / non-profit / hackerspace / university over luxurious hotels any time. Going to an expensive venue means more or less automatically more expensive ticket fees, which again is more likely to exclude pure community members without a commercial activity related to Osmocom. So any future venue would ideally: * be able to hold slightly more people than this year * have a second room or large lobby in which people can meet for extended coffee breaks in parallel to some talks, as needed * be slightly easier to find (and we have to put up some signs outside and in the lobby) * have better WiFi and/or wired connectivity === Programme / Format === * less crammed over multiple days * some more "interactive" formats were requested, for users to provide feedback to developers * there was some discussion about topics / speakers in redmine last year, but not too much participation [until it was too late]. * I'd suggest a more formal CfP process with a submission deadline that allows us to publish a preliminary schedule long ahead of the event === Video Recordings === I think they were a big success, and it was a very big surprise that the CCC Video Operations Center was volunteering to help such a small and niche-interest event like OsmoCon. We should make sure that we can repeat this for 2018. == Dates / Frequency == Having OsmoCon and OsmoDevCon back to back becomes somewhat long, if OsmoCon is 2-3 days and OsmoDevCon is 4 days. Basically we're looking at a full week for those of you who would like to attend both events. But then, I think the number of people attending both events is actually not all that big. Without checking the details, I think not more than half of the OsmoDevCon attendees were attending OsmoCon. I would expect that tendency to remain or even increase. I still think it's good to keep them back-to-back. In terms of frequency, I would actually suggest we move to a 6-month cycle rather than a 12-month cycle. There's a lot of development going on at all time. I understand that not everyone is able to attend two events just on Osmocom, especially if it's a spare time / hobby type activity. That's ok, I think there's no problem with attending either of the two only, and catching up by video recordings and/or mail on the other. The qeustion is: Should that second event be developer-oriented or user-oriented? Or again both? Any comments here? Ok, that was a somewhat lengthy e-mail. Please make sure to provide any feedback you may have as early as possible, to increase the chances of your feedback being reflected in the planning. Happy hacking, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-sdr October 2017