# Modifying 4x2 BaseOverlay seems to disable transmit?

**URL:** <https://discuss.pynq.io/t/modifying-4x2-baseoverlay-seems-to-disable-transmit/8098>\
**Category:** Support\
**Created:** [March 2, 2025, 9:06pm UTC](https://discuss.pynq.io/t/modifying-4x2-baseoverlay-seems-to-disable-transmit/8098 "2025-03-02T21:06:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hpowell](https://avatars.discourse-cdn.com/v4/letter/h/779978/32.png) [@hpowell](https://discuss.pynq.io/u/hpowell)\
**Post date:** [March 2, 2025, 9:06pm UTC](https://discuss.pynq.io/t/modifying-4x2-baseoverlay-seems-to-disable-transmit/8098/1 "2025-03-02T21:06:24Z")

</div>

Crosspost from [AMD Customer Community](https://adaptivesupport.amd.com/s/question/0D54U000093pXwLSAU/modifying-4x2-baseoverlay-seems-to-disable-transmit?language=en_US)  
Working with an RFSoC4x2, I am trying to merge the features of RFSoC-MTS and RFSoC-PYNQ by modifying pynq.overlays.base.BaseOverlay and adding modules and variables from the RFSoC. The key changes are shown here ([rfsoc\_array/array.py · 73add84a07c26f92f6271ccee8cfb7120c23d40c · hpowell-umass-ece-phd / RFSoC-Array · GitLab](https://gitlab.com/hpowell-umass-ece-phd/RFSoC-Array/-/blob/73add84a07c26f92f6271ccee8cfb7120c23d40c/rfsoc_array/array.py)), reflecting a set of IP blocks added in Vivado. This modification is intended to be non-invasive, allowing for backwards compatibility to the base.bit for the 4x2. However, when trying to transmit a 915 and 920 MHz tone from two antennas facing a receiving patch array, the tones are not received. Reverting the changes shown in this git diff ([commenting init worked, uncommented adc\_capture lines to test (73add84a) · Commits · hpowell-umass-ece-phd / RFSoC-Array · GitLab](https://gitlab.com/hpowell-umass-ece-phd/RFSoC-Array/-/commit/73add84a07c26f92f6271ccee8cfb7120c23d40c)), the tones are transmitted and received successfully. I am wondering if something about these sets of lines run in the class **init** , or the method memdict\_to\_view() that they call, is resulting in either the transmit IP failing, or some issuye with the RFDC itself. The one meaningful error I get is

```auto
    ADC setup unavailable for tile <xrfdc.RFdcAdcTile object at 0xffff609d9540>.

```

when I try to initialise my custom Overlay class. Any help, suggestions, or questions will be appreciated. Thanks.

---

<div class="post-metadata">

**Author:** ![Sumate](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@Sumate](https://discuss.pynq.io/u/Sumate)\
**Post date:** [May 20, 2025, 12:00pm UTC](https://discuss.pynq.io/t/modifying-4x2-baseoverlay-seems-to-disable-transmit/8098/2 "2025-05-20T12:00:19Z")

</div>

Yes, it’s generally true that directly modifying the 4x2 Base Overlay, particularly the rfsoc\_radio.overlay, can disable or significantly impact transmit functionality on the RFSoC 4x2 board. The base overlay is designed primarily for receiving signals, and while it provides access to the RF DAC, it doesn’t include a robust[,](https://aeccard.site/) ready-to-use transmit functionality. A discussion on the PYNQ forum clarifies this, stating that the rfsoc\_radio.overlay is not designed for transmitting.

---

<div class="post-metadata">

**Author:** ![Theaking03](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@Theaking03](https://discuss.pynq.io/u/Theaking03)\
**Post date:** [May 26, 2025, 6:32am UTC](https://discuss.pynq.io/t/modifying-4x2-baseoverlay-seems-to-disable-transmit/8098/3 "2025-05-26T06:32:10Z")

</div>

Yes, modifying the pynq.overlays.base.BaseOverlay and specifically the 4x2 Base Overlay may indeed disable transmit functionality[.](https://summitcountyauditor.site/) This is likely due to the base overlay’s configuration, which often prioritizes receiving analog signals rather than transmitting.