# Exporting XTRX register configuration

**URL:** <https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744>\
**Category:** General Discussion\
**Created:** [4 April 2025 22:52 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744 "2025-04-04T22:52:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aardric](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@aardric](https://discourse.myriadrf.org/u/aardric)\
**Post date:** [4 April 2025 22:52 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/1 "2025-04-04T22:52:04Z")

</div>

Is there an undocumented incantation to save all register settings to an ini file from within gr-limesuiteng or would I need to hack something? The objective is to examine registers in detail for debugging and configuration tuning within limeGUI (then perhaps reloading ini file contents into gr-limesuiteng). Is this a reasonable thing to think of doing? This thought came to me while I was trying to get the TX function of the XTRX working. I have been using the XTRX as RX for a while. Perhaps a more reasoned approach would be to generate a configuration with limeGUI to do what I seek ultimately and then load that into gr-limesuiteng. Comments?

---

<div class="post-metadata">

**Author:** ![andrewback](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@andrewback](https://discourse.myriadrf.org/u/andrewback)\
**Post date:** [7 April 2025 12:02 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/2 "2025-04-07T12:02:06Z")

</div>

Tagging @ricardas

---

<div class="post-metadata">

**Author:** ![aardric](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@aardric](https://discourse.myriadrf.org/u/aardric)\
**Post date:** [7 April 2025 15:31 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/3 "2025-04-07T15:31:56Z")

</div>

I have issues to work out before I turn my attention to configuring the radio chip. I am following the path of the thread [Some tech questions about the LimeSDR XTRX ecosystem](https://discourse.myriadrf.org/t/some-tech-questions-about-the-limesdr-xtrx-ecosystem/8632) starting with a gateware upgrade.

---

<div class="post-metadata">

**Author:** ![aardric](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@aardric](https://discourse.myriadrf.org/u/aardric)\
**Post date:** [7 April 2025 16:57 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/4 "2025-04-07T16:57:42Z")

</div>

The FPGA has been upgraded however, the “Hardware version” remains at 18 (as opposed to 2 which I understand is the correct value).  
0: LimeSDR XTRX, media=PCIe, addr=/dev/limepcie0, serial=000000000e5dd8a2  
Expansion name : UNSUPPORTED  
Firmware version : 4  
Gateware version : 1  
Gateware revision : 22  
Gateware target board : LimeSDR XTRX  
Hardware version : 18  
Protocol version : 1  
Serial number : 241031330  
SPI slave devices :  
FPGA  
LMS7002M  
Memory devices :  
EEPROM  
FPGA/FLASH  
FPGA/gold-image  
FPGA/user-image  
GPS Lock:  
GPS - Undefined  
Glonass - Undefined  
Galileo - Undefined  
Beidou - Undefined

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [9 April 2025 06:38 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/5 "2025-04-09T06:38:05Z")

</div>

> [@aardric](#):
>
> the “Hardware version” remains at 18 (as opposed to 2 which I understand is the correct value).

software bug, prints the whole register, which contains two values, hardware version, and bill of material version. Already fixed it.

> [@aardric](#):
>
> Is there an undocumented incantation to save all register settings to an ini file from within gr-limesuiteng or would I need to hack something?

There is no need to for that. After running the GNURadio graph, you can just connect limeGUI and readback the registers.

> [@aardric](#):
>
> Perhaps a more reasoned approach would be to generate a configuration with limeGUI to do what I seek ultimately and then load that into gr-limesuiteng.

You can do that. gr-limesuiteng accepts .ini files for configuration, but it’s purpose is to set specific chip registers that are not controllable through generic SDR parameters. The file is used as a base configuration, and then gr-limesuiteng additionally modifies the generic SDR parameters that comes from GNURadio (LO, LPF, gains, sample rate…).

> [@aardric](#):
>
> The objective is to examine registers in detail for debugging and configuration tuning within limeGUI (then perhaps reloading ini file contents into gr-limesuiteng)

You can connect limeGUI to the XTRX and modify registers while the GNURadio graph is running, just do not modify sampling rate/clock generator, as that would mess up samples data transfer.

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [9 April 2025 06:46 UTC](https://discourse.myriadrf.org/t/exporting-xtrx-register-configuration/8744/6 "2025-04-09T06:46:31Z")

</div>

The data transfer issues in that thread seemed to be caused by the host PC software, the user replied to me in private:

> It seems that the problem with the chopped data has been solved. It was something wrong with the SW on the small computer.  
> I got a PC (normal size), and installed Linux Sparky (Debian based) from scratch - it works.  
> On the small PC with a freshly installed Ubuntu 2404 - it works.  
> On the small PC with a freshly installed Linux Sparky - it works.