<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://e2e.ti.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Other wireless</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/</link><description>&lt;p style="display:none;"&gt;blank&lt;/p&gt;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: RE: TMS3705: TMS3705 IEC 61000-4-6 Immunity Issue - PCB Layout Recommendation</title><link>https://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/6475052</link><pubDate>Mon, 07 Sep 2026 13:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:93a7b56a-8575-45db-b280-8135cfa11656</guid><dc:creator>Christin Lee</dc:creator><description>Hi, Our team member will get back to end of Tuesday US time.</description></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR PIN MAPPING</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475046</link><pubDate>Mon, 07 Sep 2026 13:43:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b44167d2-babe-4684-9ded-d1fb2d79c452</guid><dc:creator>Lea</dc:creator><description>Hi ! The Main flash, CCFG, SCFG and HSM are all reprogramable. The SRAM is a volatile memory region. This means that upon a power cycle or entering the shutdown power state, the entirety of your SRAM will be lost. Kind regards, Lea</description></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR PIN MAPPING</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6475024</link><pubDate>Mon, 07 Sep 2026 13:19:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f957f6dc-3782-4187-a743-91bee62ba07d</guid><dc:creator>GURUKUMAR YADAV BAIRAGANI</dc:creator><description>Thanks for the clarifiaction,please provide inputs for below one. Could you please clarify the reprogrammable memory ranges for the device based on the memory map below? Main Flash: 0x00000000 – 0x001E7FFF 1,952 KB Application memory 2 KB sectors I understand that this range is reprogrammable. HSM Flash: 0x001E8000 – 0x001FFFFF 96 KB HSM firmware Not treated as normal Main Flash SRAM: 0x20000000 – 0x20047FFF 288 KB CCFG: 0x4E020000 – 0x4E0207FF 2 KB SCFG: 0x4E040000 – 0x4E0403FF 1 KB I understand that the Main Flash range can be reprogrammed. Could you please clarify the following for the other regions? Is the HSM Flash range reprogrammable? If yes, under what conditions or through which programming mechanism? Is CCFG reprogrammable by the customer, or is it programmed/protected by the device/HSM? Is SCFG reprogrammable by the customer, and what is its intended purpose? Is SRAM only volatile working memory, or is there any programming operation that needs to be performed on this range? Could you please identify which of these ranges are customer-programmable, HSM-programmable, read-only, or protected ? This clarification will help us implement the correct programming flow and avoid treating protected or non-programmable regions as normal Flash.</description></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR PIN MAPPING</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6474991</link><pubDate>Mon, 07 Sep 2026 12:42:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:05deec19-7ee4-437a-a2d4-f5d0aba82e74</guid><dc:creator>Lea</dc:creator><description /></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR PIN MAPPING</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping/6474990</link><pubDate>Mon, 07 Sep 2026 12:42:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:501d3cd9-c3ae-44c0-a4d6-682ae7753274</guid><dc:creator>Lea</dc:creator><description>Hi ! On the CC2755P20, the pin 25 is reset pin. You can see this on the datasheet here : https://www.ti.com/lit/ds/symlink/cc2755p20.pdf?ts=1788776126686&amp;amp;ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FCC2755P20 The RESET pin is not necessary for flashing. I&amp;#39;m able to flash a device using only 4 wires : Ground, 3v3, SWDCLK/TCK and SWDIO/TMS. Kind regards, Lea</description></item><item><title>Forum Post: TMS3705: TMS3705 IEC 61000-4-6 Immunity Issue - PCB Layout Recommendation</title><link>https://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</link><pubDate>Mon, 07 Sep 2026 05:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c70bfa9e-e1f6-4292-9c20-db8e9c90a10b</guid><dc:creator>Ryu Yamashita</dc:creator><description>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.</description><category domain="https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/tags/Industrial%2bAutomation">Industrial Automation</category><category domain="https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/tags/TMS3705">TMS3705</category></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6473585</link><pubDate>Fri, 04 Sep 2026 13:11:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3429b58c-0688-4c7b-9b2d-e7b0763d12d9</guid><dc:creator>Hideraldo De Filippo</dc:creator><description>Hello Isaac, Responding to your questions above: 1. What received power are you observing at the TMS37145? We are not using the TMS37145, but only the TMS3705. Our application is reading HDX animal ear tags. 2. Can you identify which image corresponds to the &amp;quot;no response&amp;quot; condition and which corresponds to the &amp;quot;response&amp;quot; condition? Also, could you indicate on the graphs what is being monitored in each waveform? I did not fully understand your previous explanation. I apologize if I was not clear in my previous messages. The way I presented the images may have caused some confusion, so I will present them one at a time. Initially, I wanted to measure the signals at pins 3 and 4 (D_TST and A_TST) of the TMS3705. I observed a difference between the signals when an ear tag is successfully read and when no ear tag is present. However, I could not fully understand the purpose of these pins or whether they could help me diagnose any issue in the circuit. Please see the images below: My other question is regarding the received signal. When monitoring pins 1 and 2 of the TMS3705, when I successfully read the ear tag using only the internal driver, I observe the signals shown below: However, when I use the external driver, the reading is not successful. The signals at pins 1 and 2 are shown below: My question is whether these signals look consistent with what would be expected, and whether using the external driver could cause the receiver circuit to enter some kind of protection or saturation during antenna excitation, potentially preventing the ear tag response signal from being detected by the receiver. 3. What is the distance between the transmitting and receiving devices? I tested several distances. Using only the TMS3705 internal driver, I can read the ear tag at a maximum distance of approximately 3 cm from the antenna. However, when using the external driver, together with the full-bridge and either the 285 &amp;#181;H or 420 &amp;#181;H antenna, I cannot read an ear tag at any distance. 4. What are you receiving from the TMS3705 diagnostic module? Could you please clarify what you mean by the TMS3705 diagnostic module? Are you referring to the response received through pin 14 (SCIO)? If so, below is the signal from an attempted reading using the external driver, showing pins 16 and 14 (TXCT and SCIO): Although some information is transmitted after TXCT goes high, it is not a valid or correct response. As mentioned previously, in addition to the external UCC27424 driver, we are using a full-bridge topology after the driver, which allows us to achieve several hundred volts across the antenna. Since this circuit is also shared with the excitation/reading section for FDX ear tags, our intention is to keep this solution, at least initially, in order to avoid compromising the FDX performance. If it possible. I also have another question regarding the implementation of the filter formed by R27/R28 (4.7 Ω) and C2/C3 (220 pF) shown in the schematic you provided. When I tried to implement this filter after the full-bridge, the signal was significantly degraded. Is this filter essential for the TMS3705 operation? Is there any alternative implementation that you would recommend, considering that we are using an external driver and a full-bridge? I hope this provides a clearer explanation of the measurements and the issues we are observing. I look forward to hearing your thoughts and recommendations. Thank you again for your time and for your willingness to help us. Best regards, Hideraldo</description></item><item><title>Forum Post: CC2755P20: CC2755P207E0WRHAR PIN MAPPING</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1679446/cc2755p20-cc2755p207e0wrhar-pin-mapping</link><pubDate>Fri, 04 Sep 2026 07:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:50b502c0-4b1c-49a7-ad87-912b37267a96</guid><dc:creator>GURUKUMAR YADAV BAIRAGANI</dc:creator><description>Part Number: CC2755P20 Hi Team,does pin 25 is required to program the device using swd protocol ? Please confirm. Thanks!</description><category domain="https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/tags/CC2755P20">CC2755P20</category></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676302/cc2755p20-cc2755p207e0wrhar/6472075</link><pubDate>Thu, 03 Sep 2026 10:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:118e75e7-fde3-4d10-81d9-0d49121c62bd</guid><dc:creator>GURUKUMAR YADAV BAIRAGANI</dc:creator><description>is ID CODE is 0x6BA02477 ? In TI reference manual there is no partiular ID CODE ?? how to proceed ? Please suggest</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6471179</link><pubDate>Wed, 02 Sep 2026 18:16:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8ff863ab-a3a7-4a05-a7b3-73153972f4d3</guid><dc:creator>Isaac Larson</dc:creator><description>Hello Hideraldo, Additionally, can you also show the TXCT of the TMS3705 and the enable signal of the UCC27424 on the oscilloscope capture? Thanks, Isaac</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6471111</link><pubDate>Wed, 02 Sep 2026 17:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:db2be63f-e778-4767-aa16-9384af640444</guid><dc:creator>Isaac Larson</dc:creator><description>Hello Vijay, See the datasheet here . Hello Hideraldo, A few questions to start: 1. What is the received power you are seeing on the TMS37145? 2. Can you label the which image is no response vs response? Also, can you label the plots with what you are monitoring for each waveform? I am not following you explanation earlier. 3. What is the distance between the transmitting and receiving devices? 4. What are you receiving from the diagnosis module of the TMS3705 device? I have received a reference schematic for the TMS3705 and the UCC27424. Please see below: Thanks, Isaac</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6470626</link><pubDate>Wed, 02 Sep 2026 11:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:530fdb6a-1e97-47e9-8261-e6a8ef4f75e1</guid><dc:creator>Hideraldo De Filippo</dc:creator><description>Hello Isaac, Thank you for your help and for the update. I appreciate you looking into this. I will wait for your response and look forward to hearing from you soon. Best regards, Hideraldo</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6469446</link><pubDate>Tue, 01 Sep 2026 16:01:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:dff762bc-f607-44c6-919e-55dabc5702c5</guid><dc:creator>Isaac Larson</dc:creator><description>Hello Hideraldo, Apologies for the delay. I am looking into the follow up question and will provide a response by 09/03. Thanks, Isaac</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6464856</link><pubDate>Thu, 27 Aug 2026 11:33:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b0794ebf-d3dc-4c7e-9227-14c44235bf46</guid><dc:creator>Hideraldo De Filippo</dc:creator><description>Sorry! When I was inserting the images, I ended up inserting the same images more than once. Basically: In the first group on the left: one waveform is when a tag is successfully read, and the other is when there is no tag present during the reading. In the second group: the image on the left shows the tag being read without the drive. The image on the right shows the signal with the drive enabled, but the tag cannot be successfully read.</description></item><item><title>Forum Post: RE: CC3220S-LAUNCHXL: CC3220S-LAUNCHXL: CC3220S SL_AF_RF / SL_SOCK_RAW: millisecond RX indication latency under busy RF conditions</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676697/cc3220s-launchxl-cc3220s-launchxl-cc3220s-sl_af_rf-sl_sock_raw-millisecond-rx-indication-latency-under-busy-rf-conditions/6464707</link><pubDate>Thu, 27 Aug 2026 09:00:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4fd45c20-3b88-4fcd-aa78-b3db2f0a60d6</guid><dc:creator>Ashot Andrieiev</dc:creator><description>Thank you, Josh!</description></item><item><title>Forum Post: RE: CC3220S-LAUNCHXL: CC3220S-LAUNCHXL: CC3220S SL_AF_RF / SL_SOCK_RAW: millisecond RX indication latency under busy RF conditions</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676697/cc3220s-launchxl-cc3220s-launchxl-cc3220s-sl_af_rf-sl_sock_raw-millisecond-rx-indication-latency-under-busy-rf-conditions/6464063</link><pubDate>Wed, 26 Aug 2026 21:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b94dbbe2-b6fd-4bde-9790-989aff151380</guid><dc:creator>Josh Prushing</dc:creator><description>Hi Ashot, I am currently looking into this, I will try to get back to you soon with my initial findings. I see that you have a duplicate post that ended up on another TI forum, I will go ahead and remove that thread and reply to this thread. Best Regards, Josh Prushing</description></item><item><title>Forum Post: RE: TMS3705: TMS3705 and TMS37145 - Communication Error</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6463772</link><pubDate>Wed, 26 Aug 2026 17:12:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7f8c8d34-76c1-4285-b03a-79e4701c0e58</guid><dc:creator>Hideraldo De Filippo</dc:creator><description>Hello Isaac, I measured the signals on D_TST (pin 3) and A_TST (pin 4) , respectively, and I have a few questions about the results. I am sending two images showing the measurements of both signals: one during an attempt in which the tag was successfully read, and another in which the tag was not read. I would like to know whether the measured signals are consistent with the expected behavior of these pins. If they are, what information can we extract from these signals to better understand what is happening and, especially, determine why the TMS3705 is unable to read the tag when I use an external antenna driver ? I also have a question regarding the received signal . I have observed that the signal received by the TMS3705 changes when I use the external driver compared with the configuration without the driver. I believe this change may be affecting the reading performance. The receiver input circuit follows the configuration suggested in the datasheet, using 47 kΩ and 150 kΩ . Since the external driver generates a significantly higher voltage at the antenna, could there be some kind of internal protection or momentary limiting mechanism in the TMS3705 that is being activated due to the higher signal amplitude? For example, some type of input clamp or saturation? Do you have any suggestions for tests or recommendations for this type of situation, considering that the purpose of the external driver is to increase the antenna voltage without affecting the tag signal reception? Thank you.</description></item><item><title>Forum Post: RE: CC2755P20: CC2755P207E0WRHAR</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676302/cc2755p20-cc2755p207e0wrhar/6463532</link><pubDate>Wed, 26 Aug 2026 14:32:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:661b14a8-d548-444a-9706-abfdee270539</guid><dc:creator>Ging Gonzalez</dc:creator><description>Hi, Thanks for sending these details! Indeed, the CC2755P20 provides access to debug subsystem via SWD. To verify connection, you can read the IDCODE register as documented by ARM here: https://support.arm.com/documentation/ihi0031/a/Debug-Port-Registers/Debug-Port--DP--register-descriptions/The-Identification-Code-Register--IDCODE?lang=en And you should get a value like the following: Regards, Ging</description></item><item><title>Forum Post: RE: CC2755P20: DEVICE MARKINGS ISSUE</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676712/cc2755p20-device-markings-issue/6463437</link><pubDate>Wed, 26 Aug 2026 13:29:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8954e200-fab1-4531-9bc2-90e2ae5e0471</guid><dc:creator>Jan</dc:creator><description>Hi, Thank you for reaching out. Due to the P20 having larger flash size, you should use P20 samples to flash P20 projects. Please reach out to your field representative for more information and assist with availability. Best Regards, Jan</description></item><item><title>Forum Post: CC2755P20: DEVICE MARKINGS ISSUE</title><link>https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676712/cc2755p20-device-markings-issue</link><pubDate>Wed, 26 Aug 2026 09:49:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:169dbf48-f835-4f81-92ef-71fe535fe45a</guid><dc:creator>GURUKUMAR YADAV BAIRAGANI</dc:creator><description>Part Number: CC2755P20 Hi Team,can I use this device to program CC2755P207E0WRHAR this,I see marking is P10 and my device is P20 so does it possibleto use or we need to get P20 samples for testing ? Please provide clear explination on this. Thanks!</description><category domain="https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/tags/CC2755P20">CC2755P20</category></item></channel></rss>