Aaron,
Yes, that is the solution. I saw that when looking at another YAML file
in the source folders. That is a typo in AN-400 that should probably be
fixed. In the section describing adding a FFT block to the receive chain:
clk_domains:
...
# As before, we still connect our FFT block to the clock domain
- { srcblk: _device_, srcport: ce, dstblk: fft0, dstport: ce }
srcport: ce should be srcport: rfnoc_chdr
It's obvious now but first time through it tripped me up.
Thanks for your help.
Mike
On 2/17/21 8:53 AM, Aaron Rossetto via USRP-users wrote:
On Tue, Feb 16, 2021 at 10:15 AM Mike via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> wrote:
Any ideas?
Try changing the clock domain connection to your FFT block to this:
- { srcblk: _device_, srcport: rfnoc_chdr, dstblk: fft0,
dstport:ce }
Does that allow rfnoc_image_builder to complete successfully?
Best regards,
Aaron
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
