Re: Endian-ness of USRP x410 device

Hey Jons,

our mailing list server is having some issues. Our maintainer knows about this, but I can't give you a timeline for when it'll be up again.

Like Marcus says, don't worry about the network endianness. We have a bunch of things going on to flip bytes around (among other things, it saves us some CPU load when receiving data), but you need to worry about the Noc-Shell interface. I recommend looking at some of our existing blocks as examples.

--M

On Wed, Nov 26, 2025 at 4:01 PM Marcus Müller <mmueller@gnuradio.org> wrote:

Hi Jons,

On 2025-11-26 9:17 AM, Jons wrote:
> Hi all,
> This is a specific question about USRP devices and I am posting it here because I am
> unable to send it to the usrp-users mail chain.

Uh, I'm not with Ettus anymore, but that's no good. All you should need to do is send an
email from your email address to usrp-users-join@lists.ettus.com ; after you've gotten a
confirmation email and confirmed, you should be able to post there.

> I am trying to integrate a custom noc
> block into the x410 device and when going through the email archive and a doc in the
> github repo I saw that the OTW data transmission is in Big Endian.

I'll go with: that's a time-honoured tradition :D

> Can someone help me out
> in understanding how it will affect a noc block?

Not at all – you're not interfacing with the network directly, but with your nocshell, and
your verilog module / VHDL arch sees the sample data as sample-wide array (CHDR_W is the
naming convention for the width parameter, if you want to look through the source code of
Ettus' blocks), typically.

Best,
Marcus