[Discuss-gnuradio] 50Msps performance

I thought I'd try a simple 50Msps flow-graph with the latest Gnu Radio to see how well it now works. I've attached it. As you can see, it doesn't do very much. A UHD source, a single multiply, then a null sink. On a 6-core machine running at 3.2GHz, it gets overruns, nearly continuously.

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

Well, after a few restarts, here is my output. I did a fresh pull from git because I was getting some errors with missing *.h files in gruel/src/swig or something like that. Hope this helps! RUN_VOLK_TESTS: volk_32fc_32f_multiply_32fc_a Program received signal SIGSEGV, Segmentation fault. 0x

Re: [Discuss-gnuradio] set clock source not implemented in this version

On 03/16/2012 01:57 PM, sirjanselot wrote: > > Hello I am trying to synchronize two USRPs together using the MIMO cable. > > I tried to set the clock and time source to the MIMO cable and it says that > this feature is not available in this version. > > Is this true or am I missing something?

Re: [Discuss-gnuradio] moving common swig stuff to gruel?

On Fri, Mar 16, 2012 at 4:24 PM, Josh Blum wrote: > I suppose a common swig file in gruel would be the best place to have > this. The following commit is my attempt to create such a file and use > it throughout the code base, in this case gruel and gr-core. > > Common swig file for reference: > >

[Discuss-gnuradio] set clock source not implemented in this version

Hello I am trying to synchronize two USRPs together using the MIMO cable. I tried to set the clock and time source to the MIMO cable and it says that this feature is not available in this version. Is this true or am I missing something? How do this? -- Opening a USRP2/N-Series device... Trac

Re: [Discuss-gnuradio] moving common swig stuff to gruel?

I'll take a look at it. On Fri, Mar 16, 2012 at 13:24, Josh Blum wrote: > I suppose a common swig file in gruel would be the best place to have > this. The following commit is my attempt to create such a file and use > it throughout the code base, in this case gruel and gr-core. > > Common swig f

Re: [Discuss-gnuradio] Try to understand the stream in Gnu Radio

On Fri, Mar 16, 2012 at 3:28 PM, Zhonghua wrote: > ** > On 03/16/2012 06:37 PM, Tom Rondeau wrote: > > On Fri, Mar 16, 2012 at 8:41 AM, Zhonghua wrote: > >> Hi all, >> >> After a period of using gnu radio, I have a problem of how to understand >> the stream. I got an information from a literatur

[Discuss-gnuradio] moving common swig stuff to gruel?

I suppose a common swig file in gruel would be the best place to have this. The following commit is my attempt to create such a file and use it throughout the code base, in this case gruel and gr-core. Common swig file for reference: http://gnuradio.org/cgit/jblum.git/diff/gruel/src/swig/gruel_com

Re: [Discuss-gnuradio] Try to understand the stream in Gnu Radio

On 03/16/2012 06:37 PM, Tom Rondeau wrote: On Fri, Mar 16, 2012 at 8:41 AM, Zhonghua > wrote: Hi all, After a period of using gnu radio, I have a problem of how to understand the stream. I got an information from a literature says: 'From the high level p

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

On Fri, Mar 16, 2012 at 3:11 PM, Frederick Stevens wrote: > I've added your suggested changes. It will be an hour or so until > compilation is finished. Slackware CFLAGS or CXXFLAGS are usually -O2 by > default. > > Cheers, > > Fred > Thanks. GNU Radio resets these flag to -O3 right now, though

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

I've added your suggested changes. It will be an hour or so until compilation is finished. Slackware CFLAGS or CXXFLAGS are usually -O2 by default. Cheers, Fred On 03/16/2012 02:09 PM, Tom Rondeau wrote: On Fri, Mar 16, 2012 at 3:03 PM, Frederick Stevens mailto:sk8tesgr...@gmail.com>> wrote

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

On Fri, Mar 16, 2012 at 3:03 PM, Frederick Stevens wrote: > Here is the gcc info. It will take me a bit to re compile gnuradio but I > will turn on debugging in cmake. > > gcc (GCC) 4.5.2 > Copyright (C) 2010 Free Software Foundation, Inc. > This is free software; see the source for copying cond

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

Here is the gcc info. It will take me a bit to re compile gnuradio but I will turn on debugging in cmake. gcc (GCC) 4.5.2 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNES

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

Is your system a stock slack 13.37 32bits? >> OK, that's weird as hell. That's the generic implementation, which is >> just >> a std::complex multiply in a for loop. Can you give me your gcc version? >> >> --n >> > > > Yep, that shouldn't be a problem. Fred, can you also give us the > backtrace? >

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

On Fri, Mar 16, 2012 at 2:50 PM, Nick Foster wrote: > On Fri, Mar 16, 2012 at 11:42 AM, Frederick Stevens > wrote: > >> Rafael, >> >> Here is the output from gdb: >> >> RUN_VOLK_TESTS: volk_32fc_32f_multiply_32fc_a >> >> Program received signal SIGSEGV, Segmentation fault. >> 0xb7f2c6e0 in volk_

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

On Fri, Mar 16, 2012 at 11:42 AM, Frederick Stevens wrote: > Rafael, > > Here is the output from gdb: > > RUN_VOLK_TESTS: volk_32fc_32f_multiply_32fc_a > > Program received signal SIGSEGV, Segmentation fault. > 0xb7f2c6e0 in volk_32fc_32f_multiply_32fc_a_**generic () > from /home/fred/extras/gnu

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

Rafael, Here is the output from gdb: RUN_VOLK_TESTS: volk_32fc_32f_multiply_32fc_a Program received signal SIGSEGV, Segmentation fault. 0xb7f2c6e0 in volk_32fc_32f_multiply_32fc_a_generic () from /home/fred/extras/gnuradio/gnuradio/build/volk/lib/libvolk.so.0.0.0 Dump of assembler code fo

Re: [Discuss-gnuradio] Segfault

On Thu, Mar 15, 2012 at 19:58, Philip Balister wrote: > > Can you look carefully at what data is being passed to the driver? We > may need to range check the data before we use it in the driver. I had a look and it what I could find out so far is that offset=1276 and count=1. cheers -- Stefan O

[Discuss-gnuradio] No-go on the GSoC

Sorry gang, GNU Radio was not accepted as a mentor organization for the GSoC this year. I'm very disappointed, as I'm sure everyone who helped out here is, too. I thought we had great project ideas and application, but it apparently wasn't enough. Well, on to the next big thing! Tom _

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

Also using the gdb "disassemble" command you could trace which instruction raised the fault. Cheers, Rafael Diniz > > Well, that doesn't make me happy at all. Especially since we just patched > the release yesterday... > > Sounds like the AMD chip is handling something wrong (or differently) with

Re: [Discuss-gnuradio] Try to understand the stream in Gnu Radio

On Fri, Mar 16, 2012 at 8:41 AM, Zhonghua wrote: > Hi all, > > After a period of using gnu radio, I have a problem of how to understand > the stream. I got an information from a literature says: 'From the high > level point-of-view, infinite streams of data flow through the ports. At > the C++ le

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

On Fri, Mar 16, 2012 at 11:38 AM, Frederick Stevens wrote: > Hello, > > Not sure if this is the right place to post this but I have had this error > with 3.5.2 and later (git and 3.5.2.1) on Slackware 13.37 on a dual athlon > 32 bit machine. The problem is not present on an Intel Atom (32 bit dua

Re: [Discuss-gnuradio] Problem with new blocks

Sorry, last e-mail should have said, "Check out Martin's and Zhonghua's advice..." Cheers, Ben On Fri, Mar 16, 2012 at 10:17 AM, Ben Hilburn wrote: > Aha - you suspect a SWIG error? That may indeed be the issue. > > Check out Martin's advice, and let us know how it goes. Have you > generally

Re: [Discuss-gnuradio] Reference documents for the interpolation filter in the digital clock recovery block

On Fri, Mar 16, 2012 at 12:20 PM, Johnathan Corgan < jcor...@corganenterprises.com> wrote: > On Fri, Mar 16, 2012 at 05:36, Tom Rondeau wrote: > > > I'm afraid that's before my time. I'm not sure we have the corporate > > knowledge on that anymore. > > > > If you find a good paper to describe it,

Re: [Discuss-gnuradio] Problem with new blocks

Aha - you suspect a SWIG error? That may indeed be the issue. Check out Martin's advice, and let us know how it goes. Have you generally tested the SWIG for your class? Cheers, Ben On Fri, Mar 16, 2012 at 6:37 AM, Loic Danceg wrote: > Hi Ben > > Thank you for your help. > I am really familia

Re: [Discuss-gnuradio] Reference documents for the interpolation filter in the digital clock recovery block

On Fri, Mar 16, 2012 at 05:36, Tom Rondeau wrote: > I'm afraid that's before my time. I'm not sure we have the corporate > knowledge on that anymore. > > If you find a good paper to describe it, let me know and I'll put it into > the documentation like we've done elsewhere. A wee bit of archaelo

[Discuss-gnuradio] Segfault with volk on 32 bit AMD

Hello, Not sure if this is the right place to post this but I have had this error with 3.5.2 and later (git and 3.5.2.1) on Slackware 13.37 on a dual athlon 32 bit machine. The problem is not present on an Intel Atom (32 bit dual core) machine with exactly the same configuration and librarie

Re: [Discuss-gnuradio] Problem with new blocks

On 03/16/2012 02:37 PM, Loic Danceg wrote: Hi Ben Thank you for your help. I am really familiar with Python, i think is more an error with the file .i or another error but i don't find my error :-( Le 14 mars 2012 21:34, Ben Hilburn > a écrit : Loic - That is

Re: [Discuss-gnuradio] Problem with new blocks

On Tue, Mar 13, 2012 at 01:37:48PM -0300, Loic Danceg wrote: > Hi everybody! > > I try to create my own block in a current project (rfid). So there are > currently other blocks which works correctly. > I had create my file.cc, my file.h and add the part that i need to add in the > file rfid.i > >

Re: [Discuss-gnuradio] Problem with new blocks

Hi Ben Thank you for your help. I am really familiar with Python, i think is more an error with the file .i or another error but i don't find my error :-( Le 14 mars 2012 21:34, Ben Hilburn a écrit : > Loic - > > That is a Python error, telling you that your class 'rfid' doesn't have > the memb

[Discuss-gnuradio] Try to understand the stream in Gnu Radio

Hi all, After a period of using gnu radio, I have a problem of how to understand the stream. I got an information from a literature says: 'From the high level point-of-view, infinite streams of data flow through the ports. At the C++ level,streams are dealt with in convenient sized pieces, re

Re: [Discuss-gnuradio] Reference documents for the interpolation filter in the digital clock recovery block

On Wed, Mar 14, 2012 at 10:42 PM, Anh Duc Nguyen wrote: > Hi all, > > I am a new one to GnuRadio. Now I am studying some implemented techniques > in GnuRadio, one of them is the digital clock recovery. I would like to ask > you a question that what are the reference documents or papers you used f

Re: [Discuss-gnuradio] Trouble building (32-bit Linux, volk-related?)

On Fri, Mar 16, 2012 at 2:07 AM, Ian Cullinan wrote: > Hi all, > > I'm having trouble building gnuradio from git on my 32-bit Ubuntu 10.10 > machine. The error I'm getting is: > > $ make > [ 0%] Generating ../include/volk/volk.h, volk.c, > volk_init.h, ../include/volk/volk_typedefs.h, ../include/