Hi Mike, Yes, I've run into that. I posted an issue last week here: https://github.com/EttusResearch/gr-ettus/issues/69
[https://opengraph.githubassets.com/5b58487cd101d233e77dea3debf24f97c1326803f405d696532fef76e41550f5/EttusResearch/gr-ettus/issues/69]<https://github.com/EttusResearch/gr-ettus/issues/69> syntax error in ettus_rfnoc_graph.block.yml · Issue #69 · EttusResearch/gr-ettus<https://github.com/EttusResearch/gr-ettus/issues/69> Line 25 of ettus_rfnoc_graph.block.yml in the maint-3.8-uhd4.0 branch (and possibly others) looks like: self.rfnoc_graph = ${id} = ettus.rfnoc_graph(uhd.device_addr("${graph_args}"))) You... github.com I ended up just modifying the yml file in source and then reinstalling gr-ettus. Jim ________________________________ From: Mike via USRP-users <usrp-users@lists.ettus.com> Sent: Friday, December 16, 2022 9:33 AM To: usrp-users@lists.ettus.com <usrp-users@lists.ettus.com> Subject: [USRP-users] Did anyone else need to do this? Hi all, This goes in the category of “Did anyone else need to do this?”. I’m running Ubuntu 20.04.5 LTS with GNURadio 3.8 (Maint) and UHD 4.0. I recently upgraded UHD to 4.2. I ran into a gnuradio issue starting a “RFNoC” flow graph with a syntax error for an unmatched ‘)’: Self.rfnoc_graph=ettus_rfnoc_graph_0 = ettus.rfnoc_graph(uhd.device_addr(“addr=xxx,type-n3xx”))) I was able to manually edit the generated python code to remove one of the parentheses and see the code work. I then upgraded gnuradio to 3.10 which had the same issue. I then compared the “uhd_rfnoc_graph.block.yml” block files between UHD4.0 and 4.2. It’s significantly different as 4.0 uses python .join to build the argument list and UHD 4.2 uses the python module “ast” to generate the argument list. But the final line on the 4.2 version had the syntax error of the extra ‘)’: self.rfnoc_graph = ${id} = uhd.rfnoc_graph(uhd.device_addr(“${graph_args}”))) I removed one ‘)’ then reinstalled gnuradio (make install) from the build directory and everything seemed to work after that. So, it seems like it is a simple syntax error. But normally something like this (in my experience) indicates that I might have missed some configuration step somewhere and have yet to see the other errors. So, has anyone seen something like this? Thanks, Mike
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com