gmane.comp.hardware.beagleboard.sdr

USRP Embedded

Philip Balister — 2010-07-04T18:38:18

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.

Charles R — 2010-07-04T17:32:09

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
make[4]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/root/gnuradio/gnuradio-core/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/root/gnuradio/gnuradio-core'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/gnuradio'
make: *** [all] Error 2
*******************************************************************************

doing rm /usr/lib/*.la solved the above error.
Then i encountered another error:

*****Error Log ****************************************************************
Making all in io
make[5]: Entering directory `/home/root/gnuradio/gnuradio-core/src/lib/io'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib/io'
Making all in hier
make[5]: Entering directory `/home/root/gnuradio/gnuradio-core/src/lib/hier'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib/hier'
Making all in .
make[5]: Entering directory `/home/root/gnuradio/gnuradio-core/src/lib'
/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: cannot find the library `/usr/lib/libstdc++.la' or unhandled 
argument `/usr/lib/libstdc++.la'
make[5]: *** [gnuradio-config-info] Error 1
make[5]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/root/gnuradio/gnuradio-core/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/root/gnuradio/gnuradio-core'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/gnuradio'
make: *** [all] Error 2
*******************************************************************************

I checked if libtool was present , it was up to date.

root< at >beagleboard:~/gnuradio# opkg install libtool
Package libtool (2.2.6b-r25.0.5) installed in root is up to date.


Steps i followed while building GNU radio:

1. Installed prerequisites:

opkg install  libusb1-dev guile-dev fftwf-dev alsa-dev alsa-lib-dev jack-dev 
cppunit-dev swig python-devel python-numpy-dev python-textutils 
python-distutils python-re python-stringold python-lang 
python-threading python-unittest python-shell python-pickle
python-pprint python-compiler python-pkgutil python-pydoc 
python-mmap python-netclient python-difflib python-compile
python-cheetah boost-dev gsl-dev sdcc git util-linux-ng util-linux-  ng-
swaponoff

2. did ./bootstrap

3. then ./configure --disable-usrp2 --with-fusb-tech=libusb1 CFLAGS="-
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp" CXXFLAGS="-
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp"

Here i got a output:
The following components were skipped because you asked not to build them or 
they didn't pass configuration tests

usrp2
gr-usrp2
gr-utils
grc
and the audio osx and windows packages ..

I went over the config.log file 
it said didnt build gr-wxgui because it cannot find wxpython, 
then it didnt build grc because of gr-wxgui and xdg-mime.


Is it possible to build grc on beagleboard?


4. Make gave me the above listed errors.


I am stuck at this point and not able to go ahead. Plz help.

Thanks in advance.


sorry that was a long post but will make it shorter and in chunks.

Charles R.

Error while building GNU Radio on Beagleboard.

Ashwin Raut — 2010-07-02T03:33:45

Hi,

I got the following error while building GNU Radio , i tried to search
for the error it said something about swap space in some ubuntu forums,
but i am not sure if its the same issue on beagleboard.

Console Log:

Making all in .
make[5]: Entering directory `/home/root/gnuradio/gnuradio-core/src/lib'
/bin/sh ../../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H
-I. -I../../..   -I/usr/include
-I/home/root/gnuradio/gnuradio-core/src/lib/runtime c
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I/usr/include
-I/home/root/gnuradio/gnuradio-core/src/lib/runtime
-I/home/root/gnuradio/gnuradio-coreo
mv -f .deps/bug_work_around_6.Tpo .deps/bug_work_around_6.Plo
/bin/sh ../../../libtool --tag=CXX   --mode=link g++ -Wall
-Woverloaded-virtual -march=armv7-a -mtune=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -pthread  -ver
libtool: link: g++ -shared
-nostdlib /usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../crti.o
/usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/crtbeginS.o0
[70258.842254] select 1 (init), adj 0, size 58, to kill
[70258.851959] select 1619 (dbus-daemon), adj 0, size 65, to kill
[70258.862396] select 1639 (syslogd), adj 0, size 69, to kill
[70258.872375] select 1649 (avahi-daemon), adj 0, size 91, to kill
[70258.882965] select 6316 (make), adj 0, size 103, to kill
[70258.892852] select 6318 (make), adj 0, size 105, to kill
[70258.902587] select 6578 (make), adj 0, size 108, to kill
[70258.912322] select 14622 (make), adj 0, size 133, to kill
[70258.921966] select 14641 (sh), adj 0, size 208, to kill
[70258.931488] select 14850 (ld), adj 0, size 20812, to kill
[70258.941131] send sigkill to 14850 (ld), adj 0, size 20812
collect2: ld terminated with signal 9 [Killed]
make[5]: *** [libgnuradio-core.la] Error 1
make[5]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/root/gnuradio/gnuradio-core/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/root/gnuradio/gnuradio-core/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/root/gnuradio/gnuradio-core'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/gnuradio'
make: *** [all] Error 2

What would be the reason? how to solve it.

Thanks.

Ashwin Raut.

Beagle Board Performance

devin kelly — 2010-06-18T14:09:17

Hello,

I'm interested in doing a project with the Beagle Board and the USRP1, along
with using gnu radio.  My lab doesn't have a Beagle Board or USRP1 (only
USRP2s), so I need a few questions answered before I commit to this
platform.

What type of performance can I expect from the Beagle Board?  I'm mostly
interested in doing FFTs with some comparatively small processing on that
data, is this possible?

What sort of decimation rates can I use and expect near real time
performance for this application?  I have a few (albeit several years old)
machines that struggle with just taking an FFT with a decimation rate of
around 8.  This is on the USRP2 as well.

Any advice at all is appreciated.
Devin

Need a clue to solve a Boost inconsistency under Angstrom

Stephen Hersey — 2010-05-23T02:09:17

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

Eric Brombaugh — 2010-05-18T18:30:08

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

Stephen Hersey — 2010-05-17T21:01:32

Greetings!
I'm interested in experimenting with SDR on my new BeagleBoard. However,
rather than plunge in, download lotsa packages, kick off BitBake, and find
myself lost in a maze of twisty little error messages,  I'd like to start by
understanding the overall architecture of the Beagle-SDR implementation, how
it partitions functionality between the GPP, DSP processor, and external
hardware, how it fits in with GNU Radio and Embedded SDR, and eventually,
how to connect stuff to it. I've read the ARRL Handbook chapter on SDR, I
have a general understanding of SDR principles and some experience working
with SCA environments and waveforms, and I've read the descriptions of the
USRP, but I'm having trouble finding any overall design information on the
Beagle-SDR. Can anyone point me to sources of information on the
architecture you're building here and its performance goals? (For example:
If, as appears likely, you're emulating the USRP motherboard in the
Beagleboard DSP, what sort of RF frequency range do you plan to cover?)

Down the road, I'd like to use the BeagleBoard and its SDR capabilities for
control of a semi-autonomous remotely operated vehicle, but that's down the
road. Small steps first...

Any hints are greatly appreciated.

New Beagle FPGA board

Eric Brombaugh — 2010-04-14T18:14:21

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

2010-04-12T01:10:48

 Hi, I'm currently working on integrating the DSP into GNU Radio on the Beagleboard, I remember that someone wrote some code to interface the Beagleboard to the board that Dr. Anderson is building, as per the Wireless< at >VT slides., I think it was Phillip.  Anyways,  I can't seem to find the custom gnuradio SPI block or the bitbake recipe to do that, I was wondering if I can gain access to that code so I can use it as a template to encapsulate my DSPLink code, also once I'm done with doing that what would be the best way to share the code through gnuradio openembedded or what??  thanks

al fayez

Spam

Philip Balister — 2010-04-11T18:43:22

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

Philip

Opa

Brian Padalino — 2010-04-11T18:36:34

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

Current beagle SDR status

marcos gallego — 2010-03-26T00:27:12

Hi All,
After reading the emails at http://www.mail-archive.com/beagle-sdr< at >opensdr.com/,
I have some questions:

1. What is the current status of the Beagle SDR Interface board?
I found  Beagle_InterfaceBoard.pdf diagram from Professor Anderson, Rev.1 but I'd like to know if there is a new version for that.

2. Are the PCB layout and gerber files available? Or any other place that is selling the boards?

3. What is the estimated cost for the Beagle SDR Interface board for the BOM only?

Thanks a lot for everybody that has spent time doing this wonderful project.

Thanks

Marcos




       
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969

Has anyone experience with omap mcbsp (beagleboard or overo) ?

Michele Bavaro — 2009-12-07T16:19:44

Hello everyone,

I'm following with interest the development of the SPI driver as
beagleboard to FPGA interface.

In my case, the OMAP35xx on a Gumstix OVERO connects to a Maxim/Dallas
MAX2769 (GPS front-end) through a "DSP interface".
This is a 4-wire serial bus with
1) data,
2) clock (most likely at about 20MHz),
3) a 16 bit word-sync signal,
4) a 128 words frame-sync signal.

and (maybe) you can find a short snapshot of the timing in attach. As far
as I understood from the Omap TRM, the SPI won't do the job. I'm quite
sure that I need the MCBSP to receive that protocol.

From a preliminary study, I think receiving 20Mbit/sec (2.5MByte/sec) is
possible using DMA. I think the latest kernel image with a custom U-BOOT
(to change the pin mux to expose the MCBSP3) should do. Does anyone have
any idea to share on this topic?

With regards,
Michele

Beagle-SDR and necessary hardware

Fabrizio Tappero — 2009-12-01T13:28:31

Dear Beagle-SDR developers,
hello, I am new here.

I am interested in the beagle-SDR and I understand that in order to
get started you need 3 pieces of HW:

- front end  (US$ 270)
from: http://www.ettus.com/downloads/er_ds_transceiver_dbrds_v5b.pdf

- beagle board (US$ 150)
from: http://beagleboard.org/

- beagle-SRD card (price?)
from: ?

Am I right?
Would it be possible to know how to get the beagle-SDR board? Also is
this board designed in am open-source open-hardware way? are the
schematics and PCB files available for download?

Thank you very much in advance and great job !

Regards,
Fabrizio

Question about SPI transfer rate and OMAP processing power

Przemyslaw Dmochowski — 2009-11-26T15:08:16

Hello everyone,

I work on an SDR that would work from a battery and without a PC.
I read the posts about SPI transfer rates and I was wonder whether
you've done some work to test real processing power of the BeagleBoard. 
What I am interested in is the maximum spectrum bandwidth that can be
achieved with the combination of USRP and BeagleBoard assuming the data
transfer between them is done over SPI interface.
My applications I am thinking of at the moment are not very demanding
(AM/FM UHF analog radio) but in the future I would want to have 5Mbits/s
digital transmission (probably FSK) over the radio using OFDM.
I don't own the BeagleBoard at the moment and I would appreciate  your
comments on the signal processing capabilities of the USRP-BB
configuration. Do you think the 5Mbits/s using OFDM will be possible?

Open Max SP DL Library linking error

Rachit shah — 2009-09-30T06:52:53

Transfer rate

Philip Balister — 2009-08-26T19:54:03

Fiddling around with the data genertor in the FPGA gives about 3.5 
MBytes/second as the best transfer rate you can expect (with the current 
omap mcspi driver).

real    1m 15.87s
user    0m 0.12s
sys     0m 0.53s


are the times from the test program run. So we are not burning lots of 
time pushing data around.

Philip

SPI driver

Philip Balister — 2009-08-26T18:17:12

http://github.com/balister/linux-omap-philip/commits/sdr-spi-driver

has the code for the SPI driver.

The underlying Linux kernel is based on the 2.6.29 version used on the 
beagle, so use that default Angstrom kernel and build the spisdr.ko 
module. Copy that into the /lib/modules nd run depmod -a.

Philip

Data transfer between FPGA and Beagle via SPI

Philip Balister — 2009-08-25T20:08:13

http://www.flickr.com/photos/32615155< at >N00/3857143522/

This is using a kernel driver that handles an interrupt from the fpga 
that notifies the beagle there is enough data in a FIFO to complete a 
4096 byte SPI transfer.

Philip