usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

connecting the ce clock to a custom rfnoc block

KW
Kevin Williams
Wed, Apr 2, 2025 8:30 AM

Hi,

I am trying to make use of the CE clock in a custom RFNoC block on an N300.

The way I understand it is to add it to the clock definitions in the block
yaml file:

clocks:

  • name: rfnoc_chdr
    freq: "[]"
  • name: rfnoc_ctrl
    freq: "[]"
  • name: ce
    freq: "[]"

and then just connect it in the image yaml file:

clk_domains:

  • { srcblk: device, srcport: radio,    dstblk: radio0,    dstport:
    radio    }
  • { srcblk: device, srcport: ce,        dstblk: polconv0,  dstport: ce
    }

Running make I get the error: "Invalid clock domain connection: device:ce
→ polconv0:ce (ce is not a clock input)"

I can't find another place to define that clock input for my block?

Kind regards, Kevin

Hi, I am trying to make use of the CE clock in a custom RFNoC block on an N300. The way I understand it is to add it to the clock definitions in the block yaml file: clocks: - name: rfnoc_chdr freq: "[]" - name: rfnoc_ctrl freq: "[]" - name: ce freq: "[]" and then just connect it in the image yaml file: clk_domains: - { srcblk: _device_, srcport: radio, dstblk: radio0, dstport: radio } - { srcblk: _device_, srcport: ce, dstblk: polconv0, dstport: ce } Running make I get the error: "Invalid clock domain connection: _device_:ce → polconv0:ce (ce is not a clock input)" I can't find another place to define that clock input for my block? Kind regards, Kevin
MB
Martin Braun
Wed, Apr 2, 2025 9:13 AM

What you're doing is correct. Is it possible there's an old version of the
YAML file that is being picked up? You can increase the log level of the
image builder, it will tell you which files it's sourcing.

--M

On Wed, Apr 2, 2025 at 10:31 AM Kevin Williams kevin.williams@vastech.co.za
wrote:

Hi,

I am trying to make use of the CE clock in a custom RFNoC block on an N300.

The way I understand it is to add it to the clock definitions in the block
yaml file:

clocks:

  • name: rfnoc_chdr
    freq: "[]"
  • name: rfnoc_ctrl
    freq: "[]"
  • name: ce
    freq: "[]"

and then just connect it in the image yaml file:

clk_domains:

  • { srcblk: device, srcport: radio,    dstblk: radio0,    dstport:
    radio    }
  • { srcblk: device, srcport: ce,        dstblk: polconv0,  dstport: ce
    }

Running make I get the error: "Invalid clock domain connection: device:ce
→ polconv0:ce (ce is not a clock input)"

I can't find another place to define that clock input for my block?

Kind regards, Kevin


USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

What you're doing is correct. Is it possible there's an old version of the YAML file that is being picked up? You can increase the log level of the image builder, it will tell you which files it's sourcing. --M On Wed, Apr 2, 2025 at 10:31 AM Kevin Williams <kevin.williams@vastech.co.za> wrote: > Hi, > > I am trying to make use of the CE clock in a custom RFNoC block on an N300. > > The way I understand it is to add it to the clock definitions in the block > yaml file: > > clocks: > - name: rfnoc_chdr > freq: "[]" > - name: rfnoc_ctrl > freq: "[]" > - name: ce > freq: "[]" > > and then just connect it in the image yaml file: > > clk_domains: > - { srcblk: _device_, srcport: radio, dstblk: radio0, dstport: > radio } > - { srcblk: _device_, srcport: ce, dstblk: polconv0, dstport: ce > } > > Running make I get the error: "Invalid clock domain connection: _device_:ce > → polconv0:ce (ce is not a clock input)" > > I can't find another place to define that clock input for my block? > > Kind regards, Kevin > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com >
KW
Kevin Williams
Wed, Apr 2, 2025 10:27 AM

Ah. It sneakily uses the block config which got installed in /usr/local/share/uhd and not the one I am working on.

Thanks.

From: Martin Braun martin.braun@ettus.com
Sent: Wednesday, 02 April 2025 11:13
To: Kevin Williams kevin.williams@vastech.co.za
Cc: usrp-users@lists.ettus.com
Subject: [EXTERNAL]Re: [USRP-users] connecting the ce clock to a custom rfnoc block

What you're doing is correct. Is it possible there's an old version of the YAML file that is being picked up? You can increase the log level of the image builder, it will tell you which files it's sourcing.

--M

On Wed, Apr 2, 2025 at 10:31 AM Kevin Williams <kevin.williams@vastech.co.za mailto:kevin.williams@vastech.co.za > wrote:

Hi,

I am trying to make use of the CE clock in a custom RFNoC block on an N300.

The way I understand it is to add it to the clock definitions in the block
yaml file:

clocks:

  • name: rfnoc_chdr
    freq: "[]"
  • name: rfnoc_ctrl
    freq: "[]"
  • name: ce
    freq: "[]"

and then just connect it in the image yaml file:

clk_domains:

  • { srcblk: device, srcport: radio,    dstblk: radio0,    dstport:
    radio    }
  • { srcblk: device, srcport: ce,        dstblk: polconv0,  dstport: ce
    }

Running make I get the error: "Invalid clock domain connection: device:ce
→ polconv0:ce (ce is not a clock input)"

I can't find another place to define that clock input for my block?

Kind regards, Kevin


USRP-users mailing list -- usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com mailto:usrp-users-leave@lists.ettus.com

Ah. It sneakily uses the block config which got installed in /usr/local/share/uhd and not the one I am working on. Thanks. From: Martin Braun <martin.braun@ettus.com> Sent: Wednesday, 02 April 2025 11:13 To: Kevin Williams <kevin.williams@vastech.co.za> Cc: usrp-users@lists.ettus.com Subject: [EXTERNAL]Re: [USRP-users] connecting the ce clock to a custom rfnoc block What you're doing is correct. Is it possible there's an old version of the YAML file that is being picked up? You can increase the log level of the image builder, it will tell you which files it's sourcing. --M On Wed, Apr 2, 2025 at 10:31 AM Kevin Williams <kevin.williams@vastech.co.za <mailto:kevin.williams@vastech.co.za> > wrote: Hi, I am trying to make use of the CE clock in a custom RFNoC block on an N300. The way I understand it is to add it to the clock definitions in the block yaml file: clocks: - name: rfnoc_chdr freq: "[]" - name: rfnoc_ctrl freq: "[]" - name: ce freq: "[]" and then just connect it in the image yaml file: clk_domains: - { srcblk: _device_, srcport: radio, dstblk: radio0, dstport: radio } - { srcblk: _device_, srcport: ce, dstblk: polconv0, dstport: ce } Running make I get the error: "Invalid clock domain connection: _device_:ce → polconv0:ce (ce is not a clock input)" I can't find another place to define that clock input for my block? Kind regards, Kevin _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-leave@lists.ettus.com <mailto:usrp-users-leave@lists.ettus.com>