-as-needed in the target_link_libraries of
> CMakeLists.txt did not resolve the issue either.
>
>
>
> Jeff
>
>
>
> *From:* Jeffrey P Long
> *Sent:* Friday, May 14, 2021 5:30 PM
> *To:* Brian Padalino
> *Cc:* usrp-users@lists.ettus.com
> *Subject:* [USRP-users] Re: [EXT
@lists.ettus.com
Subject: [USRP-users] Re: [EXT] Re: RFNOC block name?
Ok I had it up in /usr/lib but I moved it down to the root folder and it
basically gave the same thing with additional errors:
Kind of look like it is still not finding it. Did I set it wrong?
root@ni-e320-31DCD15:/usr/lib# export
On Mon, May 17, 2021 at 5:30 PM Jeffrey P Long wrote:
> Brian-
>
>
>
> OK just tried it and it does resolve the names now. In network mode the
> .so is installed in /usr/local/lib so it throws a bunch of errors trying to
> load everything else in that directory but when usrp probe does finally
>
on the embedded target I
could put the .so somewhere else to avoid all these other load attempts. Do you
have a recommendation?
Thanks
Jeff
From: Brian Padalino
Sent: Monday, May 17, 2021 11:08 AM
To: Jeffrey P Long
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: [EXT] Re: RFNOC block
the correct block name come up?
I can try that in a little bit.
Thanks
Jeff
From: Brian Padalino
Sent: Monday, May 17, 2021 11:08 AM
To: Jeffrey P Long
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: [EXT] Re: RFNOC block name?
On Mon, May 17, 2021 at 11:04 AM Jeffrey P Long
On Mon, May 17, 2021 at 11:04 AM Jeffrey P Long wrote:
> Brian-
>
>
>
> I think I am getting closer here. I actually just went back to using
> network mode so I could debug my issues without the extra challenge of the
> crossdev. That is a real nice thing about the E320.
>
>
>
> So I think the
17, 2021 10:10 AM
To: Jeffrey P Long
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Re: [EXT] Re: RFNOC block name?
On Sat, May 15, 2021 at 7:17 PM Jeffrey P Long
mailto:jpl...@mitre.org>> wrote:
Brian-
As a further test I moved the whole OOT module directory over to the
On Sat, May 15, 2021 at 7:17 PM Jeffrey P Long wrote:
> Brian-
>
>
>
> As a further test I moved the whole OOT module directory over to the
> device and cmake/make/install right on the device to see if it had some
> special sauce but no luck.
>
>
>
> OK maybe this is a real problem that Ettus is
laimed it’s
the most tested release ever.
Jeff
From: Jeffrey P Long
Sent: Saturday, May 15, 2021 6:07 PM
To: Brian Padalino
Cc: usrp-users@lists.ettus.com
Subject: [USRP-users] Re: [EXT] Re: RFNOC block name?
Brian-
Ok I made sure I compiled for the ARM and to be honest I lost track of
Brian-
Ok I made sure I compiled for the ARM and to be honest I lost track of which
terminal window I had sourced the SDK in so I was not sure and decided to redo
it.
But you can see the cmake and make seem successful further down below.
Then I moved it to /usr/share/uhd/modules since I saw
On Fri, May 14, 2021 at 5:48 PM Jeffrey P Long wrote:
> Ok I had it up in /usr/lib but I moved it down to the root folder and it
> basically gave the same thing with additional errors:
>
> Kind of look like it is still not finding it. Did I set it wrong?
>
>
>
> root@ni-e320-31DCD15:/usr/lib#
Ok I had it up in /usr/lib but I moved it down to the root folder and it
basically gave the same thing with additional errors:
Kind of look like it is still not finding it. Did I set it wrong?
root@ni-e320-31DCD15:/usr/lib# export UHD_MODULE_PATH=~/
root@ni-e320-31DCD15:/usr/lib#
12 matches
Mail list logo
