https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665962/cc2652r-guidance-required-for-passive-keyless-entry-key-fob-development/6428803Fri, 24 Jul 2026 20:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e5b43f79-3db6-4236-bb7a-99bc46fb6343JanHi Ram, Happy to help! I believe channel sounding will be applicable to your use-case. I have seen good measurement results in the 10s of meters range which should work well for what youa re looking to implement. The antenna design is critically important for CS. There are a few different antenna design configurations. Typically having more antennas is better for performance but this will depend on factors like the expected environment and housing. I recommend reading details on how CS works at the theoretical level to see how it may impact the performance. The following app note is useful: https://www.ti.com/lit/swra791 For programming, you may use CCS or uniflash. We also support J-Link. For authentication, CS uses standard BLE pairing and authentication. I recommend referencing some of the Bluetooth LE simplelink academy labs to learn more. Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665962/cc2652r-guidance-required-for-passive-keyless-entry-key-fob-development/6427673Fri, 24 Jul 2026 01:28:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0282aa94-d38b-4985-a7ba-5e61e984b48bRamkumar RamasamyHi Jan, Good day! Thank you for sharing the document. I have gone through it, and I have a few questions. My application is for gate access. I will be inside my car while approaching the gate. Will the system be able to detect and allow access in this situation? If yes, what is the maximum reading range or operating distance? I understand that the reading range may depend on the antenna. Could you please explain this in more detail? In the reference design, I noticed that two antennas are used. For my application, do I need one antenna or two? Also, how can I achieve the required reading range for vehicle access? I also have a few questions about the programming. Could you please explain how the programming works and how the authentication process works? I&#39;m finding it a little difficult to understand from the document. If you have any additional documents or guides that explain the system in more detail, could you please share them with me? Thank you, and I look forward to your reply. Best regards, Ram.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1666110/ri-stu-mrd2-availability-or-replacement-for-legacy-rfid-reader-ri-stu-251b/6425512Wed, 22 Jul 2026 15:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:85d55565-a7ab-4411-a473-4151d4f72a2cace jojoYou can try this store; I bought from them once.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1666452/tusb320-request-to-verify-tusb320-type-c-implementation-for-usb-2-0-otgWed, 22 Jul 2026 06:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f84fe242-b82b-427c-9f90-0fdfca633b68akhil haridasPart Number: TUSB320 GATEWAY SOM-USB TYPE C.pdf Hello TI Team, I am updating an existing design by replacing the MICRO-USB connector with a USB TYPE-C connector while maintaining USB 2.0 OTG functionality. To support the OTG /dual role functionality, i have implemented the USB TYPE-C interface using the TUSB230IRWBR. I have completed the Type-c portion ofthe schematic and would appreciate it if you could review it to confirm that the implementation is correct. If there are any design issues,missing connections, or recommended improvements, i would be grateful for you feedback. I have attached the relevant schematic for your review. Thank you for your time and support.TUSB320Wireless Infrastructurehttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1666110/ri-stu-mrd2-availability-or-replacement-for-legacy-rfid-reader-ri-stu-251b/6423820Tue, 21 Jul 2026 14:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9640b572-32ea-4037-a128-141653303a24Rizwan MurjiHi Lucas, I hope all is well. Unfortunately we no longer manufacture this line and thus we do not have any replacement here. If you need something you may need to look at 3rd party vendors to see if there is some surplus available. Unfortunately we do not have a replacement. Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665962/cc2652r-guidance-required-for-passive-keyless-entry-key-fob-development/6423810Tue, 21 Jul 2026 14:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:89c8f27a-555b-4e13-80fe-f6f18d4d8926JanHi Ram, Thank you for reaching out! In this case, I would highly recommend considering the CC27XX family of devices. That family of devices supports Channel Sounding and other car access features (such as connection handover, RAS, etc.). I would recommend the CC2745R10-Q1 LaunchPad for evaluation and take a look at the key_node and car_node examples as these are the ones that incorporate channel sounding. The following SimpleLink Academies showcase how channel sounding works and how to use it: Channel Sounding Getting Started: Car Access Demo — SimpleLink Academy for Low Power F3 SDK Bluetooth Low Energy Channel Sounding Fundamentals — SimpleLink Academy for Low Power F3 SDK Best Regards, Janhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1666110/ri-stu-mrd2-availability-or-replacement-for-legacy-rfid-reader-ri-stu-251bTue, 21 Jul 2026 09:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d0cab7f6-d9bd-4cc7-ada7-58c1906201e8lucas ebboPart Number: RI-STU-MRD2 Hello, We are currently using a Texas Instruments RFID reader in our production equipment and need to purchase a replacement unit. Product details: - Series 2000 Reader System - Reader S251B - Part Number: RI-STU-251B - Internal module references visible on the hardware: - RI-STU-251B-30 - RI-RFMI-0078-30 The product appears to be obsolete and is no longer listed in the TI support portal. Could you please advise: 1. Whether this reader or any compatible spare units are still available for purchase. 2. If not, what is the current Texas Instruments equivalent or recommended replacement. 3. Whether the recommended replacement is compatible with existing Series 2000 RFID transponders and installation. Photos of the equipment are attached for reference. Thank you for your assistance. Best regards, Lucas EBBO Rousset SAS FranceIndustrial AutomationRI-STU-MRD2https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665962/cc2652r-guidance-required-for-passive-keyless-entry-key-fob-developmentTue, 21 Jul 2026 01:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:598184d0-20fc-43fd-83da-226c4aba5001Ramkumar RamasamyPart Number: CC2652R Other Parts Discussed in Thread: CC2745R10-Q1 , UNIFLASH Hi Team, Good day..! I am planning to develop a proof-of-concept Passive Keyless Entry (PKE) system and would appreciate your guidance in selecting the appropriate solution and understanding the overall system architecture. Specifically, I would like to understand the following: 1. How does a Passive Keyless Entry (PKE) system work from key detection to authentication and unlocking? 2. Could you provide design guidelines for the antennas, including recommended PCB layout practices, matching networks, tuning methods, and reference antenna designs? 3. Is an external MCU required, or are there integrated solutions that include both the MCU and RF functionality? 4. What are the essential hardware components required on: * the key fob (transmitter) * the vehicle side (receiver/base station) 5. Which communication technologies are typically used? 6. What factors primarily influence the operating distance (antenna design, transmit power, receiver sensitivity, matching, enclosure, battery voltage, environmental conditions, etc.)? 7. Could you recommend suitable low-cost ICs for both the key fob and vehicle side, along with their datasheets, application notes, evaluation boards, and reference designs? 8. Are there complete reference designs, firmware examples, or software development kits (SDKs) available to accelerate development? My goal is to understand the complete hardware architecture and select the appropriate components before beginning the design. I would appreciate any recommended documentation, application notes, reference designs, or evaluation kits that would help me get started. Thank you for your support. Best regards, RamUniFlashCC2652RCC2745R10-Q1https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665174/trf7970a-linux-software-library-for-trf7970a-to-interface-with-a-mifare-desfire-ev3-rfid-tag/6420369Fri, 17 Jul 2026 06:54:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:190f0b8a-70c0-4229-99bd-936674be4509SiriThe forum support of this product has been reduced to first reference our existing documentation and collateral. TI does not have plans to stop production or place the device into a “Not Recommended for New Design” status, we genuinely feel most questions on these devices can be answered by reviewing existing collateral and previous questions asked. Please feel free to continue to use this device as you see fit for your applications. For support, please take a look to the “Similar Topics” section at the lower right of the thread page. In addition, please consult the existing collateral in the “Technical Documentation” section of the TRF7970A product web page along with the Frequently Asked Question document . Alternatively, you can use the search engine of your choice to look for related E2E threads. With each of these resources we believe it will help with your question. BR Sirihttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1665174/trf7970a-linux-software-library-for-trf7970a-to-interface-with-a-mifare-desfire-ev3-rfid-tagThu, 16 Jul 2026 23:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3012a431-478b-4d20-9ab9-b17c91634c7danh tuan hoangPart Number: TRF7970A We were wondering if TI can propose a software stack (C or C++) that can take advantage of the security feature of EV3? Like anti card cloning, encryption and SDM. @anjli@ti.com @ sworkman@ti.comTRF7970Ahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1664209/rf430cl330h-what-is-the-difference-between-part-number-rf432s72fdmwrgzrq1-and-rf432s72fdkwrgzrq1/6419311Thu, 16 Jul 2026 15:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:62154de1-ecfc-476d-a287-42cb458a2b39Eddie GonzalezThank you, Eshaan.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1664209/rf430cl330h-what-is-the-difference-between-part-number-rf432s72fdmwrgzrq1-and-rf432s72fdkwrgzrq1/6419274Thu, 16 Jul 2026 15:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0811ecd5-9d40-4e98-aad2-28020c9d0f77Eshaan TibrewalaHello Eddie, The RF432S72FD K WRGZRQ was the first product version which was released, and the RF432S72FD M WRGZRQ1 the wake receiver sensitivity and the temperature range was improved. Please reach out through your FAE offline and I can share specifics if you would like. Thank you. Regards, Eshaanhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1663664/ri-trp-dr2b-3d-cad-data-request-of-ri-trp-dr2b-40/6417634Wed, 15 Jul 2026 15:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4427d068-6cf3-47ad-a7f2-d1b870a13995Rizwan MurjiHi Kubra, I hope all is well and apologies for the delay. As this is an older part there is limited support but I will do my best to answer your question. For this device I do not see that we have a CAD drawing. However in the user guide the dimensions are shown. Please refer to page 6 of the following document: www.ti.com/.../scbu053a.pdf Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1664209/rf430cl330h-what-is-the-difference-between-part-number-rf432s72fdmwrgzrq1-and-rf432s72fdkwrgzrq1Tue, 14 Jul 2026 16:07:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:10221fc4-750b-45df-a60a-f04b76e4c8b7Eddie GonzalezPart Number: RF430CL330H Hello, Can you please tell me what the difference between PN: RF432S72FD M WRGZRQ1 vs RF432S72FDKWRGZRQ1 is? Thank you.RF430CL330Hhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1663664/ri-trp-dr2b-3d-cad-data-request-of-ri-trp-dr2b-40Mon, 13 Jul 2026 12:16:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c3657ed5-b858-474c-a456-fe449cfc6783kubra AksuPart Number: RI-TRP-DR2B Hello We need 3D Cad Data of RI-TRP-DR2B-40 with in step format. Could you please share with me by e-mail? If you need that i had a offer for the product i can share it.RI-TRP-DR2Bhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1659455/trf7970a-rx-pin-voltage-level-issue/6410986Thu, 09 Jul 2026 13:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bed005e1-72bd-4f4e-b80e-4fc192f2baa0Rizwan MurjiHi, I apologies for the late reply. Please note that this family of devices have limited support but I will do my best to address you issue. It looks like you have 2 issues: The datasheet describes that in direct mode 0, when the RX pin does not emit waves, it is at a low level. However, when I tested that it does not emit waves, the RX pin is at a high level. Is there any difference between the two? Yes, there is an important functional and operational difference between the two behaviors. In Direct Mode 0 , the digital pin designated to output the raw subcarrier data ( I/O_6 / MISO ) reflects the state of the raw analog digitizer loop. Seeing this pin sit high instead of low during idle states when no tag is emitting waves is an indicator of specific hardware or firmware states. The Key Differences 1. Noise Floor and Gain Saturation Datasheet Low State : The datasheet assumes an ideal, quiet RF environment. When no tag is present and the RF field is active, there should be no subcarrier modulation. The digitizer sees a flat baseline and outputs a stable low logic level . Observed High State : If your pin is sitting continuously high, the internal receiver gain stages are likely saturated, or the system is capturing environmental RF noise or transmitter phase noise. The internal digitizer interprets this continuous baseline offset or noise as a high logic state. 2. Receiver Glitch / Lock-Up State The Cause : The TRF7970A internal analog-to-digital digitizer has an auto-zero or baseline tracking loop. If the transmitter turns on or changes modes abruptly without the receiver being correctly reset, the receiver&#39;s threshold detector can lock up in a logic high state. The Impact : While stuck high, the chip cannot cleanly toggle to represent incoming subcarrier edges from a tag. The host microcontroller will fail to detect the start-of-frame edges because the baseline has shifted. 3. Missing Band-Pass Filter / Sync Settings The Cause : In Direct Mode 0, you bypass the framing hardware, but the internal analog filter chain is still active. If the band-pass filter ( Register 0x0A ) or the modulator control settings are not fully matched to your expected subcarrier frequency (e.g., 424 kHz or 848 kHz), the receiver won&#39;t track the zero-signal baseline correctly, resting at a high rail. How to Fix It Clear the Receiver : Before waiting for data in Direct Mode 0, always issue a Reset RX Gain (0x1A) or Soft Init (0x03) direct command to clear the digitizer loops and force the baseline back to low. Check the Match Network : Check the peak-to-peak AC voltage on the physical RX_IN1 and RX_IN2 pins. If it is too close to (or exceeding) 3Vpp , the transmitter is leaking directly into the receiver, blinding it and forcing the digital output high. Use Direct Mode 1 : If you are using Direct Mode 0 to decode a non-standard or proprietary protocol, consider migrating to Direct Mode 1 or Special Direct Mode . These modes provide an extracted clock alongside the data stream, making the idle state of the pin less susceptible to resting-state high/low logic errors. For the ESD issue: The 20us low pulse is actively emitted by the internal digital control and auto-zero loops of the TRF7970A Analog Front End (AFE). It is a direct reaction to the electrostatic discharge (ESD) event blinding the receiver. Because the system is running in Direct Mode 0 , the framing logic is entirely bypassed. The I/O_6 pin simply reflects the real-time digitized output of the raw receiver chain. Why the 20us Low Pulse Occurs: ESD Induces Receiver Saturation : The electrostatic discharge induces a severe common-mode voltage spike on the RX_IN1 and RX_IN2 pins. This transient energy saturates the internal analog input amplifiers. The 10us Internal Delay : The internal analog filters and gain stages take approximately \(10\ \mu\text{s}\) to desaturate and stabilize after the sudden ESD spike clears. The 20us Pulse (Active Baseline Clamping) : To recover from saturation, the TRF7970A activates its internal baseline tracking and auto-zero loop (clamping circuits). This active discharge process pulls the internal comparator down, forcing I/O_6 to a logic low for roughly 20us . Once the clamping phase completes, the digitizer releases, but because the baseline shifted during the shock, it registers as a permanent high state, flooding the MCU with 0xFF data blocks. To resolve the issue Force a &quot;Reset RX Gain&quot; Command When an ESD spike hits, the baseline recovery loop often overcompensates, latching I/O_6 high permanently. Have the MCU detect if I/O_6 remains high without toggling for more than 50us. If it latches high, immediately send the Reset RX Gain (0x1A) direct command followed by a Soft Init (0x03) command over SPI. This resets the internal thresholds and instantly forces I/O_6 back to its proper resting state. I hope this helps. Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1661815/cc2591-2-2-ghz-peak-observed-in-emi-testingTue, 07 Jul 2026 07:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a0b0e1c0-c3d1-4418-b8c9-0b87ee8518fcAkhil AithalPart Number: CC2591 Other Parts Discussed in Thread: CC2520 Hello, we are using a CC2520 zigbee transmitter in combination with a CC2591 range extender for our product. While carrying out the EMI testing, we find that there exists a 2.2GHz peak along with our intended 2.4GHz signal. The magnitude of the signal is comparable to the 2.4GHz signal. We are using a test software to transmit every 10-100ms and we are able to set the channel and transmit power. What we observe is that the channel and transmit power of our target signal at 2.4GHz is behaving as per our setting, but the unintended signal at 2.2GHz remains unchanged in its frequency as well as power for any setting. I am looking to find the root cause and potential solutions for this. It would be very helpful if you could support. Thank you. Regards, AkhilCC2520CC2591Test &amp; Measurementhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1661168/cc2340r5-openocd-and-cc2340r5-launchpad/6405539Mon, 06 Jul 2026 12:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0cd47fe3-004e-4e5a-9170-a647fccf69d3Andy RutterThank you. I was trying to use the download from https://software-dl.ti.com/ccs/esd/vscode/ti-embedded-debug/ti-openocd.html but that doesn&#39;t have the latest board files.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1659455/trf7970a-rx-pin-voltage-level-issue/6405317Mon, 06 Jul 2026 08:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:00cf6453-9d5b-42fa-8c1e-568feb682fa6user5883945customer tested the EVM board and encountered the same issue.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1661168/cc2340r5-openocd-and-cc2340r5-launchpad/6405280Mon, 06 Jul 2026 08:33:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:546798c7-bc2f-4143-bc8d-a94c258d9504LeaHi Andy ! For the CC2340R5, you should use the https://github.com/TexasInstruments/ti-openocd/blob/ti-release/tcl/board/ti_lp_em_cc2340r5.cfg file. This file is only usable in the ti-openocd repository, not the official upstream openocd repository. Kind regards, Lea