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/1684672/tps546d24a-material-composition-information-and-exemption/6496175Mon, 28 Sep 2026 18:08:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7fb8f44a-7022-455a-b71e-6868c00e5a64Caleb PerezHey UDAY. It is used to attach the different leadframes to the die. Due to this, we have the RoHS exemption 7A applied to the device. Thanks, Calebhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685539/cc2340r2-ook-10kbit-s-possible-on-cc2340r2/6495914Mon, 28 Sep 2026 14:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:72aff35d-a596-402f-acc6-94c6f8b33bd4Kilian TimmlerOk, I was able to repeat your configuration with SmartRF Studio 7. Thanks for your help. Best Regards, Kilianhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685539/cc2340r2-ook-10kbit-s-possible-on-cc2340r2/6495874Mon, 28 Sep 2026 14:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:558d21cb-280b-41d1-afa6-cb5f9418e136RGWFYI, OOK with CC2652R (&amp; CC2651R): OOK is mostly for legacy systems so I do not believe there are any plans to support OOK with CC2340.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685539/cc2340r2-ook-10kbit-s-possible-on-cc2340r2/6495820Mon, 28 Sep 2026 13:18:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:781fb9d8-5048-4db8-9eaf-a4446c82d035Kilian TimmlerThe two devices you mentioned only support FSK and GFSK per user manual. This is also a bit of a roadmap question, are you going to support OOK in the future at all?https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685539/cc2340r2-ook-10kbit-s-possible-on-cc2340r2/6495794Mon, 28 Sep 2026 12:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f43ad5c3-bfbc-4e1a-b1b6-4e5b24e3bdc1RGWHi, CC2340 supports only GFSK in Proprietary Radio Modes. Can you use CC2651R or CC2652R that support OOK ?https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685539/cc2340r2-ook-10kbit-s-possible-on-cc2340r2Mon, 28 Sep 2026 09:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d301a823-d0e3-44e2-a1d6-fb8083cacf43Kilian TimmlerPart Number: CC2340R2 Other Parts Discussed in Thread: CC2500 , CC2550 , , CC2652R Hi, I&#39;m just pondering on what part of either CC2500 or CC2550 to use as simple wake up transmitter at 2.4GHz. The product page suggests a CC2340R2 as replacement part but with SmartRF Studio it appears impossible to configure it for OOK at 10kBit/s. Do any of the newer parts support OOK at all? Is there maybe an example application out there? I hope you can help. Best Regards, KilianCC2500CC2652RCC2340R2CC2550https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1685407/cc2642r-q1-cc2642r-q1-radio-testMon, 28 Sep 2026 02:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3a8feede-334e-49f8-b244-fb80989af298xuanfeng fuPart Number: CC2642R-Q1 Hello Our project utilizes the CC2642R-Q1 and requires testing of RF indicators. Could you please inform me if there are any relevant documents and tools available? Thank you!CC2642R-Q1Body Electronics &amp; Lightinghttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1684672/tps546d24a-material-composition-information-and-exemption/6495267Sun, 27 Sep 2026 22:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4b71e826-24cb-4c5d-b0e7-2f078de071daTahar Allagre -assigning to Caleb as Luis still OoO.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1684672/tps546d24a-material-composition-information-and-exemption/6492577Wed, 23 Sep 2026 15:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a996336d-4353-4cad-9adb-51fa9426a06dLuis H. S.Hello Uday, Expect a response next week. Regards, Luishttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1684672/tps546d24a-material-composition-information-and-exemptionWed, 23 Sep 2026 12:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:74266f0d-c67a-4883-93dd-c596b5eeb160UDAY MSPart Number: TPS546D24A Hello team, Thank you for providing the material content information for part number TPS546D24ARVFR . Upon reviewing the data, I noticed that the Clip Adhesive and Die Attach Adhesive sections indicate the presence of lead . Could you please clarify why lead is present in these materials and provide additional details regarding its application? Additionally, I observed that the RoHS exemption 7(a) has been claimed. Could you please explain the basis for applying this exemption to the reported lead content? Thank you for your support. I look forward to your clarification.TPS546D24Ahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1683370/tps62130-discrepant-material-report-ncmr-13040-lfgb101-01129-tps62130rgtr-texas-instruments-incorporated/6491016Tue, 22 Sep 2026 13:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:57ffd053-fd2c-4df1-881d-bd8c8539f979Nikhil S BhardwajHi Axel The datasheet list the most conservative MSL rating Also, individual batches may be qualified at a higher/ better MSL level. In this case it is MSL 1. MSL 1 is actually better in terms of spec than MSL2. MSL 2 can be considered a subset of MSL1. Hence, it is clearly not a specification failure. Regards Nikhilhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1683370/tps62130-discrepant-material-report-ncmr-13040-lfgb101-01129-tps62130rgtr-texas-instruments-incorporated/6489937Mon, 21 Sep 2026 17:58:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f8e83d67-24d5-4a63-a13b-2341d970bcf6Nikhil S BhardwajHi Axel Is the LOT number same as the one attached in the report ? Was this reel procured from ti.com or a distributor ? Regards Nikhilhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6489676Mon, 21 Sep 2026 14:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:27225b83-9984-4eac-813c-ea9688cb67deHideraldo De FilippoHello Isaac, Below, I am answering the questions from your previous message. Over the past week, I tested a circuit similar to the one suggested in your message, using the TMS3705 + UCC27424. I was able to successfully read the transponder using my 285 &#181;H antenna, as shown in the image below. In this test, I was able to read a transponder at a distance of approximately 10 cm. However, I still have not been able to achieve a successful read when I add the final bridge stage to my circuit. As mentioned in previous messages, since we share this stage with other circuits, it would be very beneficial to maintain this architecture. The charge pulse duration is approximately 100 ms for both successful and unsuccessful reads. After triggering a reading, I perform only one reading cycle, consisting of a single charge pulse followed by an attempt to read the transponder. Note: Although I can trigger multiple reading cycles, I am currently triggering only one charge pulse per test to facilitate signal capture and analysis. Regarding your question about the charge duration of approximately 150 ms, this time remains the same in both cases, regardless of whether I use the circuit with the driver and bridge or the driver alone. In both configurations, the charge duration is approximately 100 ms. I also tested shorter charge durations, such as 50 ms, and longer durations, such as 150 ms. However, even with these variations, I was unable to achieve a successful read when using the circuit with the bridge. Below, I am attaching the oscilloscope captures of the TXCT, UCC Enable, Sense, and SFB signals. Since I am using a 2-channel oscilloscope, I had to capture the signals separately. To facilitate comparison between the images, I kept one of the signals as a reference across the different captures. I am also attaching the oscilloscope captures of TXCT, SCIO, and the actual LF signal from the antenna and transponder. As suggested, I implemented an LF pickup coil using an antenna with the same characteristics as the one used in the project, with an inductance of 285 &#181;H and a capacitance of 4.92 nF. Again, thank you for your help us! Best regards, Hideraldohttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1683370/tps62130-discrepant-material-report-ncmr-13040-lfgb101-01129-tps62130rgtr-texas-instruments-incorporated/6489553Mon, 21 Sep 2026 13:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:dd0ffdec-77a4-4d58-8638-17d319f03f95Manish GautamHi Axel, We will check this and get back to you. Regards, Manishhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1680271/cc2755p20-cc2755p207e0wrhar-programming-specifications/6489403Mon, 21 Sep 2026 10:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:482e1e5e-0574-41e3-99a6-9e4eb516848bLeaHi, 1. Yes, you must wait for CMD_WORKING to clear before sending the first HUI word. 2. I&#39;m not sure what you mean about the RXD_FULL question, you should read RXCTL not RXD_FULL 3. TX layout is as such : 4. Yes, huiSize max value is 128kB 5. You will know that the HSM FW update suceeded by listening to the response of your SACI commands : 6. The TRM mentions that these commands must not have happened in the current session : - SACI_CMD_FLASH_ERASE_CHIP • SACI_CMD_FLASH_ERASE_MAIN_APP • SACI_CMD_HSM_GET_SYS_INFO • SACI_CMD_DEBUG_REQ_CHALLENGE You can also read this related E2E thread for more info : CC2745R10-Q1: how to program the HSM to CC2745R10 for third party Kind regards, Leahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1683370/tps62130-discrepant-material-report-ncmr-13040-lfgb101-01129-tps62130rgtr-texas-instruments-incorporatedFri, 18 Sep 2026 00:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7dc03bbe-9797-4044-a7a8-d686fd73e287Axel Antonio Loaeza KimPart Number: TPS62130 QCER NCMR 13040 LFGB101-01129 _ TPS62130RGTR TEXAS INSTRUMENTS INCORPORATED.. - Template (1).pdfTPS62130Industrial Automationhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1682620/trf7970a-unable-to-detect-the-uid-of-the-tag/6487076Thu, 17 Sep 2026 15:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3b42226b-ca85-4650-bbca-86d2b7327c6fRizwan MurjiHi Shubhan, I hope all is well. Unfortunately, we are not familiar with th e SAM 9X75-Curiosity Evaluation Kit as this not a TI kit but one from Microchip technology. If you want more info on using TI tools or evaluation kits for these, I would look at the FAQ for the DLP-7970ABP kit: Frequently asked questions for TRF7970A and TRF7964A devices (Rev. B) Unfortunately, this product line has limited support but hopefully using this information above you can use TI tools to confirm its operating as expected. Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1681365/ri-trp-dr2b-compatibility-of-ri-trp-wr2b-product/6487061Thu, 17 Sep 2026 15:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:790e2c00-a80d-4cbd-bafe-db00544a8a5aRizwan MurjiHi Hyunju, I hope all is well. Please note that for this product line there is limited support, but I will do my best to answer your question. Yes, the RF data frame format remains identical across these transponders. The RI-TRP-WR2B , RI-TRP-W9TD , and RI-TRP-W9UR share the exact same low-frequency (LF) 134.2 kHz Half-Duplex (HDX) Read/Write air interface protocol. The differences between these part numbers lie entirely in their physical form factors, encapsulation, and size (e.g., 32-mm glass tube, 120-mm cylindrical package, and 85-mm disk). I would still recommend that before you purchase a large inventory that you get a tag to verify that this is indeed the case. Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679783/tms3705-tms3705-iec-61000-4-6-immunity-issue---pcb-layout-recommendation/6486894Thu, 17 Sep 2026 13:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:84a8801b-efad-40f0-a578-200d4edbe025Isaac LarsonHello Yamashita-san, Have you followed the guidance within the TMS3705 Application Report ? Can you ensure your component calculations take the cable length (5) and the antenna resonance/Q-factor (4.4/5) into consideration? You can also find an example schematic for &quot;Long Cable Reader System&quot; in section 6. I think the next steps would be to double check the component selection for the items listed above. Additionally, please verify that your high pass and low pass filtering are blocking the necessary incoming noise from the antennas. Thanks, Isaachttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1680271/cc2755p20-cc2755p207e0wrhar-programming-specifications/6485730Wed, 16 Sep 2026 17:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:61ece35d-8d25-4b0e-af50-289e71f325f1GURUKUMAR YADAV BAIRAGANIHi team, Please provide us the inputs for given below questions ? Im unable to find correct answers in user and reference manuals After cmdId=0x21 + huiSize, must we wait for CMD_WORKING clear before the first HUI word? Is RXD_FULL at that point always a reject header? Confirm TX layout: word0 = 0x21, word1 = huiSize (word count, not bytes), then packed LE HUI words with no padding. Confirm max huiSize = 128 kB and 0x82 if larger. After the last HUI word, is the next mailbox event the final result only (auth + program + boot already done), and how long can that take on CC2755P20? Must 0x21 be in a session that has never seen ERASE_*? After MAIN/CCFG/SCFG program in the same session (0x0E/0x0C/0x1A then 0x21, no reset), is that legal