https://e2e.ti.com/support/rf-microwave-group/rf-microwave/Products covered in this section are Digital Radio (Gray Chip) Products. en-USTelligent Community 13https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1672456/afe7950-afe7950-reference-design/6451231Fri, 14 Aug 2026 15:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9c7f5f9f-f7fc-4bbf-8be5-8792028bc4e8JT MillerI was able to get the reference design working. I recreated the gth xci using the powerpoint as a guide. Vivado was crashing because apparently it was launching too many parallel jobs. I had to restrict the number of parallel jobs to keep Vivado from launching too many processes and crashing the machine: launch_runs synth_1 -jobs 2 wait_on_run synth_1 launch_runs impl_1 -to_step route_design -jobs 2 wait_on_run impl_1 launch_runs impl_1 -to_step write_bitstream -jobs 2 wait_on_run impl_1https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1673414/afe7769d-afe7769-txa-and-txb-on-a-shared-lo-at-different-frequencies-via-nco-how-to-keep-tx-lo-leakage-dc-offset-and-iq-mismatch-calibration-validFri, 14 Aug 2026 14:48:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ed514459-6f0a-4dfa-9315-5a26310ca144Petro KhlyshchyborshchPart Number: AFE7769D Other Parts Discussed in Thread: AFE7769 Setup TXA and TXB share one analog LO (same PLL, one pair). I need them to transmit at two different RF frequencies, a small offset (a few MHz) apart, using the per-channel digital NCO/mixer rather than separate LOs. Question What is the recommended, supported procedure to: Place TXA and TXB at two different frequencies around their shared LO using the digital NCO/mixer, and Have the TX LO-leakage (DC offset) and TX IQ-mismatch calibration pass correctly for both chains afterward? Specifically: Does the calibration flow need to know about the per-chain frequency offset beforehand (i.e. is there a supported way to communicate it before or during calibration), or is it safe to calibrate first at the shared/nominal frequency and apply the NCO offset afterward? Is there a recommended order of operations (calibrate then shift vs. shift then calibrate), and does it differ between LO-leakage/DC-offset calibration and IQ-mismatch calibration? Are these calibrations expected to remain valid after a post-calibration NCO shift of a few MHz, or do they need to be re-run/re-triggered per chain once the offset is applied? Is per-chain NCO placement (independent frequency per chain, shared LO) a supported use case on AFE7769 at all, or is it only intended for symmetric/pair-level offsets (e.g. via low-IF mode, which applies the same offset to both chains of a pair)? Any guidance on the correct sequence, or a pointer to documentation/reference code that covers this, would be appreciated.AFE7769DAFE7769https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1670628/dac39rf20evm-broadband-chirp-generation-with-dds-spi-mode/6449090Thu, 13 Aug 2026 00:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a03c28e8-e058-445e-a04e-6c0da0b6d367Matthew KramerHello, If you installed the latest GUI (V0.4.0) you should see some Python scripts in the installation directory (By default the Texas Instruments directory in my documents). \Texas Instruments\DAC39RF20\v0.4.0\dac39rf20api_examples\!top_level_scripts\dds_vector This script will generate a chirp using the DDS vector engine. I am working on additional scripts for more advanced waveforms (including chirps with 2nd order ramps). These will be included with the next GUI update. Regards, Matthttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1672577/afe7950-clock-synchronization-calibration-for-60-afe7950-multi-channel-direct-rf-data-acquisition-system-8-5-10-5-ghzWed, 12 Aug 2026 07:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6984a557-a07e-42e9-b6fa-0122ddda6e5aJiongyi DuPart Number: AFE7950 Other Parts Discussed in Thread: LMK04832 , LMK04828-EP , LMK04828 Hello TI team, We are designing a multi-channel direct-RF sampling data acquisition and test system operating from 8.5 GHz to 10.5 GHz, and would like your recommendation on clock synchronization and phase calibration using a full TI chipset. System overview: 12 circuit boards, each with 5× AFE7950 (20 TX + 20 RX channels per board); 60× AFE7950 total (240 TX / 240 RX / 120 FB) AFE7950 internal PLL generates the ~12 GSPS DAC sampling clock from a single common 100 MHz TCXO (no external 12 GHz clock distribution) Two-level clock tree: 1× root clock device (LMK04828-EP or LMK04832) → 12× board-level clock devices, each distributing matched REFCLK + SYSREF pairs to 5× AFE7950 + local FPGA All links use JESD204B/C Subclass 1; the 12 board FPGAs are coordinated by a central timing controller All channels must be phase-coherent and phase-repeatable across power cycles Questions: Clock topology: Is a two-level tree (1 root + 12 board-level clock devices, e.g., LMK04828-EP) recommended for deterministic phase repeatability across 60 AFE7950 devices over power cycles? Any preferred alternative? SYSREF: What SYSREF frequency and generation scheme do you recommend (evaluating 12.5 MHz or 6.25 MHz; continuous vs. N-pulse)? Should SYSREF be generated at the root and distributed, or generated per board? Deterministic phase: With each AFE7950’s internal PLL generating ~12 GHz from the common 100 MHz reference, is Subclass 1 SYSREF alignment sufficient for repeatable device-to-device phase across power cycles, or are additional steps required? Calibration: For a phase-coherent multi-channel acquisition system in this frequency range, what is TI’s recommended RX common-pilot and TX feedback-path calibration methodology (NCO phase / delay table compensation), and how to maintain it over temperature? Reference noise budget: With 100 MHz multiplied to ~12 GHz (~41.6 dB theoretical PN degradation within PLL bandwidth), what reference phase noise / jitter performance do you recommend? Should the root be a jitter cleaner (LMK04828 PLL mode) rather than a pure distributor? Reference designs, EVM guidance, or app notes for multi-AFE7950 synchronous systems would be greatly appreciated. Best regardsLMK04832Datacom moduleLMK04828LMK04828-EPAFE7950https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1672456/afe7950-afe7950-reference-designTue, 11 Aug 2026 19:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0a777851-9ea3-47ad-a189-3352079305caJT MillerPart Number: AFE7950 I've inherited the attached TI-provided reference design and Vivado crashes when I try to build the design. There seem to be a few oddities. First is a simple mistake in the create_top_level_wrapper.tcl source (although I don't know how this built for you with the mistake): -make_wrapper -files [get_files ../${project}.srcs/sources_1/bd/${bd_name}/${bd_name}.bd] -top -add_files -norecurse ../${project}.gen/sources_1/bd/${bd_name}/hdl/${bd_name}_wrapper.v +make_wrapper -files [get_files ./${project}/${project}.srcs/sources_1/bd/${bd_name}/${bd_name}.bd] -top^M +add_files -norecurse ./${project}/${project}.gen/sources_1/bd/${bd_name}/hdl/${bd_name}_wrapper.v^M Second, the afe7950_lmfs12410_64b66b_bd.tcl seems to have been generated in 2023.1, but the XCI for the gth is from 2023.2. I updated the script to 2023.2 and that seems to solve the issue, but later trying to build the design it fails. For reference, I am trying to build in 2023.2 on Linux. I don't get any messages, Vivado just quits, then memory usage spikes to the maximum on my machine and I have to pkill -f "vivado" to get the machine back. The AFE_ZCU102_1T1R.pptx accurately describes how the reference design should work. Can you please check the reference design and advise? AFE_ZCU102_1T1R.zipAFE7950Aerospace & Defensehttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1671145/afe7900-rx-nco-change-during-ic-normal-operation/6445562Mon, 10 Aug 2026 15:42:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d38aa936-0140-4bef-8c6c-418dda0a1887arye nudelmani solved it by latte, from regsiter map it was impossible to figure outhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1671738/afe7950evm-post-deletedMon, 10 Aug 2026 03:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:574d5361-ff0c-4ce5-8e42-6f2212cfbafdRogan Ross**POST DELETED**AFE7950EVMhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1671660/afe7903-solderability-issueSat, 08 Aug 2026 16:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:68674677-e355-409f-9ca1-dfdcdbc2e383Mike NeumanPart Number: AFE7903 We've been succesfully using the AFE7903IABJ in a socket since we started the project. We just spun and assembled our first two boards that solder the part on. Both boards have failed in a very pecuiliar way. 1.2V and 1.8V are shorted on the part itself. The balls underneath all look just fine--there are no bridges here. We removed one of the AFE7903's and probed its 1.2V and GND pins and found a 50mOhm resistance between them. 1.8V and GND also have similarly low impedance. But most surprising, there is what looks like a solderball that appeared underneath the heat spreader. There's nothing in our process (entirely SMT) that would account for solder appearing on both boards (assembled on different days) in the same location. See attached images for chip1 (removed from board) and chip2 (still on board). They both have the same blob(?) of solder(?) in the same location. I did not photograph these parts before placing them, but none of the rest in our lot have this defect before soldering. We followed the Loctite GC10 reflow curve #2: The following are "chip1" (taken off PCB): The following are taken from "chip 2" still on the PCB: Please advise on next steps. Burning these rather expensive chips is getting painful.AFE7903Wireless Infrastructurehttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1671604/afe7950evm-need-3d-modelFri, 07 Aug 2026 19:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3126b269-8c2c-4aaa-aeff-4182bf3cb763Kevin O'DonnellPart Number: AFE7950EVM It would be very helpful to have a 3D model of the TI AFE7950EVM evaluation board assembly. Step file of the assembly would be great. ThanksAFE7950EVMWireless Infrastructurehttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1671145/afe7900-rx-nco-change-during-ic-normal-operationThu, 06 Aug 2026 13:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6b54a2d2-d891-4b81-b729-a2cc324c76cfarye nudelmanPart Number: AFE7900 Hi i can attach via mail our initialization file with inital NCO configuration that uses opcode 0x2F, then 0x31 for RX, 0x32 for FB, followed by Tune System opcode 0x36. We need to change all receive NCOs at runtime by +/-N Hz. during the AFE normal operation We tried runtime opcode 0x38 for regular RX: - 0x018 = 0x20 - 0x0A0 = RX channel number (0..3) - 0x0A1 = 0x00 (Band0/NCO0) - 0x0A2..0x0A5 = 32-bit FCW, LSB first - 0x0A6 = 0x03, 0x0A7 = 0x00 - 0x193 = 0x38 - 0x018 = 0x00 Macro status register 0x0F0 always reads 0x00. Replacing status polling with a delay did not help, and we observed no NCO frequency movement. We also tried direct writes to all RX and FB pages: - 0x012 pages: RXA=0x01, RXB=0x02, RXC=0x04, RXD=0x08, FB1=0x10, FB2=0x20 - on every selected page, wrote FMULT to 0x102..0x100 and FCW to 0x0A3..0x0A0 (MSB first) for example - for +1 MHz: 1681 MHz, FCW=0xE0222222, RX/FB FMULT=0x0003E8 This also produced no observable movement. Direct TX NCO changes work through the same FPGA SPI write path (TX page 0x019 and FCW registers 0x353..0x350). However, all AFE SPI reads through our FPGA bridge currently return 0x00. We also noticed that the supplied initialization writes 0x0000E000 to the opcode 0x31/0x32 frequency operands, rather than 0xE0000000. Could you please confirm: 1. The correct supported runtime SPI sequence for all RX and FB NCOs. 2. Whether opcodes 0x38 and 0x39 are supported with this initialization/firmware. 3. The correct FCW operand format and meaning of opcode 0x2F. 4. Whether direct FCW writes require FMULT and/or an additional latch/update command. 5. The required timing-controller state (register 0x015). 6. The correct SPI readback/status procedure. Attached the complete initialization file Thanks. AryeAFE7900https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1670628/dac39rf20evm-broadband-chirp-generation-with-dds-spi-modeWed, 05 Aug 2026 10:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:09edc561-4c42-469d-9f8b-1426a8f95c09firat gPart Number: DAC39RF20EVM Other Parts Discussed in Thread: DAC39RF20 Hi, I purchased the DAC39RF20EVM. How do I generate wideband chirp signals using DDS mode via USB connection? Can I generate complex waveforms with this mode? Can PW and PRI be produced using DDS Mode? Is there a guide on this?DAC39RF20DAC39RF20EVMhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667657/afe7950evm-afe7950evm-modified-for-spi-programming-issues/6436201Fri, 31 Jul 2026 16:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f4d752ae-0ef7-4242-a8ad-ff5b5195131cDavid ChaparroHi LG, Looking at your tiafe_bringup file I can see that the channels are not being taken out of standby mode. Please add the lines below to the end of your bringup and the Rx and Tx will then be in active mode. dev_spi_write(0x0015,0x80); dev_spi_write(0x00ec,0x01); dev_spi_write(0x00f4,0x01); dev_spi_write(0x00e4,0x01); dev_spi_write(0x00ed,0x00); dev_spi_write(0x00f5,0x00); dev_spi_write(0x00e5,0x00); dev_spi_write(0x00ed,0x01); dev_spi_write(0x00f5,0x00); dev_spi_write(0x00e5,0x01); dev_spi_write(0x0015,0x00); Regards, David Chaparrohttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667657/afe7950evm-afe7950evm-modified-for-spi-programming-issues/6435778Fri, 31 Jul 2026 09:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:537c394b-6c68-4bb4-9b6b-ac60d14446b7Loot GoblinHii David, PFA configuration files that we are using to program AFE. PS, config_lmk is used to generate the Format5C file. With that we made a tiafe_bringup.h and with this we programmed the AFE. e2e.ti.com/.../tiafe_5F00_bringup.h e2e.ti.com/.../6443.config_5F00_lmk.txthttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667582/afe7769devm-request-access-to-afe77xxd-latte-gui-secure-software/6432520Wed, 29 Jul 2026 06:49:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:5f648693-7b60-4cd0-8444-de69b50cddadkijin KIMHi Simran, Thank you for granting access! To answer your question, our primary focus is deployment on operator networks, but the design will be flexible enough to support private networks as well, depending on customer requirements. Thanks again for your support. Best regards, RFNISSIhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667582/afe7769devm-request-access-to-afe77xxd-latte-gui-secure-software/6431522Tue, 28 Jul 2026 15:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d1e8d88a-598a-4991-ae67-5aa2e92f94e0Simran NandaHi, Thank you for the details! I have granted you access. Also, is this deployment tied to an operator or private network? BR, Simranhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667997/lp-em-cc2745r10-q1-channel-sounding-check/6431389Tue, 28 Jul 2026 13:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ac1861d2-162c-47b4-82c3-bd460bb4b944Blake SandersHello Baekyeon- Thank you for reaching out. I would be happy to help you get the Channel Sounding demo within the SDK up and running. TI does not currently offer an example application that performs Channel Sounding without using Python, but you are welcome to develop your own application if desired. Regarding the provided Channel Sounding example application, the correct documentation can be found at Channel Sounding - BLE5 Stack User's Guide . This links to the 9.20.01.21 version of the SDK that you are using. Per this documentation, the correct version of Python is 3.10.11. Regarding the compiler, the one which is provided with the default installation of CCS will work just fine. If a compiler is not installed, the download page can be found here . I believe the version you provided is a CCS windows installer file. Have you successfully installed Code Composer Studio on your machine? The installation will provide the necessary compiler. For help, please see the Introduction to the SimpleLink Low Power F3 SDK to get started on CCS and the cc23xx and cc27xx platforms. Best, Blake Sandershttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667582/afe7769devm-request-access-to-afe77xxd-latte-gui-secure-software/6430622Tue, 28 Jul 2026 02:05:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e2bb42ca-1dc3-497f-9d06-b52f2794b293kijin KIMHello Simran, Thank you for your support. Please find the details of our project using the AFE7769D below: Application: High-Power Repeater Use case: RF frequency: 800 MHz to 4.0 GHz IBW (Instantaneous Bandwidth): 100 MHz Output power level: 40W - 100W Timeline to board design and production: Board Design: August 2026 to November 2026 Production: Q1 2027 (Expected) Estimated volume per year: 500 units / year Please grant us access to the AFE7769D design documents and relevant Latte configuration scripts so we can proceed with our evaluation. Best regards, RFNISSIhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667997/lp-em-cc2745r10-q1-channel-sounding-check/6430533Tue, 28 Jul 2026 00:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8b7eb9e9-4005-40c7-9317-35fe307dbac6baekyeon CHOI: CCS_21.0.0.00014_win : simplelink_lowpower_f3_sdk_9_20_01_21 https://software-dl.ti.com/simplelink/esd/simplelink_lowpower_f3_sdk/9.14.02.16/exports/docs/ble5stack/ble_user_guide/html/channel-sounding/channel-sounding.htmlhttps://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667997/lp-em-cc2745r10-q1-channel-sounding-checkMon, 27 Jul 2026 23:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8872176a-6f50-4095-9275-514aebaca240baekyeon CHOIPart Number: LP-EM-CC2745R10-Q1 Hello. I purchased the LP-EM-CC2745R10-Q1(DK) and attempted to run the channel sounding example. I attempted to proceed based on the information provided by TI, but i am facing difficulties because the compiler and Python versions listed are outdated and differ from current versions. I need up-to-date documentation to assist with testing. Additionally, the explanation in the link describes checking logs using Python, but i'm also wondering if there is a way to do it without using Python. I look forward to your reply. Thank you.LP-EM-CC2745R10-Q1https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1667657/afe7950evm-afe7950evm-modified-for-spi-programming-issues/6430084Mon, 27 Jul 2026 16:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:96380d01-cfba-4d33-9f81-bb846b023afdDavid ChaparroHi LG, Can you share the configuration file that you are using to program the AFE? I suspect that the channels are still in standby mode, which is why you see the links are up but see no data. Regards, David Chaparro