Re: [Discuss-gnuradio] complaints about missing volk.h

Hi Michael, Thanks for the explanation. In the end I reverted back to boost-1.69.0 which fixed the problem. I also tried adding 1.70 to the list in gnuradio/volk/cmake/Modules/VolkBoost.cmake as suggested by Chris Kuethe further up this thread but it did not help. My thanks to you both. Che

[Discuss-gnuradio] Missing Length Tag

Hello, I'm trying to solve a problem that when I start/stop my flowgraph to reconfigure recording to file, a fatal error regarding missing tag length is posted by the tagged stream to pdu block. This block follows a stream to tagged stream block. It's the problem that this person was having in t

Re: [Discuss-gnuradio] GTK related segmentation fault when running GRC

That appears to have done the trick! Thank you! If it happens again, I'll follow up, but hopefully you won't see any responses on this topic. Jason On 5/30/2019 2:45 PM, Müller, Marcus (CEL) wrote: Hi Jason, that backtrace didn't quite tell me anything, but then I googled the library in whi

Re: [Discuss-gnuradio] GTK related segmentation fault when running GRC

Hi Jason, that backtrace didn't quite tell me anything, but then I googled the library in which the segfault happens (gtk3-nocsd). The github page to that library literally describes it as "A hack to disable gtk+ 3 client side decoration"; the readme says it's automatically being preloaded into th

Re: [Discuss-gnuradio] GTK related segmentation fault when running GRC

I've the high level source of the problem, but not the root. If I simply change my Desktop from Mate to Ubuntu's default, then GRC runs fine and doesn't seg fault. So it seems there's something with Mate on Ubuntu that conflicts with something in gnuradio-companion causing it to seg fault, but I ha

Re: [Discuss-gnuradio] Received data rate for wifi_rx in gnuradio

Well, you could look at the raw data you've captured/processed from the Lime, and process a few milliseconds of that. Plot the amplitude, and you will see the bursts of the wifi transmitter. You can isolate a burst and determine the spectral bandwidth to bound the modulation rate, then do some

Re: [Discuss-gnuradio] ARM optimizations update

Hi, Of course, like I said in my previous emails, this is more of a scratch pad to see what's worth it and what's working. There will obviously be one commit per kernel per pull request. --Albin On Thu, May 30, 2019, 17:04 Andrej Rode wrote: > Hi Albin, > > just to throw in some snarky commen

Re: [Discuss-gnuradio] ARM optimizations update

Hi Albin, just to throw in some snarky comments. On Thu, 30 May 2019 16:20:44 +0200 Albin Stigö wrote: > I've finished ARM NEON SIMD optimization for 44 kernels which means > only 23 kernels (not often used) are now missing a NEON > implementation. I've checked on your progress a couple of we

[Discuss-gnuradio] ARM optimizations update

Hi, I've finished ARM NEON SIMD optimization for 44 kernels which means only 23 kernels (not often used) are now missing a NEON implementation. All of the kernels so far are written using compiler intrinsics which means they will compile on both arm 32 and 64 bit. I've experimented with aarch64 a

[Discuss-gnuradio] [GSoC19] The overall structure of Verilog simulation block

Hi all, I post a report to illustrate the structure of the Verilog simulation block, you can find it here(https://b0wen-hu.github.io/2019/05/29/GSoC-Structure-of-the-Verilog-simulation-block/). You can find i