Re: Gnuradio 3.8 on a Raspberry pi 4 B?
On 11/25/21 5:52 PM, Marcus Müller wrote: Hi Lamar! ... I don't want to get into this again, honestly, we have like six or seven threads on this mailing list. Marcus, Sorry if I come across as a bit abrasive; that's not the intent. Nor am I wanting to overstate the point, or just continue an unproductive conversation ad nauseum. It's really that simple: Stillstand and technical and community Death, or Progress and Breakage. It's a balance to strike, which is why with every release, the poor Maintainer goes and looks into their crystal ball, to see what they can improve without breaking the usability on reasonably old systems for the next release. We're really doing our best to *not* let GNU Radio die, so please understand that as much as I personally like what Glen does, it cannot define GNU Radio's speed. ... Of course it can't define it; not my point. My point is that a part of release balance is migration planning that allows smooth transitions and upgrades. I advocated for that for years for another large project that tended to break things every major version; I maintained the RPM packages for that software for five years, and was perpetually caught in the middle between those who developed the software, expecting users to do various 'things' to upgrade from one version to the next and those users who expected 'rpm -U' to Just Work, which it didn't. So I DO understand and sympathize with the issues on the developer side. But I also believe that breakage should not happen between incremental versions. Since GNUradio is built on Python, using the Python model, I expect breakage between Python 2.x and 3.x; I expect rather less breakage between 3.x and 3.(x+1). That's when as a maintainer, you, responsibly, publicly say that, no, sorry, we're no longer in a position to guarantee the quality of further software releases. I have been in that position; it's not an easy one. And no you can't guarantee that quality as a volunteer. So, please, understand that I might get a bit frustrated by people portraying things like we're letting Glen stand out in the rain. Or that we do things "willy-nilly". We don't. We made sure he has migration options, multiple people are and have been offering help, people are actively trying to help him get his airplay running, even though it's a commercial product that's incompatible by its own choice with our software license. I am familiar with the frustration on both the developers' parts and the users' parts, since I HAVE been caught between. And no I don't believe you're 'letting Glen stand out in the rain' or doing things 'willy-nilly;' that's reading more into what I wrote than is there. I am just stating a fact; even the churn that is necessary muddies the waters. No argument from me that upgrades and progress is necessary; it IS necessary, but what has been lacking (at least the last time I checked; my apologies if this type of document now exists) is a document that outlines the changes required for OOT modules and users programs to migrate from one version to another; better in ways would be a script that can make the edits, although the way of automation is fraught with peril (been there, done that, during the same stint as RPM maintainer). And YES the SDRplay API is way more closed than I would like. And I'm not trying to frustrate anyone; but there IS significant volatility in the GNUradio system that can be very frustrating to users.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Lamar! On 25.11.21 14:39, Lamar Owen wrote: On Nov 25, 2021 8:15 AM, Marcus Müller wrote: ... Honestly, a RPi4 would just go to waste with me! If you want to crowdsource one for the greater good of the SDR community, I'd say: Radioastronomy outreach, or ham radio, that's the two things I'd think a RPi4 would make the biggest impact. Radio astronomy outreach is PRECISELY what Glen is doing, and what the rapid changes in GNUradio are making difficult. I don't want to get into this again, honestly, we have like six or seven threads on this mailing list. What works today will continue working as long as the hard- and software it is based on exists and functions. Nobody is asking Glen to delete his code (quite the opposite, share with us so we can help you)! Thing is: soft- and hardware we work on is subject to change. We're not the one choosing that. What I did 2018–2021ish is to make sure GNU Radio works in 2021, on systems you install 2021. It does. Had we kept everything the way Glen wished we, then it wouldn't, and we would have not seen the explosion in active contributors that now actually do something with GNU Radio that it couldn't do before. It's really that simple: Stillstand and technical and community Death, or Progress and Breakage. It's a balance to strike, which is why with every release, the poor Maintainer goes and looks into their crystal ball, to see what they can improve without breaking the usability on reasonably old systems for the next release. We're really doing our best to *not* let GNU Radio die, so please understand that as much as I personally like what Glen does, it cannot define GNU Radio's speed. It literally mustn't, lest you want people to fork off GNU Radio and do something that actually moves forward. I've got a longer email in one of the other threads on this, but that's *exactly* what we had with the `next` branch during the later years of the great 3.7 stagnation. Fragmentation, a lack of perspective, and hence a reduced contributor base, which then led to need for *abrupter* chaos. Luckily, you don't have to make a fork to get an old version of GNU Radio: you can just download, build and install an old version of GNU Radio :) Problem is, at some point you can, but none of the maintainers actually find time to do the same, so they know everything they do to that old version might break something in more or less subtle ways. That's when as a maintainer, you, responsibly, publicly say that, no, sorry, we're no longer in a position to guarantee the quality of further software releases. And that's exactly what Jeff announced for 3.7: Hey, we haven't done anything to it for quite a while, we can't actually test what it does when we change something, we don't have the programmer and maintainer volunteer base to develop this version: it's outdated. Luckily, we did this after years after releasing 3.8, which very clearly was meant to be a version that should make the transition from 5 years of standstill to something that will still compile next year easier (Python2 compatibility, SWIG, GRC conversion features, nearly no code structure changes). So, please, understand that I might get a bit frustrated by people portraying things like we're letting Glen stand out in the rain. Or that we do things "willy-nilly". We don't. We made sure he has migration options, multiple people are and have been offering help, people are actively trying to help him get his airplay running, even though it's a commercial product that's incompatible by its own choice with our software license. We have a fantastic release management (kudos to Jeff, but also to Josh for planning the next releases) and maintenance branch longevity for a project with this few people actually doing the codebase work. We've got *awesome* volunteers. Please don't scare them away! Best regards, Marcus smime.p7s Description: S/MIME Cryptographic Signature
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
On Nov 25, 2021 8:15 AM, Marcus Müller wrote:... Honestly, a RPi4 would just go to waste with me! If you want to crowdsource one for the greater good of the SDR community, I'd say: Radioastronomy outreach, or ham radio, that's the two things I'd think a RPi4 would make the biggest impact.Radio astronomy outreach is PRECISELY what Glen is doing, and what the rapid changes in GNUradio are making difficult. The SDRplay device has some good characteristics for this. (I have a couple myself, as well as a Pluto, an Airspy R2, an Airspy Mini, a LimeSDR, and a smattering of RTL-SDR devices.While I know GNUradio is just a huge project, and that it is unreasonable to expect everything in it to be stable, the major churn between 3.7, 3.8, and 3.9 makes it difficult and discouraging to those who are trying to use it for outreach like this.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Greg, :) ! On 24.11.21 18:44, Gregory Ratcliff wrote: Marcus, "..I don't have an RPi4, so can't test.” You really should get one, if only to monitor ADSB from airplanes on your own. I've got Deutsche Flugsicherung round the corner, and to be honest, they're doing a better job! (Truth is, I've got so much more hardware than time... I did gift my father an RTL dongle and a setting up of gr-air-modes on his laptop for his birthday a couple years back. These days, he uses the dongle to listen to DAB+ broadcasts.) Honestly, a RPi4 would just go to waste with me! If you want to crowdsource one for the greater good of the SDR community, I'd say: Radioastronomy outreach, or ham radio, that's the two things I'd think a RPi4 would make the biggest impact. Cheers, Marcus smime.p7s Description: S/MIME Cryptographic Signature
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
To add another piece of information to this discussion, last night I built the whole GNU Radio 3.9-maint on my Raspberry Pi, and it wasn't too bad. I followed the instructions from here: - https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi - https://wiki.gnuradio.org/index.php/InstallingGR#For_GNU_Radio_3.9_and_Master_Branch - https://github.com/gnuradio/volk#building-on-raspberry-pi-and-other-arm-boards-32-bit The heavy step, which was the 'make' in the GNU Radio 'build' directory, took about 2 hours and 10 minutes on the Raspberry Pi using 'make -j 3' - I think it is a reasonable time considering I built all of the in-tree modules except for gr-uhd. 73, Franco K4VZ > On 11/24/2021 12:44 PM Gregory Ratcliff wrote: > > > Marcus, > > > "..I don't have an RPi4, so can't test.” > > You really should get one, if only to monitor ADSB from airplanes on your > own. > > > All, > > Oh my. Many of us have always had Marcus on the "Marcus pedestal", > thinking he knew or more importantly experimented with all things tech + > Linux. > Maybe we need to create a crowdfund for him? > > > Why? I think the RPi is the most influential STEM tool ever created. RPi > + DSP = new converts and experts > > Years ago, Fred Martin (Media Lab) designed the coolest SBC called the > miniboard for undergrads for the MIT 6.170 course; he shared the board layout > with me and while at Ohio State a small group of us made thousands of them. > Fred was the first Ebon in my book. > > At the same time I was working on the TAPR DSP59 project and was holding > both the mini board and my recently hand assembled DSP59 in my hands thinking > there _had_to_a_way. There wasn’t. > A lot has changed. > > Why2? > > I think the world of computing is becoming more level. By this I mean > that in core middle range of mainstream computing, they are all getting > closer from a performance standpoint, only differing by factors of ten or so. > > Think about what the performance of the RPi 12 will be- it will be > limited, but likely perfectly capable of doing some magical work for us. > These fringe (and fun) SBCs and projects help produce the needed experts > that we need. > > Apologies for evangelizing a bit on the gnuradio list-please keep up the > great work. > > Greg > nz8r > >
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Marcus, "..I don't have an RPi4, so can't test.” You really should get one, if only to monitor ADSB from airplanes on your own. All, Oh my. Many of us have always had Marcus on the "Marcus pedestal", thinking he knew or more importantly experimented with all things tech + Linux. Maybe we need to create a crowdfund for him? Why? I think the RPi is the most influential STEM tool ever created. RPi + DSP = new converts and experts Years ago, Fred Martin (Media Lab) designed the coolest SBC called the miniboard for undergrads for the MIT 6.170 course; he shared the board layout with me and while at Ohio State a small group of us made thousands of them. Fred was the first Ebon in my book. At the same time I was working on the TAPR DSP59 project and was holding both the mini board and my recently hand assembled DSP59 in my hands thinking there _had_to_a_way. There wasn’t. A lot has changed. Why2? I think the world of computing is becoming more level. By this I mean that in core middle range of mainstream computing, they are all getting closer from a performance standpoint, only differing by factors of ten or so. Think about what the performance of the RPi 12 will be- it will be limited, but likely perfectly capable of doing some magical work for us. These fringe (and fun) SBCs and projects help produce the needed experts that we need. Apologies for evangelizing a bit on the gnuradio list-please keep up the great work. Greg nz8r smime.p7s Description: S/MIME cryptographic signature
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Note that this is an old thread that just got reopened, probably by mistake. On Wed, Nov 24, 2021 at 12:11 PM Marcus Müller wrote: > Hi Jean-Michel, > > don't apologize for sharing your technically shaped view on things. I, > too, would look at > an RPi4 as embedded device! But that is because my use ways of thinking > are much more in > terms of "do GUI-ish stuff on a PC/laptop, number crunching on a > PC/workstation/server, > and only exactly what needs to be done there on an embedded platform". > I can see how if you want to write letters or browse the web, a > low/medium-end > smartphone-powered computer works for you. And, sure enough, > low/medium-rate signal > processing, why not; if I need things to demodulate something in the kHz > range and display > something simple, OK, why not wayland/Mutter, X11/XFCE or whatever. > > Regarding suboptimality: yep, Raspbian is a 32bit ARM debian-derivative > distro "same > binary for all RPi generations", and they literally build-on-target, and > although the very > few people behind it very critical for establishing the RPi as "the" Linux > SBC, they've > not really received any official support from the Pi foundation; do with > that info what > you will. The Raspbian person I've had contact was super nice, and he > helped me understand > how GNU Radio works under these situations. He was happy to hear how VOLK > worked. Nice guy. > > Raspberry Pi OS is a more directly derived debian (currently, based on > Debian 11), and as > far as I know it uses sensible architectural settings for the RPi4. That > means you should > be able to "apt install gnuradio" and run "volk_profile" right there. I > don't have an > RPi4, so can't test. Last time I checked (that's already a while back) > they still haven't > put together an officially sanctioned QEMU aarch64 target with enough > device tree to > emulate a headless RPi. > > I honestly think that unless you're doing something *very* specific > chances are, you'll > never have to use a self-built GNU Radio on a RPi these days; and I've > been asking people > not to build on target forever, not the least to save them the pain. > > Best regards, > Marucs > > On 29.05.20 17:07, jean-michel.fri...@femto-st.fr wrote: > > apologies to the list then, I was not aware of the use of RPi as > > desktop computer, and have always been obsessed with optimization > > of resources for embedded systems. Most probably for a desktop use, > > a sub-optimal binary distribution such as Raspbian is best suited indeed, > > as we find daily on our personal computers. > > > > JM > > > > -- > > JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > > 25000 Besancon, France > > > > May 29, 2020 4:56 PM, "Glen Langston" wrote: > > > >> Thanks for your explanation. > >> > >> ssh-ing in as root did work fine. > >> > >> I find that the rtl_ programs do work, like rtl_fm. > >> > >> I also understand your approach to embedded real-time applications. > >> > >> This probably works particularly well for the PlutoSDR. > >> > >> My goal is for student use, where they are particularly graphical > >> user interface aware. > >> > >> Best regards > >> > >> Glen > >> > >>> On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: > >>> > >>> It is indeed my belief that there is no point in running a graphical > user > >>> interface on an embedded system, much less a windowing system. If an > embedded > >>> board is supposed to interact with a user, a Qt5 or SDL dedicated > interface > >>> will be much lighter and efficient than a X-Window server and a window > manager > >>> client. > >>> > >>> This is the reason for providing the examples at the end of the > tutorial > >>> where a Non GUI flowgraph is generated, the resulting Python script > sent to > >>> the embedded board and running there, possibly streaming the output > (in my > >>> example 0-MQ) to a client. In the case of gr-acars, I just fetch > periodically > >>> the log-file from the RPi4 to the host computer for analysis. > >>> > >>> Nevertheless if you want to go in the windowing system direction, > Buildroot > >>> seems to provide Xorg support: > >>> > >>> make menuconfig > >>> Target packages -> Graphic libraries and applications -> X.org X > Window System > >>> > >>> I have never used nor tested, so I have no idea how much space/how > long it takes > >>> to compile. > >>> > >>> There is no binary package management system with buildroot: the whole > point, which > >>> makes is different from OpenEmbedded/Yocto, is to generate a custom > minimal > >>> image with only the needed tools and not compile all possible binary > packages > >>> (the disk size difference being about 10-fold, with about 8 GB needed > for > >>> buildroot when my attempt at completing the OpenEmbedded system ended > at about > >>> 80 GB and many unnecessary binary packages). > >>> > >>> The default network configuration is to fetch the IP address from a > DHCP server. > >>> Otherwise add an
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Jean-Michel, don't apologize for sharing your technically shaped view on things. I, too, would look at an RPi4 as embedded device! But that is because my use ways of thinking are much more in terms of "do GUI-ish stuff on a PC/laptop, number crunching on a PC/workstation/server, and only exactly what needs to be done there on an embedded platform". I can see how if you want to write letters or browse the web, a low/medium-end smartphone-powered computer works for you. And, sure enough, low/medium-rate signal processing, why not; if I need things to demodulate something in the kHz range and display something simple, OK, why not wayland/Mutter, X11/XFCE or whatever. Regarding suboptimality: yep, Raspbian is a 32bit ARM debian-derivative distro "same binary for all RPi generations", and they literally build-on-target, and although the very few people behind it very critical for establishing the RPi as "the" Linux SBC, they've not really received any official support from the Pi foundation; do with that info what you will. The Raspbian person I've had contact was super nice, and he helped me understand how GNU Radio works under these situations. He was happy to hear how VOLK worked. Nice guy. Raspberry Pi OS is a more directly derived debian (currently, based on Debian 11), and as far as I know it uses sensible architectural settings for the RPi4. That means you should be able to "apt install gnuradio" and run "volk_profile" right there. I don't have an RPi4, so can't test. Last time I checked (that's already a while back) they still haven't put together an officially sanctioned QEMU aarch64 target with enough device tree to emulate a headless RPi. I honestly think that unless you're doing something *very* specific chances are, you'll never have to use a self-built GNU Radio on a RPi these days; and I've been asking people not to build on target forever, not the least to save them the pain. Best regards, Marucs On 29.05.20 17:07, jean-michel.fri...@femto-st.fr wrote: apologies to the list then, I was not aware of the use of RPi as desktop computer, and have always been obsessed with optimization of resources for embedded systems. Most probably for a desktop use, a sub-optimal binary distribution such as Raspbian is best suited indeed, as we find daily on our personal computers. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 4:56 PM, "Glen Langston" wrote: Thanks for your explanation. ssh-ing in as root did work fine. I find that the rtl_ programs do work, like rtl_fm. I also understand your approach to embedded real-time applications. This probably works particularly well for the PlutoSDR. My goal is for student use, where they are particularly graphical user interface aware. Best regards Glen On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: It is indeed my belief that there is no point in running a graphical user interface on an embedded system, much less a windowing system. If an embedded board is supposed to interact with a user, a Qt5 or SDL dedicated interface will be much lighter and efficient than a X-Window server and a window manager client. This is the reason for providing the examples at the end of the tutorial where a Non GUI flowgraph is generated, the resulting Python script sent to the embedded board and running there, possibly streaming the output (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically the log-file from the RPi4 to the host computer for analysis. Nevertheless if you want to go in the windowing system direction, Buildroot seems to provide Xorg support: make menuconfig Target packages -> Graphic libraries and applications -> X.org X Window System I have never used nor tested, so I have no idea how much space/how long it takes to compile. There is no binary package management system with buildroot: the whole point, which makes is different from OpenEmbedded/Yocto, is to generate a custom minimal image with only the needed tools and not compile all possible binary packages (the disk size difference being about 10-fold, with about 8 GB needed for buildroot when my attempt at completing the OpenEmbedded system ended at about 80 GB and many unnecessary binary packages). The default network configuration is to fetch the IP address from a DHCP server. Otherwise add an etc/network/interfaces entry in the output/target directory of buildroot with the static IP configuration, and make to re-generate sdcard.img including this configuration file. Similarly if the usr/share/uhd/images binary files are needed: copy in output/target and make. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 3:33 AM, "Glen Langston" wrote: Hi Thanks for your help. I’ve written the image to an SDCARD and the PI4 boots to the command line prompt. The password is accepted and I’ve
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Glen - I'm late to the party. but I presume you have buster (debian 10) installed - see /etc/os-release. I don't own a raspberry pi 4 but I know someone who does and they recommend using following guide to upgrade to bullseye (debian 11) https://www.tomshardware.com/how-to/upgrade-raspberry-pi-os-to-bullseye-from-buster bullseye (debian 10) comes with gnuradio 3.8. If you need to use buster (debian 10) and gnuradio3.8, then you have to build it from source. -- Cinaed On 5/24/20 12:50, Glen I Langston wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi, Just to announce both gr-qtgui[1] and gr-dtv[2] are now supported by gnuradio package in buildroot. Best regards Gwen [1] https://git.buildroot.net/buildroot/commit/?id=494d7f4a12e8c33afac583c1b641a81d28c48ee3 [2] https://git.buildroot.net/buildroot/commit/?id=c878facaf807dd6f1ab5ad50dc8a3667c3d146dd On Sat, 30 May 2020 07:48:02 +0200 Gwenhael Goavec-Merou wrote: > Hi, > On Fri, 29 May 2020 14:48:48 -0700 > Ron Economos wrote: > > > There is some middle ground. On my Beagleboard X-15, I use a stripped > > down console only version of Ubuntu 18.04 and ssh (with X11 forwarding) > > in from another host. Kernel support is awesome with 4.14, 4.19 and 5.4 > > available along with real-time compiled versions. > > > > I've been using a Samsung EVO 128 GB microSD card for a year and half > > now with no problems. For 32-bit testing, I've compiled GNU Radio many > > many (100's ?) times on that card. > > > > I was disappointed to see that the Digital Television component was > > missing on the buildroot version of GNU Radio. The X-15 is (just barely) > > capable of running the DVB-T2 transmitter at 5 MHz bandwidth, which I > > consider phenomenal. A RPi4 should do a little better. > > > I have not added gr-dtv more or less because I haven't tested this one. But it > always possible to add this and to contribue by sending to the mailing list. > > It's the same for gr-qtgui, I'm working to re-add (this option from buildroot > was dropped in the same time as qt4 before gnuradio 3.8 upgrade). > > Gwen > > > Ron > > > > On 5/29/20 08:07, jean-michel.fri...@femto-st.fr wrote: > > > apologies to the list then, I was not aware of the use of RPi as > > > desktop computer, and have always been obsessed with optimization > > > of resources for embedded systems. Most probably for a desktop use, > > > a sub-optimal binary distribution such as Raspbian is best suited indeed, > > > as we find daily on our personal computers. > > > > > > JM > > > > > > -- > > > JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > > > 25000 Besancon, France > > > > > > May 29, 2020 4:56 PM, "Glen Langston" wrote: > > > > > >> Thanks for your explanation. > > >> > > >> ssh-ing in as root did work fine. > > >> > > >> I find that the rtl_ programs do work, like rtl_fm. > > >> > > >> I also understand your approach to embedded real-time applications. > > >> > > >> This probably works particularly well for the PlutoSDR. > > >> > > >> My goal is for student use, where they are particularly graphical > > >> user interface aware. > > >> > > >> Best regards > > >> > > >> Glen > > >> > > >>> On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: > > >>> > > >>> It is indeed my belief that there is no point in running a graphical > > >>> user interface on an embedded system, much less a windowing system. If > > >>> an embedded board is supposed to interact with a user, a Qt5 or SDL > > >>> dedicated interface will be much lighter and efficient than a X-Window > > >>> server and a window manager client. > > >>> > > >>> This is the reason for providing the examples at the end of the tutorial > > >>> where a Non GUI flowgraph is generated, the resulting Python script sent > > >>> to the embedded board and running there, possibly streaming the output > > >>> (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch > > >>> periodically the log-file from the RPi4 to the host computer for > > >>> analysis. > > >>> > > >>> Nevertheless if you want to go in the windowing system direction, > > >>> Buildroot seems to provide Xorg support: > > >>> > > >>> make menuconfig > > >>> Target packages -> Graphic libraries and applications -> X.org X Window > > >>> System > > >>> > > >>> I have never used nor tested, so I have no idea how much space/how long > > >>> it takes to compile. > > >>> > > >>> There is no binary package management system with buildroot: the whole > > >>> point, which makes is different from OpenEmbedded/Yocto, is to generate > > >>> a custom minimal image with only the needed tools and not compile all > > >>> possible binary packages (the disk size difference being about 10-fold, > > >>> with about 8 GB needed for buildroot when my attempt at completing the > > >>> OpenEmbedded system ended at about 80 GB and many unnecessary binary > > >>> packages). > > >>> > > >>> The default network configuration is to fetch the IP address from a DHCP > > >>> server. Otherwise add an etc/network/interfaces entry in the > > >>> output/target directory of buildroot with the static IP configuration, > > >>> and make > > >>> to re-generate sdcard.img including this configuration file. Similarly > > >>> if the usr/share/uhd/images binary files are needed: copy in > > >>> output/target and make. > > >>> > > >>> JM > > >>> > > >>> -- > > >>> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > > >>> 25000 Besancon, France > > >>> > > >>> May 29, 2020 3:33 AM, "Glen
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi, On Fri, 29 May 2020 14:48:48 -0700 Ron Economos wrote: > There is some middle ground. On my Beagleboard X-15, I use a stripped > down console only version of Ubuntu 18.04 and ssh (with X11 forwarding) > in from another host. Kernel support is awesome with 4.14, 4.19 and 5.4 > available along with real-time compiled versions. > > I've been using a Samsung EVO 128 GB microSD card for a year and half > now with no problems. For 32-bit testing, I've compiled GNU Radio many > many (100's ?) times on that card. > > I was disappointed to see that the Digital Television component was > missing on the buildroot version of GNU Radio. The X-15 is (just barely) > capable of running the DVB-T2 transmitter at 5 MHz bandwidth, which I > consider phenomenal. A RPi4 should do a little better. > I have not added gr-dtv more or less because I haven't tested this one. But it always possible to add this and to contribue by sending to the mailing list. It's the same for gr-qtgui, I'm working to re-add (this option from buildroot was dropped in the same time as qt4 before gnuradio 3.8 upgrade). Gwen > Ron > > On 5/29/20 08:07, jean-michel.fri...@femto-st.fr wrote: > > apologies to the list then, I was not aware of the use of RPi as > > desktop computer, and have always been obsessed with optimization > > of resources for embedded systems. Most probably for a desktop use, > > a sub-optimal binary distribution such as Raspbian is best suited indeed, > > as we find daily on our personal computers. > > > > JM > > > > -- > > JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > > 25000 Besancon, France > > > > May 29, 2020 4:56 PM, "Glen Langston" wrote: > > > >> Thanks for your explanation. > >> > >> ssh-ing in as root did work fine. > >> > >> I find that the rtl_ programs do work, like rtl_fm. > >> > >> I also understand your approach to embedded real-time applications. > >> > >> This probably works particularly well for the PlutoSDR. > >> > >> My goal is for student use, where they are particularly graphical > >> user interface aware. > >> > >> Best regards > >> > >> Glen > >> > >>> On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: > >>> > >>> It is indeed my belief that there is no point in running a graphical user > >>> interface on an embedded system, much less a windowing system. If an > >>> embedded board is supposed to interact with a user, a Qt5 or SDL > >>> dedicated interface will be much lighter and efficient than a X-Window > >>> server and a window manager client. > >>> > >>> This is the reason for providing the examples at the end of the tutorial > >>> where a Non GUI flowgraph is generated, the resulting Python script sent > >>> to the embedded board and running there, possibly streaming the output > >>> (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch > >>> periodically the log-file from the RPi4 to the host computer for analysis. > >>> > >>> Nevertheless if you want to go in the windowing system direction, > >>> Buildroot seems to provide Xorg support: > >>> > >>> make menuconfig > >>> Target packages -> Graphic libraries and applications -> X.org X Window > >>> System > >>> > >>> I have never used nor tested, so I have no idea how much space/how long > >>> it takes to compile. > >>> > >>> There is no binary package management system with buildroot: the whole > >>> point, which makes is different from OpenEmbedded/Yocto, is to generate a > >>> custom minimal image with only the needed tools and not compile all > >>> possible binary packages (the disk size difference being about 10-fold, > >>> with about 8 GB needed for buildroot when my attempt at completing the > >>> OpenEmbedded system ended at about 80 GB and many unnecessary binary > >>> packages). > >>> > >>> The default network configuration is to fetch the IP address from a DHCP > >>> server. Otherwise add an etc/network/interfaces entry in the > >>> output/target directory of buildroot with the static IP configuration, and > >>> make > >>> to re-generate sdcard.img including this configuration file. Similarly if > >>> the usr/share/uhd/images binary files are needed: copy in output/target > >>> and make. > >>> > >>> JM > >>> > >>> -- > >>> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > >>> 25000 Besancon, France > >>> > >>> May 29, 2020 3:33 AM, "Glen Langston" wrote: > >>> > Hi > > Thanks for your help. > > I’ve written the image to an SDCARD and the PI4 boots to > the command line prompt. The password is accepted and > I’ve looked around. > > Gnuradio seems to be installed, but not the xwindow system. > > How do you use gnuradio-companion etc? > > I could not find “xstartup” or some such program. > > Thanks > > Glen > >>> On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: > >>> > >>> I have uploaded http://jmfriedt.org/sdcard.img > >>> my Buildroot
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
There is some middle ground. On my Beagleboard X-15, I use a stripped down console only version of Ubuntu 18.04 and ssh (with X11 forwarding) in from another host. Kernel support is awesome with 4.14, 4.19 and 5.4 available along with real-time compiled versions. I've been using a Samsung EVO 128 GB microSD card for a year and half now with no problems. For 32-bit testing, I've compiled GNU Radio many many (100's ?) times on that card. I was disappointed to see that the Digital Television component was missing on the buildroot version of GNU Radio. The X-15 is (just barely) capable of running the DVB-T2 transmitter at 5 MHz bandwidth, which I consider phenomenal. A RPi4 should do a little better. Ron On 5/29/20 08:07, jean-michel.fri...@femto-st.fr wrote: apologies to the list then, I was not aware of the use of RPi as desktop computer, and have always been obsessed with optimization of resources for embedded systems. Most probably for a desktop use, a sub-optimal binary distribution such as Raspbian is best suited indeed, as we find daily on our personal computers. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 4:56 PM, "Glen Langston" wrote: Thanks for your explanation. ssh-ing in as root did work fine. I find that the rtl_ programs do work, like rtl_fm. I also understand your approach to embedded real-time applications. This probably works particularly well for the PlutoSDR. My goal is for student use, where they are particularly graphical user interface aware. Best regards Glen On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: It is indeed my belief that there is no point in running a graphical user interface on an embedded system, much less a windowing system. If an embedded board is supposed to interact with a user, a Qt5 or SDL dedicated interface will be much lighter and efficient than a X-Window server and a window manager client. This is the reason for providing the examples at the end of the tutorial where a Non GUI flowgraph is generated, the resulting Python script sent to the embedded board and running there, possibly streaming the output (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically the log-file from the RPi4 to the host computer for analysis. Nevertheless if you want to go in the windowing system direction, Buildroot seems to provide Xorg support: make menuconfig Target packages -> Graphic libraries and applications -> X.org X Window System I have never used nor tested, so I have no idea how much space/how long it takes to compile. There is no binary package management system with buildroot: the whole point, which makes is different from OpenEmbedded/Yocto, is to generate a custom minimal image with only the needed tools and not compile all possible binary packages (the disk size difference being about 10-fold, with about 8 GB needed for buildroot when my attempt at completing the OpenEmbedded system ended at about 80 GB and many unnecessary binary packages). The default network configuration is to fetch the IP address from a DHCP server. Otherwise add an etc/network/interfaces entry in the output/target directory of buildroot with the static IP configuration, and make to re-generate sdcard.img including this configuration file. Similarly if the usr/share/uhd/images binary files are needed: copy in output/target and make. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 3:33 AM, "Glen Langston" wrote: Hi Thanks for your help. I’ve written the image to an SDCARD and the PI4 boots to the command line prompt. The password is accepted and I’ve looked around. Gnuradio seems to be installed, but not the xwindow system. How do you use gnuradio-companion etc? I could not find “xstartup” or some such program. Thanks Glen On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: I have uploaded http://jmfriedt.org/sdcard.img my Buildroot image generated for RPi4 that I have been using daily for the last 2 months, so pretty sure it is working. Actually it is 1.1 GB because of lapack needed for gnss-sdr but GNU Radio 3.8/Python3 will only require about 500 MB. Gwenhael Goavec-Merou ported all GNU Radio related software/libraries to Buildroot: the missing parts for gnss-sdr are found at https://github.com/oscimp/PlutoSDR in the for_next branch. root passwd=root, no user account, USRP FPGA images to be added in usr/share/uhd/images manually if libuhd is needed. Tested with RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 24, 2020 9:51 PM, "Glen I Langston" wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
apologies to the list then, I was not aware of the use of RPi as desktop computer, and have always been obsessed with optimization of resources for embedded systems. Most probably for a desktop use, a sub-optimal binary distribution such as Raspbian is best suited indeed, as we find daily on our personal computers. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 4:56 PM, "Glen Langston" wrote: > Thanks for your explanation. > > ssh-ing in as root did work fine. > > I find that the rtl_ programs do work, like rtl_fm. > > I also understand your approach to embedded real-time applications. > > This probably works particularly well for the PlutoSDR. > > My goal is for student use, where they are particularly graphical > user interface aware. > > Best regards > > Glen > >> On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: >> >> It is indeed my belief that there is no point in running a graphical user >> interface on an embedded system, much less a windowing system. If an embedded >> board is supposed to interact with a user, a Qt5 or SDL dedicated interface >> will be much lighter and efficient than a X-Window server and a window >> manager >> client. >> >> This is the reason for providing the examples at the end of the tutorial >> where a Non GUI flowgraph is generated, the resulting Python script sent to >> the embedded board and running there, possibly streaming the output (in my >> example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically >> the log-file from the RPi4 to the host computer for analysis. >> >> Nevertheless if you want to go in the windowing system direction, Buildroot >> seems to provide Xorg support: >> >> make menuconfig >> Target packages -> Graphic libraries and applications -> X.org X Window >> System >> >> I have never used nor tested, so I have no idea how much space/how long it >> takes >> to compile. >> >> There is no binary package management system with buildroot: the whole >> point, which >> makes is different from OpenEmbedded/Yocto, is to generate a custom minimal >> image with only the needed tools and not compile all possible binary packages >> (the disk size difference being about 10-fold, with about 8 GB needed for >> buildroot when my attempt at completing the OpenEmbedded system ended at >> about >> 80 GB and many unnecessary binary packages). >> >> The default network configuration is to fetch the IP address from a DHCP >> server. >> Otherwise add an etc/network/interfaces entry in the output/target directory >> of buildroot with the static IP configuration, and >> make >> to re-generate sdcard.img including this configuration file. Similarly if the >> usr/share/uhd/images binary files are needed: copy in output/target and make. >> >> JM >> >> -- >> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, >> 25000 Besancon, France >> >> May 29, 2020 3:33 AM, "Glen Langston" wrote: >> >>> Hi >>> >>> Thanks for your help. >>> >>> I’ve written the image to an SDCARD and the PI4 boots to >>> the command line prompt. The password is accepted and >>> I’ve looked around. >>> >>> Gnuradio seems to be installed, but not the xwindow system. >>> >>> How do you use gnuradio-companion etc? >>> >>> I could not find “xstartup” or some such program. >>> >>> Thanks >>> >>> Glen >> >> On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: >> >> I have uploaded http://jmfriedt.org/sdcard.img >> my Buildroot image generated for RPi4 that I have been >> using daily for the last 2 months, so pretty sure it is >> working. Actually it is 1.1 GB because of lapack needed >> for gnss-sdr but GNU Radio 3.8/Python3 will only require >> about 500 MB. >> Gwenhael Goavec-Merou ported all GNU Radio related software/libraries >> to Buildroot: the missing parts for gnss-sdr are found at >> https://github.com/oscimp/PlutoSDR in the for_next branch. >> >> root passwd=root, no user account, USRP FPGA images to be added >> in usr/share/uhd/images manually if libuhd is needed. Tested with >> RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. >> >> JM >> >> -- >> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, >> 25000 Besancon, France >> >> May 24, 2020 9:51 PM, "Glen I Langston" wrote: >> >> Hello >> >> I’ve been a great proponent of gnuradio, but I’m finding in >> increasing difficult to do anything new, as installation of 3.8 is >> essentially impossible for most people. >> >> I’ve written and built my own python modules and C++ blocks. >> >> However, despite months of trying now, I can not get 3.8 to install >> on a raspberry pi. >> >> Has anyone achieved 3.8 on a raspberry pi? >> >> If so can you please save the entire OS, gzip compressed and put it >> online somewhere. It will probably be about 3 GB compressed. >> >> Thanks >> >> Glen >> >> Note that there are many many (too many) different guides on line >>
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Thanks for your explanation. ssh-ing in as root did work fine. I find that the rtl_ programs do work, like rtl_fm. I also understand your approach to embedded real-time applications. This probably works particularly well for the PlutoSDR. My goal is for student use, where they are particularly graphical user interface aware. Best regards Glen > On May 29, 2020, at 1:57 AM, jean-michel.fri...@femto-st.fr wrote: > > It is indeed my belief that there is no point in running a graphical user > interface on an embedded system, much less a windowing system. If an embedded > board is supposed to interact with a user, a Qt5 or SDL dedicated interface > will be much lighter and efficient than a X-Window server and a window manager > client. > > This is the reason for providing the examples at the end of the tutorial > where a Non GUI flowgraph is generated, the resulting Python script sent to > the embedded board and running there, possibly streaming the output (in my > example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically > the log-file from the RPi4 to the host computer for analysis. > > Nevertheless if you want to go in the windowing system direction, Buildroot > seems to provide Xorg support: > > make menuconfig > Target packages -> Graphic libraries and applications -> X.org X Window System > > I have never used nor tested, so I have no idea how much space/how long it > takes > to compile. > > There is no binary package management system with buildroot: the whole point, > which > makes is different from OpenEmbedded/Yocto, is to generate a custom minimal > image with only the needed tools and not compile all possible binary packages > (the disk size difference being about 10-fold, with about 8 GB needed for > buildroot when my attempt at completing the OpenEmbedded system ended at about > 80 GB and many unnecessary binary packages). > > The default network configuration is to fetch the IP address from a DHCP > server. > Otherwise add an etc/network/interfaces entry in the output/target directory > of buildroot with the static IP configuration, and > make > to re-generate sdcard.img including this configuration file. Similarly if the > usr/share/uhd/images binary files are needed: copy in output/target and make. > > JM > > -- > JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > 25000 Besancon, France > > May 29, 2020 3:33 AM, "Glen Langston" wrote: > >> Hi >> >> Thanks for your help. >> >> I’ve written the image to an SDCARD and the PI4 boots to >> the command line prompt. The password is accepted and >> I’ve looked around. >> >> Gnuradio seems to be installed, but not the xwindow system. >> >> How do you use gnuradio-companion etc? >> >> I could not find “xstartup” or some such program. >> >> Thanks >> >> Glen >> >>> On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: >>> >>> I have uploaded http://jmfriedt.org/sdcard.img >>> my Buildroot image generated for RPi4 that I have been >>> using daily for the last 2 months, so pretty sure it is >>> working. Actually it is 1.1 GB because of lapack needed >>> for gnss-sdr but GNU Radio 3.8/Python3 will only require >>> about 500 MB. >>> Gwenhael Goavec-Merou ported all GNU Radio related software/libraries >>> to Buildroot: the missing parts for gnss-sdr are found at >>> https://github.com/oscimp/PlutoSDR in the for_next branch. >>> >>> root passwd=root, no user account, USRP FPGA images to be added >>> in usr/share/uhd/images manually if libuhd is needed. Tested with >>> RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. >>> >>> JM >>> >>> -- >>> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, >>> 25000 Besancon, France >>> >>> May 24, 2020 9:51 PM, "Glen I Langston" wrote: >>> Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
To whom it may concern: Just want to mention: Raspberry Pi 4 is actually fast enough to replace low-end x86 desktops (if you provide it a fast storage device), and they actually advertise their boards as a low-power desktop replacement (in their official adverts). So, I don't see much problems in using Raspberry Pi with X11 GUI applications. It's just a different use case for the board. Some use it as an embedded board, while some use it as a low-power mini PC. Regards, Kyeong Su Shin 보낸 사람: jean-michel.fri...@femto-st.fr 대신 Discuss-gnuradio 보낸 날짜: 2020년 5월 29일 금요일 오후 2:57 받는 사람: Glen Langston 참조: GNURadio Discussion List 제목: Re: Gnuradio 3.8 on a Raspberry pi 4 B? It is indeed my belief that there is no point in running a graphical user interface on an embedded system, much less a windowing system. If an embedded board is supposed to interact with a user, a Qt5 or SDL dedicated interface will be much lighter and efficient than a X-Window server and a window manager client. This is the reason for providing the examples at the end of the tutorial where a Non GUI flowgraph is generated, the resulting Python script sent to the embedded board and running there, possibly streaming the output (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically the log-file from the RPi4 to the host computer for analysis. Nevertheless if you want to go in the windowing system direction, Buildroot seems to provide Xorg support: make menuconfig Target packages -> Graphic libraries and applications -> X.org X Window System I have never used nor tested, so I have no idea how much space/how long it takes to compile. There is no binary package management system with buildroot: the whole point, which makes is different from OpenEmbedded/Yocto, is to generate a custom minimal image with only the needed tools and not compile all possible binary packages (the disk size difference being about 10-fold, with about 8 GB needed for buildroot when my attempt at completing the OpenEmbedded system ended at about 80 GB and many unnecessary binary packages). The default network configuration is to fetch the IP address from a DHCP server. Otherwise add an etc/network/interfaces entry in the output/target directory of buildroot with the static IP configuration, and make to re-generate sdcard.img including this configuration file. Similarly if the usr/share/uhd/images binary files are needed: copy in output/target and make. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 3:33 AM, "Glen Langston" wrote: > Hi > > Thanks for your help. > > I’ve written the image to an SDCARD and the PI4 boots to > the command line prompt. The password is accepted and > I’ve looked around. > > Gnuradio seems to be installed, but not the xwindow system. > > How do you use gnuradio-companion etc? > > I could not find “xstartup” or some such program. > > Thanks > > Glen > >> On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: >> >> I have uploaded http://jmfriedt.org/sdcard.img >> my Buildroot image generated for RPi4 that I have been >> using daily for the last 2 months, so pretty sure it is >> working. Actually it is 1.1 GB because of lapack needed >> for gnss-sdr but GNU Radio 3.8/Python3 will only require >> about 500 MB. >> Gwenhael Goavec-Merou ported all GNU Radio related software/libraries >> to Buildroot: the missing parts for gnss-sdr are found at >> https://github.com/oscimp/PlutoSDR in the for_next branch. >> >> root passwd=root, no user account, USRP FPGA images to be added >> in usr/share/uhd/images manually if libuhd is needed. Tested with >> RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. >> >> JM >> >> -- >> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, >> 25000 Besancon, France >> >> May 24, 2020 9:51 PM, "Glen I Langston" wrote: >> >>> Hello >>> >>> I’ve been a great proponent of gnuradio, but I’m finding in >>> increasing difficult to do anything new, as installation of 3.8 is >>> essentially impossible for most people. >>> >>> I’ve written and built my own python modules and C++ blocks. >>> >>> However, despite months of trying now, I can not get 3.8 to install >>> on a raspberry pi. >>> >>> Has anyone achieved 3.8 on a raspberry pi? >>> >>> If so can you please save the entire OS, gzip compressed and put it >>> online somewhere. It will probably be about 3 GB compressed. >>> >>> Thanks >>> >>> Glen >>> >>> Note that there are many many (too many) different guides on line >>> >>> 1) apt-get >>> >>> 2) pybombs >>> >>> 3) git clone then build >>> >>> each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
It is indeed my belief that there is no point in running a graphical user interface on an embedded system, much less a windowing system. If an embedded board is supposed to interact with a user, a Qt5 or SDL dedicated interface will be much lighter and efficient than a X-Window server and a window manager client. This is the reason for providing the examples at the end of the tutorial where a Non GUI flowgraph is generated, the resulting Python script sent to the embedded board and running there, possibly streaming the output (in my example 0-MQ) to a client. In the case of gr-acars, I just fetch periodically the log-file from the RPi4 to the host computer for analysis. Nevertheless if you want to go in the windowing system direction, Buildroot seems to provide Xorg support: make menuconfig Target packages -> Graphic libraries and applications -> X.org X Window System I have never used nor tested, so I have no idea how much space/how long it takes to compile. There is no binary package management system with buildroot: the whole point, which makes is different from OpenEmbedded/Yocto, is to generate a custom minimal image with only the needed tools and not compile all possible binary packages (the disk size difference being about 10-fold, with about 8 GB needed for buildroot when my attempt at completing the OpenEmbedded system ended at about 80 GB and many unnecessary binary packages). The default network configuration is to fetch the IP address from a DHCP server. Otherwise add an etc/network/interfaces entry in the output/target directory of buildroot with the static IP configuration, and make to re-generate sdcard.img including this configuration file. Similarly if the usr/share/uhd/images binary files are needed: copy in output/target and make. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 29, 2020 3:33 AM, "Glen Langston" wrote: > Hi > > Thanks for your help. > > I’ve written the image to an SDCARD and the PI4 boots to > the command line prompt. The password is accepted and > I’ve looked around. > > Gnuradio seems to be installed, but not the xwindow system. > > How do you use gnuradio-companion etc? > > I could not find “xstartup” or some such program. > > Thanks > > Glen > >> On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: >> >> I have uploaded http://jmfriedt.org/sdcard.img >> my Buildroot image generated for RPi4 that I have been >> using daily for the last 2 months, so pretty sure it is >> working. Actually it is 1.1 GB because of lapack needed >> for gnss-sdr but GNU Radio 3.8/Python3 will only require >> about 500 MB. >> Gwenhael Goavec-Merou ported all GNU Radio related software/libraries >> to Buildroot: the missing parts for gnss-sdr are found at >> https://github.com/oscimp/PlutoSDR in the for_next branch. >> >> root passwd=root, no user account, USRP FPGA images to be added >> in usr/share/uhd/images manually if libuhd is needed. Tested with >> RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. >> >> JM >> >> -- >> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, >> 25000 Besancon, France >> >> May 24, 2020 9:51 PM, "Glen I Langston" wrote: >> >>> Hello >>> >>> I’ve been a great proponent of gnuradio, but I’m finding in >>> increasing difficult to do anything new, as installation of 3.8 is >>> essentially impossible for most people. >>> >>> I’ve written and built my own python modules and C++ blocks. >>> >>> However, despite months of trying now, I can not get 3.8 to install >>> on a raspberry pi. >>> >>> Has anyone achieved 3.8 on a raspberry pi? >>> >>> If so can you please save the entire OS, gzip compressed and put it >>> online somewhere. It will probably be about 3 GB compressed. >>> >>> Thanks >>> >>> Glen >>> >>> Note that there are many many (too many) different guides on line >>> >>> 1) apt-get >>> >>> 2) pybombs >>> >>> 3) git clone then build >>> >>> each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Glen - try typing apt list --installed | grep xorg to check if it's installed. It could be a /boot/boot.ini thing. I had odroid running debian 8 where I had to install X11 by hand. I enclosed a tar file with a script for install X11 which should work well enough to get you going. -- Cinaed On 5/28/20 6:33 PM, Glen Langston wrote: Hi Thanks for your help. I’ve written the image to an SDCARD and the PI4 boots to the command line prompt. The password is accepted and I’ve looked around. Gnuradio seems to be installed, but not the xwindow system. How do you use gnuradio-companion etc? I could not find “xstartup” or some such program. Thanks Glen On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: I have uploaded http://jmfriedt.org/sdcard.img my Buildroot image generated for RPi4 that I have been using daily for the last 2 months, so pretty sure it is working. Actually it is 1.1 GB because of lapack needed for gnss-sdr but GNU Radio 3.8/Python3 will only require about 500 MB. Gwenhael Goavec-Merou ported all GNU Radio related software/libraries to Buildroot: the missing parts for gnss-sdr are found at https://github.com/oscimp/PlutoSDR in the for_next branch. root passwd=root, no user account, USRP FPGA images to be added in usr/share/uhd/images manually if libuhd is needed. Tested with RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 24, 2020 9:51 PM, "Glen I Langston" wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way. x11.tar Description: Unix tar archive
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
This is just a guess, but it's probably intended to be remotely accessed with ssh. Try: ssh -Y username@host The -Y enables X11 forwarding. After you log in to the remote host, try: gnuradio-companion Ron On 5/28/20 18:33, Glen Langston wrote: Hi Thanks for your help. I’ve written the image to an SDCARD and the PI4 boots to the command line prompt. The password is accepted and I’ve looked around. Gnuradio seems to be installed, but not the xwindow system. How do you use gnuradio-companion etc? I could not find “xstartup” or some such program. Thanks Glen On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: I have uploaded http://jmfriedt.org/sdcard.img my Buildroot image generated for RPi4 that I have been using daily for the last 2 months, so pretty sure it is working. Actually it is 1.1 GB because of lapack needed for gnss-sdr but GNU Radio 3.8/Python3 will only require about 500 MB. Gwenhael Goavec-Merou ported all GNU Radio related software/libraries to Buildroot: the missing parts for gnss-sdr are found at https://github.com/oscimp/PlutoSDR in the for_next branch. root passwd=root, no user account, USRP FPGA images to be added in usr/share/uhd/images manually if libuhd is needed. Tested with RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 24, 2020 9:51 PM, "Glen I Langston" wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Thanks for your help. I’ve written the image to an SDCARD and the PI4 boots to the command line prompt. The password is accepted and I’ve looked around. Gnuradio seems to be installed, but not the xwindow system. How do you use gnuradio-companion etc? I could not find “xstartup” or some such program. Thanks Glen > On May 24, 2020, at 3:59 PM, jean-michel.fri...@femto-st.fr wrote: > > I have uploaded http://jmfriedt.org/sdcard.img > my Buildroot image generated for RPi4 that I have been > using daily for the last 2 months, so pretty sure it is > working. Actually it is 1.1 GB because of lapack needed > for gnss-sdr but GNU Radio 3.8/Python3 will only require > about 500 MB. > Gwenhael Goavec-Merou ported all GNU Radio related software/libraries > to Buildroot: the missing parts for gnss-sdr are found at > https://github.com/oscimp/PlutoSDR in the for_next branch. > > root passwd=root, no user account, USRP FPGA images to be added > in usr/share/uhd/images manually if libuhd is needed. Tested with > RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. > > JM > > -- > JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, > 25000 Besancon, France > > May 24, 2020 9:51 PM, "Glen I Langston" wrote: > >> Hello >> >> I’ve been a great proponent of gnuradio, but I’m finding in >> increasing difficult to do anything new, as installation of 3.8 is >> essentially impossible for most people. >> >> I’ve written and built my own python modules and C++ blocks. >> >> However, despite months of trying now, I can not get 3.8 to install >> on a raspberry pi. >> >> Has anyone achieved 3.8 on a raspberry pi? >> >> If so can you please save the entire OS, gzip compressed and put it >> online somewhere. It will probably be about 3 GB compressed. >> >> Thanks >> >> Glen >> >> Note that there are many many (too many) different guides on line >> >> 1) apt-get >> >> 2) pybombs >> >> 3) git clone then build >> >> each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Barry, test qa_trellis #225 failed, only one of ~200. vy73 Harald DD0VS Am Mon, 25 May 2020 16:47:40 -0500 schrieb Barry Duggan : > Hi Harald, > > One of the 'make test' may not pass; it doesn't on the 3B+. It's a > math test, but I don't remember the number. It has not been a problem > for me. > > The 3B+ took about 4 hours, so the rPi 4 is quite a bit faster :) > > 73, > Barry Duggan KV4FV >
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Harald, One of the 'make test' may not pass; it doesn't on the 3B+. It's a math test, but I don't remember the number. It has not been a problem for me. The 3B+ took about 4 hours, so the rPi 4 is quite a bit faster :) 73, Barry Duggan KV4FV On 5/25/20 4:41 PM, Harald Fritzsche (DD0VS) wrote: Hello Barry, i confirm that with that description on https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi gnuradio was able to build following the instructions "From SOurce" in about 100minutes on a rPI 4 (2GB). I do not know, what was going wrong beginning of this year ... During writing test are running. 130/243 passed. My b200mini was runing with the newly build libuhd. make install i will do later. vy73 Harald DD0VS Am Mon, 25 May 2020 11:27:36 -0500 schrieb Barry Duggan : Hi Glen, I have done several installs of GR 3.8 on my rPi 3B+. Here is the procedure: https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi I don't have a rPi 4 yet, but am interested to know if that procedure fails on it. I am using 2020-02-13-raspbian-buster-full. Do not skip any steps! It takes about 4 hours. Regards,
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Dear Robert, i am not able to provide a usable SD-Image. I suggest to do the following: Got to: https://www.sdrplay.com/new-downloadable-sd-card-image-for-raspberry-pi4-and-sdrplay/ and pick the card prepared for SDR play (contains a complete gnuradio). This should contain Adalm-Pluto support (but im am not sure about it). This image provides Gr 3.7 but should be ok for testing. If this works, follow the instruction of Barry (you do not need to compile libuhd). Hope that helps a little. vy73 Harald DD0VS Am Mon, 25 May 2020 22:19:57 +0200 schrieb Robert Heerekop : > Dear all, > Thanks all for your joined efforts in a RPi4 built. > Please notice that we're highly interested in testing a > compiled/built RPi4 SD Card image. > If you have working RPi setup with eg Adalm-Pluto or SDR, we highly > appreciate if you can share! > Thanks and continue your good work! > '73 Robert > PE1MFU > > Op ma 25 mei 2020 21:08 schreef Harald Fritzsche (DD0VS) > : > > > Hello Barry, all, > > > > i confirm that 1. step from page: > > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > > building libuhd is working on a rPI4 (with 2GB). > > > > There is one change needed: > > > > The instruction: > > cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_INSTALL_PREFIX=/usr/local ../ > > > > must be extended like this: > > cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_CXX_FLAGS=-latomic > > -DCMAKE_INSTALL_PREFIX=/usr/local ../ > > (not sure whether this is the right list, maybe one can inform the > > usrp-list too) > > > > Thank you! > > > > Next is testing if hardware is detected. > > > > Than i will go to building GR38 what failed for me some month ago. > > > > vy73 > > Harald > > DD0VS > > > > Am Mon, 25 May 2020 11:27:36 -0500 > > schrieb Barry Duggan : > > > > > Hi Glen, > > > > > > I have done several installs of GR 3.8 on my rPi 3B+. Here is the > > > procedure: > > > > > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > > > > > > I don't have a rPi 4 yet, but am interested to know if that > > > procedure fails on it. I am using > > > 2020-02-13-raspbian-buster-full. Do not skip any steps! It takes > > > about 4 hours. > > > > > > Regards, > > > > > >
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hello Barry, i confirm that with that description on https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi gnuradio was able to build following the instructions "From SOurce" in about 100minutes on a rPI 4 (2GB). I do not know, what was going wrong beginning of this year ... During writing test are running. 130/243 passed. My b200mini was runing with the newly build libuhd. make install i will do later. vy73 Harald DD0VS Am Mon, 25 May 2020 11:27:36 -0500 schrieb Barry Duggan : > Hi Glen, > > I have done several installs of GR 3.8 on my rPi 3B+. Here is the > procedure: > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > > I don't have a rPi 4 yet, but am interested to know if that procedure > fails on it. I am using 2020-02-13-raspbian-buster-full. Do not skip > any steps! It takes about 4 hours. > > Regards,
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Dear all, Thanks all for your joined efforts in a RPi4 built. Please notice that we're highly interested in testing a compiled/built RPi4 SD Card image. If you have working RPi setup with eg Adalm-Pluto or SDR, we highly appreciate if you can share! Thanks and continue your good work! '73 Robert PE1MFU Op ma 25 mei 2020 21:08 schreef Harald Fritzsche (DD0VS) : > Hello Barry, all, > > i confirm that 1. step from page: > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > building libuhd is working on a rPI4 (with 2GB). > > There is one change needed: > > The instruction: > cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_INSTALL_PREFIX=/usr/local ../ > > must be extended like this: > cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_CXX_FLAGS=-latomic > -DCMAKE_INSTALL_PREFIX=/usr/local ../ > (not sure whether this is the right list, maybe one can inform the > usrp-list too) > > Thank you! > > Next is testing if hardware is detected. > > Than i will go to building GR38 what failed for me some month ago. > > vy73 > Harald > DD0VS > > Am Mon, 25 May 2020 11:27:36 -0500 > schrieb Barry Duggan : > > > Hi Glen, > > > > I have done several installs of GR 3.8 on my rPi 3B+. Here is the > > procedure: > > > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > > > > I don't have a rPi 4 yet, but am interested to know if that procedure > > fails on it. I am using 2020-02-13-raspbian-buster-full. Do not skip > > any steps! It takes about 4 hours. > > > > Regards, > > >
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hello Barry, all, i confirm that 1. step from page: https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi building libuhd is working on a rPI4 (with 2GB). There is one change needed: The instruction: cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_INSTALL_PREFIX=/usr/local ../ must be extended like this: cmake -DNEON_SIMD_ENABLE=OFF -DCMAKE_CXX_FLAGS=-latomic -DCMAKE_INSTALL_PREFIX=/usr/local ../ (not sure whether this is the right list, maybe one can inform the usrp-list too) Thank you! Next is testing if hardware is detected. Than i will go to building GR38 what failed for me some month ago. vy73 Harald DD0VS Am Mon, 25 May 2020 11:27:36 -0500 schrieb Barry Duggan : > Hi Glen, > > I have done several installs of GR 3.8 on my rPi 3B+. Here is the > procedure: > https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi > > I don't have a rPi 4 yet, but am interested to know if that procedure > fails on it. I am using 2020-02-13-raspbian-buster-full. Do not skip > any steps! It takes about 4 hours. > > Regards,
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
To put this concisely: nice. On 5/24/20 9:59 PM, jean-michel.fri...@femto-st.fr wrote: I have uploaded http://jmfriedt.org/sdcard.img my Buildroot image generated for RPi4 that I have been using daily for the last 2 months, so pretty sure it is working. Actually it is 1.1 GB because of lapack needed for gnss-sdr but GNU Radio 3.8/Python3 will only require about 500 MB. Gwenhael Goavec-Merou ported all GNU Radio related software/libraries to Buildroot: the missing parts for gnss-sdr are found at https://github.com/oscimp/PlutoSDR in the for_next branch. root passwd=root, no user account, USRP FPGA images to be added in usr/share/uhd/images manually if libuhd is needed. Tested with RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 24, 2020 9:51 PM, "Glen I Langston" wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
Hi Glen, I have done several installs of GR 3.8 on my rPi 3B+. Here is the procedure: https://wiki.gnuradio.org/index.php/InstallingGRFromSource_on_Raspberry_Pi I don't have a rPi 4 yet, but am interested to know if that procedure fails on it. I am using 2020-02-13-raspbian-buster-full. Do not skip any steps! It takes about 4 hours. Regards, -- Barry Duggan KV4FV On Sun, 24 May 2020 15:50:26 -0400, Glen I Langston wrote: Hello I’ve been a great proponent of gnuradio, but I’m finding in increasing difficult to do anything new, as installation of 3.8 is essentially impossible for most people. I’ve written and built my own python modules and C++ blocks. However, despite months of trying now, I can not get 3.8 to install on a raspberry pi. Has anyone achieved 3.8 on a raspberry pi? If so can you please save the entire OS, gzip compressed and put it online somewhere. It will probably be about 3 GB compressed. Thanks Glen Note that there are many many (too many) different guides on line 1) apt-get 2) pybombs 3) git clone then build each one fails in a different way.
Re: Gnuradio 3.8 on a Raspberry pi 4 B?
I have uploaded http://jmfriedt.org/sdcard.img my Buildroot image generated for RPi4 that I have been using daily for the last 2 months, so pretty sure it is working. Actually it is 1.1 GB because of lapack needed for gnss-sdr but GNU Radio 3.8/Python3 will only require about 500 MB. Gwenhael Goavec-Merou ported all GNU Radio related software/libraries to Buildroot: the missing parts for gnss-sdr are found at https://github.com/oscimp/PlutoSDR in the for_next branch. root passwd=root, no user account, USRP FPGA images to be added in usr/share/uhd/images manually if libuhd is needed. Tested with RTL-SDR DVB-T dongle, PlutoSDR (gr-iio) and B210. JM -- JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000 Besancon, France May 24, 2020 9:51 PM, "Glen I Langston" wrote: > Hello > > I’ve been a great proponent of gnuradio, but I’m finding in > increasing difficult to do anything new, as installation of 3.8 is > essentially impossible for most people. > > I’ve written and built my own python modules and C++ blocks. > > However, despite months of trying now, I can not get 3.8 to install > on a raspberry pi. > > Has anyone achieved 3.8 on a raspberry pi? > > If so can you please save the entire OS, gzip compressed and put it > online somewhere. It will probably be about 3 GB compressed. > > Thanks > > Glen > > Note that there are many many (too many) different guides on line > > 1) apt-get > > 2) pybombs > > 3) git clone then build > > each one fails in a different way.
