[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-23 Thread Maria Muñoz
Hi Martin, I have figured it out when you write the path. There was a misspelling, "gr_ettus" instead of "gr-ettus". Now, I can build the image, thank you! Kind Regards, El jue, 18 jul 2024 a las 18:06, Martin Braun () escribió: > > On Thu, Jul 18, 2024 at 3:06 PM Maria Muñoz wrote: > >> Hi M

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-18 Thread Martin Braun
On Thu, Jul 18, 2024 at 3:06 PM Maria Muñoz wrote: > Hi Martin, > > Oh! I didn't know there was a debug option. The line says this: > [DEB] Executing the following command: /bin/bash -c ". ./setupenv.sh && > make X440_X4_200 > IMAGE_CORE=/home/user/rfnoc/gr-ettus/rfnoc-nbc_v2/rfnoc/icores/x440_20

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-18 Thread Maria Muñoz
Hi Martin, Oh! I didn't know there was a debug option. The line says this: [DEB] Executing the following command: /bin/bash -c ". ./setupenv.sh && make X440_X4_200 IMAGE_CORE=/home/user/rfnoc/gr-ettus/rfnoc-nbc_v2/rfnoc/icores/x440_200_rfnoc_image_core.v EDGE_FILE=/home/user/rfnoc/gr-ettus/rfnoc-n

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-18 Thread Martin Braun
Hi Maria, I'm not sure what's going on. Can you run rfnoc_image_builder -l debug [...your options...] and post the line that says "Executing the following command: ..."? I wonder if RFNOC_OOT_MAKEFILE_SRCS is correctly set. BTW, if you just upgraded to 4.6, consider upgrading to 4.7. On the X440,

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-18 Thread Maria Muñoz
Hi Martin, I had another issue once I resolved the YML problem. I start the synthesis with this command: rfnoc_image_builder -y x440_200_nbc_rfnoc_image_core.yml -d x440 -t X440_X4_200 --fpga-dir ~/rfnoc/uhd/fpga/ But Vivado can't find my OOT block: ERROR: [Synth 8-439] module 'rfnoc_block_nbc

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread Martin Braun
Quick update for the wide world: This bug was not fixed in 4.7, but a fix is on the way. --M On Wed, Jul 17, 2024 at 12:05 PM Martin Braun wrote: > Hey Maria, > > thanks for reporting this issue. Some pointers: > - As a workaround, you can install ruamel.yaml 0.17. I don't know how you > instal

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread mamuki92
That works, thank you! ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread Martin Braun
In that case you can just do apt install python3-ruamel.yaml and make sure you have no other version installed. --M On Wed, Jul 17, 2024 at 12:22 PM Maria Muñoz wrote: > Hi Martin, > . > Thanks for your answer. I will do the workaround. > By the way, I'm using Ubuntu 20.04. > > Kind Regards,

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread Maria Muñoz
Hi Martin, . Thanks for your answer. I will do the workaround. By the way, I'm using Ubuntu 20.04. Kind Regards, El mié, 17 jul 2024 a las 12:07, Martin Braun () escribió: > Quick addendum: If you do update to 4.7, you will need to update some > image core files, because we changed stuff for X41

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread Martin Braun
Quick addendum: If you do update to 4.7, you will need to update some image core files, because we changed stuff for X410 and X440. Best to go back to the YAML files we provide in-tree and add your OOT blocks to those. --M On Wed, Jul 17, 2024 at 12:05 PM Martin Braun wrote: > Hey Maria, > > th

[USRP-users] Re: Synthesize an OOT block with rfnoc and UHD 4.6

2024-07-17 Thread Martin Braun
Hey Maria, thanks for reporting this issue. Some pointers: - As a workaround, you can install ruamel.yaml 0.17. I don't know how you installed it before, but you can do `pip install "ruamel.yaml<0.18.0"` if you used pip before. - I need to double-check this, but I think UHD 4.7 has a fix for this.