On 03/09/2018 12:11 AM, Samuel Prager via USRP-users wrote:
Still looking for more info on this problem.
I have the exact same RfNoC block/software program running on an X300
and see no such jumps or otherwise unexpected behavior.
I have attempted to isolate this issue on the E312 by creating the
device3 with the */“no_reload_fpga”/* flag. (Appropriate image is
loaded before hand with the uhd_usrp_image_loader. Running my program
the first time works as expected, but if I kill the program and
restart, I get this error:
/“AssertionError: zf_peek32(ctrl_base+ARBITER_RB_ADDR_SPACE) > 0 in
virtual void e300_fifo_mb::release()"/
The last few lines in the Uhd log file are:
/e300_impl.cpp:639,1,E300,[E300] Setting up dest map for host ep 0 to
be stream 0
device3_impl.cpp:131,0, DEVICE3, Setting up NoC-Shell Control for port
#0 (SID; 00:00>02:10)
device3_impl.cpp:139,0,DEVICE3, OK
davice3_impl.cpp:141,0, DEVICE3, Port 16: found NoC-Block with ID
12AD100000000000.
e300_impl.cpp:639,1,E300, [E300] Setting up dest map for host ep 1 to
be stream 1
device3_impl.cpp:160,0,DEVICE3, Setting up NoC Shell port for #1 (SID:
00:01>02:11)/
Shouldn’t the E312 be able to operate without needing to reload the
FPGA image each time? Has this been tested? I would really appreciate
any hints or pointers into why this is happening.
Thank you,
Sam
The E3xx run an "idle" image when the device is not being used. I
cannot remember the reason for that, TBH.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
