[USRP-users] Can the Octoclock CDA-2990 use a Timeprovider 4100's PPS/Freq as inputs?

Hi, I'd like to use a Chronos Timeprovider 4100 to provide the input signals to the Octoclock CDA-2990. Will the Octoclock accept the Timeprovider's signals for 10MHz and PPS? Presumably the Time

[USRP-users] Re: Can the Octoclock CDA-2990 use a Timeprovider 4100's PPS/Freq as inputs?

Hi Marcus, >The Octoclock is basically a *distributor* of PPS and 10MHz. It cannot use the 1PPS to phase-lock its internal clock. >For the 10MHz signal from your time-provider, I would insert a 3-5dB attenuator, since the lowest level of the > TimeProvider output is right at the top end of what

[USRP-users] Re: Multi-port Transmission with RFNoC Replay Block on USRP x410

Hey,\ \ Have you tried using a single replay block?\ The replay block can be configured to have multiple ports that each can be connected the radio. For example the [x410_X4_200_rfnoc_image_core.yaml](https://github.com/EttusResearch/uhd/blob/master/fpga/usrp3/top/x400/x410_X4_200_rfnoc_image_co

[USRP-users] Re: Can the Octoclock CDA-2990 use a Timeprovider 4100's PPS/Freq as inputs?

On 13/03/2025 09:30, Chris Newman via USRP-users wrote: Hi, I found some documentation for the Timeprovider 4100 and there are 2 ports which can be configured to output either 1PPS or 10MHz. The latter is a square wave so I guess I can plug that into the Octoclock: image.png The question no

[USRP-users] Multi-port Transmission with RFNoC Replay Block on USRP x410

Hello, I'm working with the USRP x410 and need to transmit from all four ports at 200MSPS using the RFNoC replay block. Is this possible with the existing block? When I tried to duplicate the block, I encountered errors with memory connections. What's the best way to properly replicate thi

[USRP-users] Re: Can the Octoclock CDA-2990 use a Timeprovider 4100's PPS/Freq as inputs?

Hi, I found some documentation for the Timeprovider 4100 and there are 2 ports which can be configured to output either 1PPS or 10MHz. The latter is a square wave so I guess I can plug that into the Octoclock: [image: image.png] The question now is if the Timeprovider's PPS output is compatible

[USRP-users] Re: rfnoc_image_builder error: trying to tool lock on already tool locked arc

Hi David & Wade, I would just like to chime in on this that I've been having exactly the same issue, repeatably, building for N310&320 series devices. I'm running a heavily customised image with plenty of (known good) custom logic, and the error comes up seemingly at random following a commit.

[USRP-users] Re: [EXT] Re: Trouble updating file system on X410

Thank you for helping! I tried your suggestion, and it did allow me to try mender again. Unfortunately it still did not work, and now I don’t get any QSFP network connection. I think it may be because I did a: mender -commit command before rebooting this time. So then I tried t

[USRP-users] Re: axi_mm io_signature issue

Hi Brian, I'm pretty sure that's a typo. Someone mixed 4096 with 8192. But it should not matter as long as the bus is big enough. The extra bits will be ignored and optimized out. Even 4096 is bigger than needed in most cases. There has been some work to have the image builder set these widths to

[USRP-users] Re: Trouble updating file system on X410

Hi! When you see the error “(…) Artifact Payload type 'rootfs-image' is not supported by this Mender Client. (…)” then you edit /data/mender/mender.conf and set the following content: {\ "RootfsPartA": "/dev/mmcblk0p2",\ "RootfsPartB": "/dev/mmcblk0p3"\ } Then you should be able to run the