discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Porting new hardware to GNURadio


From: Martin Braun
Subject: Re: [Discuss-gnuradio] Porting new hardware to GNURadio
Date: Fri, 27 Apr 2012 09:23:17 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Apr 26, 2012 at 11:31:40AM -0400, Getz, Robin wrote:
> On Thu 26 Apr 2012 10:58, Johnathan Corgan pondered:
> > On Thu, Apr 26, 2012 at 07:38, Getz, Robin <address@hidden> wrote:
> > > Is there a "golden" reference to look at? (I assume
> > > gr-howto-write-a-block-3.6.0.tar.gz
> > > should have everything we need?)
> >
> > This will give you the "canonical" format for writing your own
> > out-of-tree installable GNU Radio blocks.
> 
> And what is preferred? I always think in-tree is better - but that's just me.

Just adding to what Johnathan said:

out-of-tree is easier to start with. You can use gr_modtool[1] to create
all the skeleton code, chuck in your driver hooks and be running within
the hour.

Just do something like (change this to whatever you need)

$ gr_modtool.py create fmccomms
$ cd gr-fmccomms/
$ gr_modtool.py add -t sink sink_c
$ gr_modtool.py add -t source source_c

Then, fill in the blanks (i.e. edit lib/fmccomms_sink_c.cc and so on).

MB

[1] https://cgran.org/wiki/devtools

-- 
Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)

Dipl.-Ing. Martin Braun
Research Associate

Kaiserstra├če 12
Building 05.01
76131 Karlsruhe

Phone: +49 721 608-43790
Fax: +49 721 608-46071
www.cel.kit.edu

KIT -- University of the State of Baden-W├╝rttemberg and
National Laboratory of the Helmholtz Association

Attachment: pgpnpoTD6Tbjg.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]