I recompiled the program with commenting out all non-multiply kernels(see attached). Still pegged out for 2 hours and still going. Do you know specifically which kernel relates to the multiply_cc function?
Thanks again, kyp From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom Rondeau Sent: Friday, February 15, 2013 1:09 PM To: Karl Petrow Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Work around for gr.multiply_cc( ) for non NEON enabled ARM devices On Fri, Feb 15, 2013 at 12:21 PM, Karl Petrow <kpet...@maritimeinfosystems.com<mailto:kpet...@maritimeinfosystems.com>> wrote: The Pi is having some problems running: sudo volk_profile It pegs out at 100% and I just cut it at 24 hours. I am going to reboot and run it on terminal only with it overclocked for the weekend, but do you have any other suggestions? I was really excited about Volk after reading up on it, but unfortunately it seems to be too much for the RPi. Thanks karl You can edit volk/apps/volk_profile.cc and change the the number of samples and iterations it runs for each kernel. The function call is (from volk/lib/qa_utils.h): #define VOLK_PROFILE(func, tol, scalar, len, iter, results) So len and iter can be decreased for your processor's needs. Tom From: trond...@trondeau.com<mailto:trond...@trondeau.com> [mailto:trond...@trondeau.com<mailto:trond...@trondeau.com>] On Behalf Of Tom Rondeau Sent: Thursday, February 14, 2013 10:42 AM To: Karl Petrow Cc: discuss-gnuradio@gnu.org<mailto:discuss-gnuradio@gnu.org> Subject: Re: [Discuss-gnuradio] Work around for gr.multiply_cc( ) for non NEON enabled ARM devices On Thu, Feb 14, 2013 at 10:08 AM, Karl Petrow <kpet...@maritimeinfosystems.com<mailto:kpet...@maritimeinfosystems.com>> wrote: Has anyone developed a work around for replacing gr.multiple_cc() to work on ARM devices that have to disable NEON in order to install? I have two lines in gr.ais that keep giving me overflow. Thanks ahead of time, karl You can turn it off. Have you run 'volk_profile' on the system, yet? If so, that would have generated a ~/.volk/volk_config. You can edit that file by hand to specify the architecture you want as 'generic' for whatever kernel is causing you trouble. This just runs a standard C for loop with no SIMD instructions (except whatever the compiler tries to do). Tom
volk_profile.cc
Description: volk_profile.cc
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
