Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
This is like the error I encountered and got past by having swap.
The kernel used then was built without swap.
A new kernel got way past that but I have run into another error near
the end which seems to suggest I need greater than 2GB of swap so I’m
adding another 2GB of swap.
[100%] Built target pygen_gnuradio_core_src_lib_swig_2dc10
Segmentation fault
make[2]: ***
[gr-digital/swig/CMakeFiles/_digital_swig.dir/digital_swigPYTHON_wrap.cxx.o]
Error 139
make[1]: *** [gr-digital/swig/CMakeFiles/_digital_swig.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs…
Linking CXX shared module _gnuradio_core_gengen.so
[100%] Built target _gnuradio_core_gengen
Linking CXX shared module _blocks_swig.so
[100%] Built target _blocks_swig
make: *** [all] Error 2
73 … Sid.
Hi,
Lately there have been several emails about installing GNU Radio on
Raspberry Pi and other ARM platforms. I tried to get it installed on the
Zedboard ARMv7, but I was unsuccessful, with the following error message:
Just from you nick, I would think that the zedboard in question is a
paralella prototype ?
Do you use the linaro image ?
I compiled it a couple of day ago for that platform.
cmake -Dhave_mfpu_neon=0 -DCMAKE_CXX_FLAGS:STRING="-march=armv7 -mfpu=vfp
-mfloat-abi=hard" -DCMAKE_C_FLAGS:STRING="-march=armv7 -mfpu=vfp
-mfloat-abi=hard" …/
The linaro image is not a hardfp image AFAIK, it’s a softfp eabi.
Also, why would you disable neon ??? the ARM core in the zynq has a
neon unit so you should use it.
I compiled it using those flags :
-DCMAKE_CXX_FLAGS:STRING="-mfpu=neon"
-DCMAKE_C_FLAGS:STRING="-mfpu=neon"
I also disabled python support because compiling the SWIG generated
files requires multi-Go of RAM and trying to use swap for it made each
SWIG file take hours to compile …
Cheers,
SylvainHi Doug,
On 26 March 2013 13:29, Douglas G. [email protected]
wrote:
Minor nit-pick: the Zedboard uses the Xilinx Zynq (dual ARM
Cortex-A9). If you’re curious about it, there is a website up at:
http://www.zedboard.org/
The Parallella prototype hardware is a Zedboard + FMC with 16 or
64-core Epiphany floating-point coprocessor [1], which is what I
suspect what Sylvain meant in his reply to Tommy.
Best,
Andrew
[1] For a picture see:
http://www.embecosm.com/2013/03/22/community-access-parallella-prototype/
–
Andrew B.
http://carrierdetect.com
On Tue, Mar 26, 2013 at 3:51 AM, Sylvain M. [email protected]
wrote:
Hi,
Lately there have been several emails about installing GNU Radio on
Raspberry Pi and other ARM platforms. I tried to get it installed on the
Zedboard ARMv7, but I was unsuccessful, with the following error message:Just from you nick, I would think that the zedboard in question is a
paralella prototype ?
Minor nit-pick: the Zedboard uses the Xilinx Zynq (dual ARM
Cortex-A9). If you’re curious about it, there is a website up at:
http://www.zedboard.org/
Cheers,
Sylvain
To address Tommy’s original question:
I don’t have a lot of help for you unfortunately - I’ve built
GNURadio for the ZC702 dev board (which is very similar to the
Zedboard - a full comparison is apparently available here:
http://www.zedboard.org/content/differences-between-zedboard-and-xilinx-zynq-7000-soc-zc702-evaluation-kit)
- but I never natively compile.
I use OpenEmbedded (technically OE-Core + meta-openembedded - which
has a GNURadio build recipe courtesy of Phil Balister, and pull in his
meta-zynq layer to target the ZC702 via his machine definition). This
lets me build on one of my x86_64 machines, and bring over the
cross-compiled binaries. I find it goes much faster this way, but it
does require some getting used to the OE environment. If you’re
interested in trying that system out, Phil has a pretty excellent
getting started guide at:
Since I don’t have direct experience with the Zedboard, all I’ll do
is point out that a quick google search shows that someone forked
Phil’s meta-zynq layer to provide a machine definition specific to the
Zedboard (also on GitHub: https://github.com/milosoftware/meta-zynq).
Otherwise I’m not sure what is causing your issue: I’m
cross-compiling with GCC 4.7.2 and not seeing any compile errors
(although I’ll note the last version of GNURadio I’ve built was 3.6.3)
- but perhaps you and Sid are seeing the same issue: running out of
available memory, in which case adding more via additional swap space
could solve the problem.
All that said - I’m glad to see other folks trying out the Zynq - it
strikes me as a very exciting platform for GNURadio-related work.
Good luck!
Doug
–
Doug G.
[email protected]
Adding another 2GB of swap allowed it to build and I used checkinstall
to produce a .deb file.
I installed the .deb package and have gnuradio-companion up and running.
BTW, platform is an ODROID-X.
73 … Sid.
4GB of swap on an SD card? I’m worried that that may wear out the SD
card, but I’ll give it a shot.
Sincerely,
Tommy James Tracy II
Ph.D Student
High Performance Low Power Lab
University of Virginia
Phone: 913-775-2241
Dear Sylvain,
Thank you! I wasn’t aware of the soft eabi. I’m going to try compiling
with the flags you have listed and maybe later come back to integrate
Java support if needed.
Sincerely,
Tommy James Tracy II
Ph.D Student
High Performance Low Power Lab
University of Virginia
Phone: 913-775-2241
On 26 Mar 2013 12:37, Philip B. wrote:
On 03/26/2013 12:29
PM, Tommy T. II wrote:4GB of swap on an SD card? I’m worried
that that may wear out the SD card, but I’ll give it a shot.No
other way to natively compile gnuradio on low ram systems.The good
news is there are only a couple of problem files.Philip
One could
presumably plug a USB-based hard drive into the E100, and swap from
that…
On 03/26/2013 12:29 PM, Tommy T. II wrote:
4GB of swap on an SD card? I’m worried that that may wear out the SD card, but
I’ll give it a shot.
No other way to natively compile gnuradio on low ram systems.
The good news is there are only a couple of problem files.
Philip