Finally, I found that...
In Vivado there is a limit for the number of warnings and errors which are
displayed by the tool for a particular error or warning; the default value
of this limit is 100.
I concluded that:
*The synthesis not completed might be unrelated. This specific "warning"
is one o
Hi,
Are you running your FPGA build in a VM or on a system with a limited
amount of RAM?
Jonathon
On Fri, Feb 4, 2022 at 8:44 AM sp h wrote:
> Finally, I found that...
> In Vivado there is a limit for the number of warnings and errors which are
> displayed by the tool for a particular error or
Hi everyone,
I've been trying to implement the phosphor (among others) example with
RFNoC, but the error "'top_block_sptr' object has no attribute
'rfnoc_graph' " pops up when I try to run any flowgraph.
I'm using an E312 with UHD 4.1.0.5 and gnuradio v3.8.0.5.
I've installed gr-ettus using both
"Hopefully, someone can try the uhd "test_timed_commands" example in 4.1
to..."
Figure I ought to be about as good as the next somebody.
test_timed_commands output with UHD 4.1.0 and an X310
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107800;
UHD_4.1
Dustin,
Thank you for running that. So apparently, it isn't just an issue on my end.
Thanks,
Jim
From: Dustin Widmann
Sent: Friday, February 4, 2022 11:16 AM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Timed Commands Not Working
"Hopefully, someo
If you could start out with both 10MHz and PPS using GPS signal, set all clocks
to the same time (e.g., zero) at the common PPS, and then switch to using
external ref, it might be possible. My understanding is that the only thing
the PPS is needed for is setting the common time. In other words,
No, I built FPGA from Ubuntu 20.04, a physical PC not VM.
Ram is enough 12G, In other cases, it can be built correctly.
I think some connections and blocks in the RFNOC core image have errors...
On Fri, Feb 4, 2022 at 5:44 PM Jonathon Pendlum
wrote:
> Hi,
>
> Are you running your FPGA build in
Seeing the same behavior using UHD 4.1.0.1 on my N320 and E320, using internal
clock and time sources:
$ ./lib/uhd/examples/test_timed_commands --args addr=192.168.10.2
Creating the usrp device with: addr=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100;
UHD_4.1.0.HEAD-0-
.. Now that I look closely at test_timed_commands, I'm more confused. My
understand of set_command_time is that it sets an FPGA register of the future
time at which to process subsequent commands, but none of the calls will block.
If the application wants to wait for the timed command to occur,
For reference, I've done it over again with the latest commits from the
UHD-4.0 and UHD-3.15.LTS branches.
Creating the usrp device with: ...
[INFO] [UHD] linux; Clang version 13.0.0 ; Boost_107400;
UHD_4.0.0.0-240-gb38c9d83
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum
Tested with UHD 4.0.0.0 release tag and UHD 4.1.0.0 release tag with the
same results. Hmm.
Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400;
UHD_4.1.0.HEAD-0-gd21735d5
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8
Hello,
I know that when I see O's (overruns) in the terminal it means my host
processing is not keeping up with the sample stream coming in from the
USRP. Samples are being dropped because the host is too slow to keep up.
I'm wondering if there is a test I can run that would reveal the cause of
t
Hi Richard,
I don't know the answer but I have a couple of comments / questions:
1) do you have cables that would enable you to eliminate your switch (at
least for debugging purposes)? I'm thinking of some type of NIC re-config
and breakout cable that would allow your NIC to have multiple 10Gbe
con
On 2022-02-04 15:26, Richard Bell wrote:
Hello,
I know that when I see O's (overruns) in the terminal it means my host
processing is not keeping up with the sample stream coming in from the
USRP. Samples are being dropped because the host is too slow to keep up.
I'm wondering if there is a t
You mentioned the log file. Did you check build-X300_HG/build.log or just
the console? In addition to that, you could look at the other files
generated in the build-X300_HG directory. Sometimes they have information
that the console doesn't show.
If Vivado didn't output a useful error message, the
Hi, thanks for your attention in the first message I attached the YAML
RFNOC image core...( x300_with_fft.yml )
On Sat, Feb 5, 2022 at 1:48 AM Wade Fife wrote:
> You mentioned the log file. Did you check build-X300_HG/build.log or just
> the console? In addition to that, you could look at the o
Hi, In RFNOC image core files I saw that BSP connection?
what's them and what's the difference between ordinary connections and BSP
connections...
thanks in advance
*BSP connections:*
# BSP Connections
- { srcblk: radio0, srcport: ctrl_port, dstblk: _device_, dstport:
ctrlport_radio0 }
- { sr
17 matches
Mail list logo
