Wow, I don't know why running it in the GUI would matter. You mentioned you did some customization in the Vivado GUI. Could that have something to do with it?
I looked over your YAML and I noticed you have MEM_DATA_W on the Replay block set to 128 but you're building for the X410_X4_200 target which expects 64-bit interfaces. I think that would corrupt the data, but not prevent TX. So I don't know if that entirely explains the issue. But it does need to be 64 unless you've made changes elsewhere to compensate. Wade On Wed, Jun 7, 2023 at 8:30 PM <jmalo...@umass.edu> wrote: > If I use the same yml file I pasted above, I am able to generate an image > that properly transmits. However, if I use the same yml file, but when I > use the rfnoc_image_builder but with a GUI option, the transmit fails to > work. I do not edit anything in the GUI, I just tested the bitstream > created as is after invoking rfnoc_image_builder with the GUI option. I > would imagine that GUI option or not, the constraints have to be identical. > Is there any chance they are not? > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
