Other wireless technologies forum - Recent Threads

TPS546D24A: Material composition information and exemption

UDAY MS — Wed, 23 Sep 2026 12:04:26 GMT

Part 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.

RE: TPS546D24A: Material composition information and exemption

Caleb Perez — Mon, 28 Sep 2026 18:08:54 GMT

Hey 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,
Caleb

RE: CC2340R2: OOK 10kBit/s possible on CC2340R2

Kilian Timmler — Mon, 28 Sep 2026 14:43:48 GMT

Ok, I was able to repeat your configuration with SmartRF Studio 7. Thanks for your help.

Best Regards,

Kilian

CC2340R2: OOK 10kBit/s possible on CC2340R2

Kilian Timmler — Mon, 28 Sep 2026 09:59:20 GMT

Part Number: CC2340R2

Hi,

I'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,

Kilian

RE: CC2340R2: OOK 10kBit/s possible on CC2340R2

RGW — Mon, 28 Sep 2026 14:13:57 GMT

FYI, OOK with CC2652R (& CC2651R):

OOK is mostly for legacy systems so I do not believe there are any plans to support OOK with CC2340.

RE: CC2340R2: OOK 10kBit/s possible on CC2340R2

Kilian Timmler — Mon, 28 Sep 2026 13:18:23 GMT

The 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?

RE: CC2340R2: OOK 10kBit/s possible on CC2340R2

RGW — Mon, 28 Sep 2026 12:52:03 GMT

Hi,

CC2340 supports only GFSK in Proprietary Radio Modes.

Can you use CC2651R or CC2652R that support OOK ?

CC2642R-Q1: CC2642R-Q1 Radio test

xuanfeng fu — Mon, 28 Sep 2026 02:04:46 GMT

Part 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!

RE: TPS546D24A: Material composition information and exemption

Tahar Allag — Sun, 27 Sep 2026 22:39:11 GMT

re -assigning to Caleb as Luis still OoO.

RE: TPS546D24A: Material composition information and exemption

Luis H. S. — Wed, 23 Sep 2026 15:34:32 GMT

Hello Uday,

Expect a response next week.

Regards,

Luis

TPS62130: DISCREPANT MATERIAL REPORT NCMR 13040 LFGB101-01129 / TPS62130RGTR / TEXAS INSTRUMENTS INCORPORATED..

Axel Antonio Loaeza Kim — Fri, 18 Sep 2026 00:22:38 GMT

Part Number: TPS62130

QCER NCMR 13040 LFGB101-01129 _ TPS62130RGTR TEXAS INSTRUMENTS INCORPORATED.. - Template (1).pdf

RE: TPS62130: DISCREPANT MATERIAL REPORT NCMR 13040 LFGB101-01129 / TPS62130RGTR / TEXAS INSTRUMENTS INCORPORATED..

Nikhil S Bhardwaj — Tue, 22 Sep 2026 13:22:03 GMT

Hi 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

Nikhil

RE: TPS62130: DISCREPANT MATERIAL REPORT NCMR 13040 LFGB101-01129 / TPS62130RGTR / TEXAS INSTRUMENTS INCORPORATED..

Nikhil S Bhardwaj — Mon, 21 Sep 2026 17:58:16 GMT

Hi Axel

Is the LOT number same as the one attached in the report ?

Was this reel procured from ti.com or a distributor ?

Regards

Nikhil

RE: TMS3705: TMS3705 and TMS37145 - Communication Error

Hideraldo De Filippo — Mon, 21 Sep 2026 14:44:24 GMT

Hello 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 µ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 µH and a capacitance of 4.92 nF.

Again, thank you for your help us!

Best regards,

Hideraldo

TMS3705: TMS3705 and TMS37145 - Communication Error

Vijay Pawar — Thu, 13 Aug 2026 11:36:15 GMT

Part Number: TMS3705

Hello,

We are trying to detect the Transponder TMS37145 using the Basestation IC TMS3705FDRQ1.

The Coil used here is having Inductance of 300uH.

After the charge phase, we are able to see the Diagnostic data on SCIO line, but after that we are not able to receive the expected response.
Attached waveforms for reference.
What could be the reason behind this behaviour from Tag, ?
OR

Can you please share, How the SCIO Data looks like for fresh transponder mode, in read only mode.

Also we are trying to keep TXCT line ON for 50ms and OFF for 50ms in continous Loop.
Can you suggest, if this is right way or can you suggest, proper timing diagram.

Regards,

Vijay Pawar

RE: TPS62130: DISCREPANT MATERIAL REPORT NCMR 13040 LFGB101-01129 / TPS62130RGTR / TEXAS INSTRUMENTS INCORPORATED..

Manish Gautam — Mon, 21 Sep 2026 13:02:32 GMT

Hi Axel,

We will check this and get back to you.

Regards,

Manish

RE: CC2755P20: CC2755P207E0WRHAR programming specifications

Lea — Mon, 21 Sep 2026 10:14:23 GMT

Hi,

1. Yes, you must wait for CMD_WORKING to clear before sending the first HUI word.
2. I'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,
Lea

CC2755P20: CC2755P207E0WRHAR programming specifications

GURUKUMAR YADAV BAIRAGANI — Tue, 08 Sep 2026 08:53:27 GMT

Part Number: CC2755P20

Hi Team,

can you please provide us the programming sepcification for HSM range for CC2755P20 device and provide inputs on how to program the hsm range.

Thanks!

Gurukumar B

TRF7970A: Unable to detect the UID of the tag.

Shubham Singh — Wed, 16 Sep 2026 06:01:07 GMT

Part Number: TRF7970A

Hi TI Team,

Currently, we are working on the bring-up of the TRF7970A RFID module using the SAM9X75-Curiosity Evaluation Kit.

For this setup, we are using the DLP-based TRF7970A module. I have attached an image of the module for your reference

We have completed the required pin multiplexing and device-tree configuration for interfacing the TRF7970A module over the SPI interface using our Yocto build.

The relevant device-tree node and pin-multiplexing configuration are attached below for your reference:

After building the Yocto image and flashing it onto the SAM9X75-Curiosity board, we verified that the TRF7970A driver is loading successfully and the device is binding correctly to the SPI interface.

The corresponding logs are attached below:

However, when using the NFC tool for polling and tag detection, the RFID tag is not being detected, even though the driver is loaded and the module is successfully bound.

The polling output is attached below:

Could you please help us debug this issue and suggest the appropriate steps or checks to identify why the TRF7970A is unable to detect the RFID tag?

In particular, it would be helpful if you could advise us on any additional SPI configuration, GPIO/IRQ configuration, TRF7970A register settings, power/reset sequencing, or NFC tool configuration that we should verify.

Please let us know if you need any additional logs, register dumps, device-tree details, or hardware information from our side.

RE: TRF7970A: Unable to detect the UID of the tag.

Rizwan Murji — Thu, 17 Sep 2026 15:45:10 GMT

Hi Shubhan,

I hope all is well. Unfortunately, we are not familiar with the 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,

Riz

RI-TRP-DR2B: Compatibility of RI-TRP-WR2B Product

HYUNJU LEE — Fri, 11 Sep 2026 05:11:33 GMT

Part Number: RI-TRP-DR2B

Hello,

I am looking for a replacement for a discontinued product.

Could you please confirm whether the RI-TRP-WR2B has the same compatibility as other R/W transponders, such as the RI-TRP-W9TD and RI-TRP-W9UR?

Specifically, does the RF data frame format of the “32-mm Glass Transponder Read Only, Read/Write” described in SCBU019.pdf remain the same across these products?

We would appreciate your official confirmation regarding the compatibility and RF data frame format.

Thank you for your assistance.

Best regards,

RE: RI-TRP-DR2B: Compatibility of RI-TRP-WR2B Product

Rizwan Murji — Thu, 17 Sep 2026 15:38:13 GMT

Hi 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,

Riz

RE: TMS3705: TMS3705 IEC 61000-4-6 Immunity Issue - PCB Layout Recommendation

Isaac Larson — Thu, 17 Sep 2026 13:04:50 GMT

Hello 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 "Long Cable Reader System" 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,
Isaac

TMS3705: TMS3705 IEC 61000-4-6 Immunity Issue - PCB Layout Recommendation

Ryu Yamashita — Mon, 07 Sep 2026 05:28:45 GMT

Part Number: TMS3705

Hello Team,

We are using the TMS3705 and encountered communication failures during IEC 61000-4-6 conducted immunity testing.

After adding a common-mode choke (BNX028-01) to the antenna communication path, immunity performance improved significantly. Based on this result, we suspect that conducted RF noise is coupling into the ANT1/ANT2 signal path.

We have attached the schematic, PCB layout, and test results.

EMC_Translation.pdf

Could you please review the design and advise:

Recommended PCB layout improvements for ANT1/ANT2 routing
Component placement recommendations around the TMS3705
Additional filtering or EMC countermeasures that TI recommends

Any feedback would be greatly appreciated.

Best regards,
Ryu.

RE: CC2755P20: CC2755P207E0WRHAR programming specifications

GURUKUMAR YADAV BAIRAGANI — Wed, 16 Sep 2026 17:11:35 GMT

Hi 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