USRP Embedded

Ettus research was showing this at the European Reconfigurable Radio 
Technology Workshop.

http://balister.dyndns.org:8008/~balister/img_0819.jpg

I'm working on the FPGA to ARM device driver for them.

Philip

libstdc++ error while building GNU Radio on Beagleboard.

Hi,

while building GNU radio on beagleboard , i encountered libstdc++ error, 
At first it was 
Cannot find libstdc++.so in /lib/ i copied libstdc++.so from /usr/lib/ to lib/ 
but the file was 0 bytes.
I didnt see this error again but then after doing make i got following error:

*****Error Log **************************************************************

libtool: link: ( cd ".libs" && rm -f "libgnuradio-core-qa.la" && ln -s 
"../libgnuradio-core-qa.la" "libgnuradio-core-qa.la" )
g++ -DHAVE_CONFIG_H -I. -I../../..   -I/usr/include -
I/home/root/gnuradio/gnuradio-core/src/lib/runtime -
I/home/root/gnuradio/gnuradio-core/src/lib/general c
mv -f .deps/gnuradio-config-info.Tpo .deps/gnuradio-config-info.Po
/bin/sh ../../../libtool --tag=CXX   --mode=link g++ -Wall -Woverloaded-virtual 
-march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -pthread   -o  
libtool: link: g++ -Wall -Woverloaded-virtual -march=armv7-a -mtune=cortex-a8 -
mfpu=neon -mfloat-abi=softfp -pthread -o .libs/gnuradio-config-info gnuradio-b
/usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../crt1.o: In function 
`_start':
init.c:(.text+0x2c): undefined reference to `__libc_csu_fini'
init.c:(.text+0x34): undefined reference to `__libc_csu_init'
./.libs/libgnuradio-core.so: undefined reference to `fstat'
./.libs/libgnuradio-core.so: undefined reference to `stat'
collect2: ld returned 1 exit status
make[5]: *** [gnuradio-config-info] Error 1
make[5]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[4]: *** [all-recursive] Error 1

Error while building GNU Radio on Beagleboard.

Beagle Board Performance

Need a clue to solve a Boost inconsistency under Angstrom

I'm attempting to build OSSIE using the Bitbake build system for the
BeagleBoard. I've successfully built the Angstrom x11-image
(local.conf lists DISTRO = "angstrom-2008.1") on my cross-build system
(running Debian Lenny updated a week ago), so I trust the basic sanity
of my OE toolchain and the basic Angstrom build.

I've followed the instructions at "Getting started with Embedded SDR"
(http://www.opensdr.com/node/7), with adaptations that seem reasonable
for the latest bitbake, mainly replacing ${OEDIR} with ${OETREE}. (I
notice those instructions date from 2008, so there may be something
else obsolete I'm doing...) I have also compared them to the Overo
build instructions, and I don't see any obvious incompatibilities.

The OSSIE version I'm getting from the SVN repo at
https://svn.geekisp.com/opensdr/OE/ossie_collection is 0.7.0.0, tagged
as ossie-cf-0.0.0+svnr380-r2.

When I try to bitbake a console-image with the OSSIE collection
included, I get an error compiling the OSSIE CF, which seems to be an
incompatibility with the Boost package, version 1_36_0, that is pulled
in by bitbake. The error is listed below:

FileSystem_impl.cpp: In member function 'virtual void
FileSystem_impl::remove(const char*)':
FileSystem_impl.cpp:95: error: void value not ignored as it ought to be
FileSystem_impl.cpp: In member function 'virtual
CF::FileSystem::FileInformationSequence* FileSystem_impl::list(const
char*)':
FileSystem_impl.cpp:168: error: 'class
boost::filesystem::basic_directory_entry<boost::filesystem::basic_path<std::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
boost::filesystem::path_traits> >' has no member named 'leaf'

There's a post on Nabble
(http://old.nabble.com/-filesystem--compiling-code-breaks-on-1.36-td19002108.html)
that mentions a very similar error, suggesting that Boost 1.36.0 broke
compatibility with older revs in regard to the filesystem.

All of this speaks to me of a version incompatibility between the
copies of OSSIE and Boost I'm using; either I'm following an outdated
set of instructions and fetching an old version of OSSIE from the
wrong place, or there's a setting I've neglected to tweak.

Can anyone who has recently built OSSIE on Angstrom, perhaps even for
the BeagleBoard, suggest where I may be going wrong here? I've got the
build logs if necessary, but in the interests of brevity I won't just
paste them all in here...

Thanks, Steve N1XNX

Beagle FPGA board - status update

Hi,

A quick status on the Beagle FPGA project:

Boards are back from the PCB fab and the first one has been assembled 
and is being tested. Configuration software is available and the board 
is working with both the Angstrom Stable and Unstable development trees. 
So far all power, ID, clocking and configuration support circuitry is 
working as designed. Off-board I/O and the remaining Beagle interface 
remains to be tested.

Find out more about this project at the following sites:

http://members.cox.net/ebrombaugh1/embedded/beagle/beagle_fpga.html

http://www.elinux.org/BeagleBoard_Tracker

Please let me know if you have any questions or comments on this.

Thanks,

Eric

Looking for overview information on the project

New Beagle FPGA board

Hi,

I'm about to go to fab with a prototype FPGA interfacing board for the 
Beagle:

http://members.cox.net/ebrombaugh1/embedded/beagle/beagle_fpga.html

While the board is fairly general in its applications, I am interested 
in SDR and that's part of the motivation for building it. There have 
already been some SDR RX projects based on the interface standard I'm 
using on this board - see this page:

http://sdrtrack.drupalcafe.com/?q=node/2

and it wouldn't be too difficult to build TX capabilities using a 
similar form factor.

This board is based on the Xilinx XC3S200A Spartan 3A part. It's a 
relatively small FPGA as such things go, but it's got enough horsepower 
to do some basic filter, conversion and rate change operations. Since it 
will be connecting directly to the Beagle GPIO port there are 
opportunities for some reasonable data rates too, so while it won't 
approach USRP2 levels of performance, it should be good for a variety of 
narrow-band applications.

At the moment I'm estimating the BOM for this board will run less than 
$100. I should be getting boards back in less than a month and I'll keep 
the web page updated with my progress.

Comments & questions invited...

Eric

GNU Radio / Beagleboard + DSP

Spam

Brian didn't really send it. I've contacted him and he is trying to 
figure out what happened...

Philip

Opa

http://sites.google.com/site/sfdgf67iykjfdhs/kqks8o