I had the same problem indeed,
I think this is because vivado 2017.4 output image size is a bit
different from the output imase size of vivado 2015.4.
I say so because the error did not appear with uhd-3.10.3. I think the
problem is that no one updated the tools provided with libuhd
used to
Hi guys,
I am responding to the following thread:
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2018-August/057669.html
I am having the same problem while running the uhd_image_builder.py with
the default images for X310.
See below:
