[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread mruane--- via USRP-users
Hi Piotr, I’m looking into the DPU driver kernel mods now. I’ll keep you posted. Cheers, Mike per...@o2.pl wrote: > Hello Mike, > > After short look at current linux-xlnx - it seems that there are not that > many changes needed for DPU to work. The driver is in one C file + C header:\ > li

[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread mruane--- via USRP-users
Hey Piotr! I was able to patch the meta-mender layer to fix the PSEUDO_ABORT bug. I’m still not sure it’s a bug in Mender, but it only seems to occur when I have the graphviz recipe included, which is required by the Vitis-AI library recipes. I’m really glad to have Mender images now. Tha

[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread mruane--- via USRP-users
Hi Piotr, I’m using kas 4.4. I followed the README in github.com/meta-ettus, under the section, “Building an Image using the Alchemy distro and kas.“ There is a link to the kas repo, and I just installed the latest. It’s been a while, but I believe that I went the manual kas route because I

[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread Piotr Krysik
W dniu 11.10.2024 o 15:19, Martin Braun pisze: On Fri, Oct 11, 2024 at 6:13 AM Piotr Krysik wrote: Regarding ‘kas’ command - that works well with the ‘zeus’ branch of meta-ettus (used up to UHD 4.6). But when I switched to more recent ‘kirkstone’ branch - it stopped. Probably some

[USRP-users] Re: Control operation timed out with custom block

2024-10-11 Thread houshang . azizi
Hi! I am facing similar issue. Can you please be more specific on how did you manage to fix it? Thanks! `du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.` `du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation ti

[USRP-users] Re: EnvironmentError: IOError: recv error on socket

2024-10-11 Thread Houshang
Hi Martin Thanks for getting back to me! I am running into some issues. Following might give you an idea. If you need more info to be able to help further, feel free to ask: ad@bm-super11-intel:~$ sudo uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_21.11; UHD_4.7.0

[USRP-users] Re: EnvironmentError: IOError: recv error on socket

2024-10-11 Thread Martin Braun
Are you trying to reach the N3xx? Because it shouldn't be findable by an unqualified uhd_find_devices call if it is reachable via DPDK. uhd_find_devices will only find DPDK-reachable devices if you specify the full address. --M On Thu, Oct 10, 2024 at 3:16 PM Houshang wrote: > Hello > I hereby

[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread Martin Braun
On Fri, Oct 11, 2024 at 6:13 AM Piotr Krysik wrote: > Regarding ‘kas’ command - that works well with the ‘zeus’ branch of > meta-ettus (used up to UHD 4.6). But when I switched to more recent > ‘kirkstone’ branch - it stopped. Probably some changes are needed in > that command. I would guess kas

[USRP-users] Re: Triggering of Rx synchronously with Tx in RFNoC

2024-10-11 Thread Martin Braun
Hey Piotr, it took me a bit to respond because this is tricky question. And I still don't have a great answer, but I also don't want to let you hang. A few thoughts: - Maybe you just want to write an RFNoC block that drops samples in a regular pattern for you. That way you wouldn't rely on timed

[USRP-users] Re: RFNoC Replay module (DRAM to PC)

2024-10-11 Thread Martin Braun
Hey Jorge Chen, I see what you're saying. Still, I'm not even sure 8 ports will fit. You could start with 5 ports, and then use a single streamer to get data out of the replay block into the host. You can use the replay block API to specify the memory region you want to download (or upload). So, t

[USRP-users] Re: RFNoC Replay module (DRAM to PC)

2024-10-11 Thread Jorge Chen
Hi Martin Thank you for your reply. I understand the N310’s default Replay block has 4 input and 4 output ports. In my setup, I connect the tx_streamers to the Replay block’s input ports and route the output ports to the DUC blocks on the TX side. On the RX side, I connect the DDC blocks to the Re

[USRP-users] Re: KAS kirkstone build of ni-titanium-rev5 on x410 with Vitis-AI Library and DPU drivers: Mainline kernel incompatible with zocl DPU driver; possible to use linux-xlnx kernel and make ti

2024-10-11 Thread Piotr Krysik
Hi Mike, The Kconfig files format is probably as mysterious to me (i.e. I don't know what processes them so they end up in the configuration and has proper dependencies). But you can just look at what the author of the driver added to appropriate 'Kconfig' and 'Makefile'. I.e. open 'gitk' pro