[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-10 Thread Piotr Krysik
Hello Mike, It’s good that you have experience with tftpboot, because the paths in my description are a bit wrong. I meant to put everything in /tftpboot directory for simplicity but then written /tftpboot/x410 - like I have it. So this is a mistake and ‘/tftpboot/x410’ should be replaced by

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

2024-10-10 Thread Houshang
Hello I hereby want to share more info. Please see attached file. Thanks Hoshang On Thu, 10 Oct 2024 at 09:02, Houshang wrote: > Hello > Does anyone know how to deal with the following error? > Thanks > Houshang > > ad@bm-super11-intel:/etc/netplan$ uhd_usrp_probe > [INFO] [UHD] linux; GNU C++ v

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

2024-10-10 Thread Houshang
Hello Does anyone know how to deal with the following error? Thanks Houshang ad@bm-super11-intel:/etc/netplan$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_21.11; UHD_4.7.0.HEAD-0-ga5ed1872 [INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=10.

[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-10 Thread perper
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:\ linux-xlnx/drivers/misc/xlnx_dpu.c\ linux-xlnx/drivers/misc/xlnx_dpu.h Look at their histories. Initial addition of this driver is 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-10 Thread mruane--- via USRP-users
Hi Piotr, I’m really glad you mentioned xlnx_dpu.c and xlnx_dpu.h. I found those a few days ago (in the linux-xlnx github repo, I think), and I was trying to find a recipe that installs them, but no luck. I didn’t think of manually copying them to the NI kernel and adding them to the NI rec

[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-10 Thread mruane--- via USRP-users
Hi Piotr, Thanks. The PXE boot info is fantastic. I don’t have it set up yet, but I’m going to start setting everything up today. I’ll start with just getting JTAG tftpboot running, and then start setting up NFS/PXE boot. Once this is working, it will REALLY simplify testing the rootfs.

[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-10 Thread mruane--- via USRP-users
Hi Piotr! So sorry for the delay! Wow, that’s a lot of good information! Thanks for the starting point information. I spent some time trying to find a common starting point. I have also been looking at the kernel config parameters in the defconfig and .cfg files. In the linux-xlnx kern

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

2024-10-10 Thread mruane--- via USRP-users
Hi Piotr, I just noticed that I had a typo in my reply to you. Regarding the statement, > you could just set it to transmit samples as soon as it gets them (i.e. the > wr_data_en signal would be equal to the inverted FIFO empty flag) I called the control signal ‘wr_data_en‘, thinking of the en