u.org
> ] *On Behalf
> Of *Marcus Müller
> *Sent:* Wednesday, May 24, 2017 12:26 PM
> *To:* discuss-gnuradio@gnu.org; Philip Balister
>
> *Subject:* Re: [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
> Hi Jessica,
>
> that's really interesting!
>
>
nuradio
> [mailto:discuss-gnuradio-bounces+jessica.iwamoto=aero@gnu.org] *On
> Behalf Of *Marcus Müller
> *Sent:* Wednesday, May 24, 2017 12:26 PM
> *To:* discuss-gnuradio@gnu.org; Philip Balister
> *Subject:* Re: [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
&g
uss-gnuradio@gnu.org; Philip Balister
Subject: Re: [Discuss-gnuradio] Custom C++ blocks on E310
Hi Jessica,
that's really interesting!
It means that the problem only happens when you use your compiler to build your
C++ blocks, but not when only using the GNU Radio that's already part
> *Sent:* Monday, May 15, 2017 8:38 AM
> *To:* Ben Hilburn
> *Cc:* discuss-gnuradio@gnu.org
> *Subject:* [WARNING: SPOOFED E-MAIL--Non-Aerospace Sender] Re:
> [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
> Hi Ben,
>
>
>
> Here is some of the backtrace f
, 2017 8:38 AM
To: Ben Hilburn
Cc: discuss-gnuradio@gnu.org
Subject: [WARNING: SPOOFED E-MAIL--Non-Aerospace Sender] Re: [Discuss-gnuradio]
Custom C++ blocks on E310
Hi Ben,
Here is some of the backtrace from the error. At the top level, the error
starts in the msg_connect function and it looks
/runtime_swigPYTHON_wrap.cxx:47551
Thanks,
Jessica
From: Ben Hilburn [mailto:bhilb...@gnuradio.org]
Sent: Friday, May 12, 2017 1:35 PM
To: Jessica Iwamoto
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Custom C++ blocks on E310
Hey Jessica -
The SIGBUS you are receiving indicates that there is likely
t; aero@gnu.org] *On Behalf Of *Jessica Iwamoto
> *Sent:* Wednesday, May 10, 2017 9:53 AM
> *To:* discuss-gnuradio@gnu.org
> *Subject:* [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
> Hi all,
>
>
>
> I have built custom C++ blocks that work on my PC, but don
scuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] Custom C++ blocks on E310
Hi all,
I have built custom C++ blocks that work on my PC, but don't work when cross
compiled for the E310. Specifically, I am trying to build a custom C++ block
with a message port and cross compile it for the E310.
Hi all,
I have built custom C++ blocks that work on my PC, but don't work when cross
compiled for the E310. Specifically, I am trying to build a custom C++ block
with a message port and cross compile it for the E310. I am using version
3.7.12 of GNU radio and the latest version of the SDK/toolc
