Thanks--I'll give that a try when the dust clears here.
On 9/4/18 1:59 PM, Martin Braun via USRP-users wrote:
On Fri, Aug 17, 2018 at 01:02:28PM -0400, Daryl Lee via USRP-users wrote:
In November of 2016, I cross-compiled UHD (git-cloned) on my Ubuntu 16.04
development host targeting a Zynq ch
On 09/06/2018 04:01 PM, Harper, Andrew wrote:
I'm running Xubuntu 16.04 on the hardware, i.e. not VM:
Distributor ID:Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:xenial
Ethernet info:
description: Ethernet interface
product: RTL8
On 09/06/2018 03:29 PM, Harper, Andrew via USRP-users wrote:
Hi, I am having a troubling error from my x310 USRP whenever I try to
pull samples using the USRP source block. The error message I am
getting is:
[ERROR] [STREAMER] The receive packet handler caught a value exception.
ValueError:
Hi, I am having a troubling error from my x310 USRP whenever I try to pull
samples using the USRP source block. The error message I am getting is:
[ERROR] [STREAMER] The receive packet handler caught a value exception.
ValueError: Bad CHDR or packet fragment
WARN: USRP Source Block caught rx err
On 09/06/2018 08:52 AM, Jason Matusiak wrote:
> Just finished running the second command just mentioned below, still died
> with the package "six" error.
I found the problem, will regenerate images and sdk tonight and update
Dropbox in the morning. Thanks for testing this and finding I still had
On Thu, Sep 6, 2018 at 2:43 PM Pratik Chatterjee via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Hi,
>
> Can anyone please provide some insight on the use of configuration buses
> in the axi wrapper - why and when would we want to use them? Do they
> complement the axis stream signals (m_axi
Hi,
Can anyone please provide some insight on the use of configuration buses in
the axi wrapper - why and when would we want to use them? Do they
complement the axis stream signals (m_axis and s_axis) in any way? Thank
you,
Pratik
___
USRP-users mailing
Update: The issue is included on the head of the UHD-3.12 branch, but is
not included in the v3.12.0.0 release. So, be sure to checkout the
v3.12.0.0 tag.
The issue we replicated is the STREAM_CMD_NUM_SAMPS_AND_DONE. The
continuous streaming issue is still outstanding, but may be related.
Rega
OK. I will give it a shot. Which issue did you duplicate (the confusion is
my fault for discussing two different issues in the same thread): Issue #1
(NUM_SAMPS_AND_DONE) or Issue #2 (CONTINUOUS)?
Rob
On Thu, Sep 6, 2018 at 1:52 PM Michael West wrote:
> Hi Rob,
>
> Thank you once again. We ha
Hi Rob,
Thank you once again. We have reproduced the issue and are working on
tracing down the root cause and fixing the issue. We have confirmed that
the issue exists on 3.13, but we have also confirmed it does not exist on
3.12.0.0. So, you can use v3.12.0.0 in the meantime. To be sure you a
On 09/06/2018 08:52 AM, Jason Matusiak wrote:
> Just finished running the second command just mentioned below, still died
> with the package "six" error.
I looked at the sdk manifest in Dropbox and don't see the python-six
included, but it looks like the sdk should. Going to run some builds
here,
Sorry Andrew, I didn't see your response.
I tried your steps, but on the gnuradio rebuild, it failes with this error:
[ 6%] Building CXX object
gnuradio-runtime/lib/CMakeFiles/gnuradio-runtime.dir/block.cc.o
/opt/gnuradio/e300/src/gnuradio/gnuradio-runtime/lib/block.cc: In member
function 'void
Just finished running the second command just mentioned below, still died with
the package "six" error.
- Original Message - Subject: RE: Re: [USRP-users] Issues
installing GNUradio using PYBOMBS (e3xx-custom-uhd or e3xx-rfnoc)
From: "Jason Matusiak"
Date: 9/6/18 8:44 am
To:
Thanks Philip, that will be very helpful. Will the steps be the same as
before? :
1 - sh ./oecore-x86_64-armv7ahf-neon-toolchain-nodistro.0.sh
2 - pybombs prefix init /opt/gnuradio/e300 -R e3xx-rfnoc -a e300
Or will something need to change there?
- Original Message - Subjec
14 matches
Mail list logo
