<?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>Sensors</title><link>https://e2e.ti.com/support/sensors-group/sensors/</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: IWR6843ISK: IWR6843ISK: ISED Canada certification status and certification package</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699557/iwr6843isk-iwr6843isk-ised-canada-certification-status-and-certification-package</link><pubDate>Sat, 21 Nov 2026 00:44:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:65594ca7-0c48-410a-9539-5c4886bdacb4</guid><dc:creator>Michael Mazilu</dc:creator><description>Part Number: IWR6843ISK Is the IWR6843ISK evaluation module certified by ISED Canada (or does it have an ISED certificate / TAC number)? If it is not certified in Canada, can you confirm that in writing? Also, could you point me to the certification package and test reports for the IWR6843ISK (including measured emission bandwidth, harmonics and spurious levels), and the measured antenna radiation pattern data?</description><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/IWR6843ISK">IWR6843ISK</category></item><item><title>Forum Post: RE: DCA1000EVM: DCA1000EVM records 0 packets with IWR6843AOPEVM Rev G (worked before)</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699190/dca1000evm-dca1000evm-records-0-packets-with-iwr6843aopevm-rev-g-worked-before/6545018</link><pubDate>Fri, 20 Nov 2026 23:19:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ed30cfd6-7ce5-47f9-8201-d90f5cfbaddb</guid><dc:creator>David Guirgis</dc:creator><description>Hi Ethan, Let me see if this Is something SW Apps can assist with? Thank you, David Guirgis</description></item><item><title>Forum Post: RE: LM96163: I2c Timing Questions</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699403/lm96163-i2c-timing-questions/6544895</link><pubDate>Fri, 20 Nov 2026 20:19:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:bafc4f32-e008-4948-b38d-0a3e553cac70</guid><dc:creator>Meredith McKean</dc:creator><description>Hi Roger, The stop condition should only take place at the end of a write or read transaction. An example is below. What temperature results are you seeing with the results? Best Regards, Meredith McKean</description></item><item><title>Forum Post: RE: PGA970: persistent OSC_BAD</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699253/pga970-persistent-osc_bad/6544862</link><pubDate>Fri, 20 Nov 2026 19:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:28bcbe06-ed6c-46af-b884-151241dc0d03</guid><dc:creator>Tom Sand</dc:creator><description>Here is a scope capture of testing on GPIO2, routing Cortex-M0 clock running at 1MHz:</description></item><item><title>Forum Post: RE: PGA970: Product recommendation for sensor-conditioning SoC; PGA970 or something else?</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1695701/pga970-product-recommendation-for-sensor-conditioning-soc-pga970-or-something-else/6544846</link><pubDate>Fri, 20 Nov 2026 19:05:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:fc5137fd-6055-4846-a87f-e975837bb8ef</guid><dc:creator>Eric.Preiss</dc:creator><description>Hi Tom, I&amp;#39;m still getting up to speed with supporting PGA970. I responded to your other thread. I&amp;#39;ll get my board up and running early next week and get back to you on your other questions. Best, Eric</description></item><item><title>Forum Post: RE: PGA970: persistent OSC_BAD</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699253/pga970-persistent-osc_bad/6544844</link><pubDate>Fri, 20 Nov 2026 19:04:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3265d772-1ff3-49fc-a689-5f2d9b0da0db</guid><dc:creator>Eric.Preiss</dc:creator><description>Thanks, Tom. Yes, I meant one of the divided down clocks. Thanks for sending the zoomed out images. Yes, this appears to be a problem with the PGA970 device. I have EVM&amp;#39;s and will test on one of my boards. A customer has followed the same procedure and posted to E2E in the past, and was able to output the OSC8MHZ to GPIO2, to verify the oscillator was good. All of your scope shots point to a bad oscillator. Best, Eric</description></item><item><title>Forum Post: RE: PGA970: persistent OSC_BAD</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699253/pga970-persistent-osc_bad/6544838</link><pubDate>Fri, 20 Nov 2026 18:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ba917f32-50db-41ec-bdc7-615fc22c4ca7</guid><dc:creator>Tom Sand</dc:creator><description>Here is a scope capture of testing on GPIO2, routing Cortex-M0 clock running at 2MHz:</description></item><item><title>Forum Post: RE: PGA970: persistent OSC_BAD</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699253/pga970-persistent-osc_bad/6544834</link><pubDate>Fri, 20 Nov 2026 18:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c94f289d-7b43-4a37-bac5-364e5e5f1198</guid><dc:creator>Tom Sand</dc:creator><description>Here is a scope captures of testing on GPIO2, routing OSC8MHz. Will try to follow up with captures of Cortex-M0 clk-2MHz, and Cortex-M0 clk-1MHz.</description></item><item><title>Forum Post: RE: TMP116: RESET content of TMP116 EEPROM3</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699511/tmp116-reset-content-of-tmp116-eeprom3/6544829</link><pubDate>Fri, 20 Nov 2026 18:48:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:735f21b7-17b1-48cf-9855-6b53f806fecb</guid><dc:creator>Meredith McKean</dc:creator><description>Hi Thomas, The EEPROM registers include the NIST information for traceability. If you wish to verify NIST traceability, this information is necessary to track the device. If NIST traceability is not required, the EEPROM can be used. Best Regards, Meredith McKean</description></item><item><title>Forum Post: RE: PGA970: persistent OSC_BAD</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699253/pga970-persistent-osc_bad/6544825</link><pubDate>Fri, 20 Nov 2026 18:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4689969c-f385-4697-b30c-0359bb2e3c46</guid><dc:creator>Tom Sand</dc:creator><description>Hello Eric, Thank you for following up with us. I tried resetting PSMON2 by writing 0x00 to it instead of 0x10; same result, both right away and several seconds later and really all of the time reads of PSMON2 are reporting 0x10. For the slower oscillator frequencies did you mean to change some setting controlling the primary internal oscillator? I&amp;#39;m not familiar with how to do that. If you meant to place alternate outputs into the MUX, I tried routing the Cortex-M0 clock to the MUX instead of the internal oscillator, and to configure the Cortex-M0 clock alternatively as 2MHz and as 1MHz. The results all look messy. I&amp;#39;ve been trying to upload the photos into this post, but the E2E website seems to be having a lot of problems. I&amp;#39;ll go ahead and try to post this text portion and follow up with the scope traces. We&amp;#39;ll consider swapping out the PGA970 chip, we don&amp;#39;t have anything other than the PGA970EVM itself, but it looks like they&amp;#39;re in stock at Digikey. Is there anyone who can duplicate our testing on a known-good PGA970EVM (or other hardware with a PGA970 on it)? Thank you, -Tom</description></item><item><title>Forum Post: RE: IWRL6432: IWRL6432 SPI SBL Users Guide</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699359/iwrl6432-iwrl6432-spi-sbl-users-guide/6544770</link><pubDate>Fri, 20 Nov 2026 17:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d0bb86f1-e42b-449b-aaad-0f7a12a3fe10</guid><dc:creator>Josh Deardorff</dc:creator><description>Hi Gil Jae, Here&amp;#39;s the guide, specifically for loading images over SPI with the SBL ! Best, Josh</description></item><item><title>Forum Post: RE: IWRL6432FSPEVM: Communication protocol of IWRL6432FSPEVM mmWave sensor to interface with raspberry pi 5 or other MCU.</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699317/iwrl6432fspevm-communication-protocol-of-iwrl6432fspevm-mmwave-sensor-to-interface-with-raspberry-pi-5-or-other-mcu/6544760</link><pubDate>Fri, 20 Nov 2026 17:46:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2033e259-fb08-4f87-840a-23875ece15d5</guid><dc:creator>Josh Deardorff</dc:creator><description>Hi Pisit, Glad to here you got the device up and running. The firmware of the device is fully open and modifiable to fit your needs. What this means is the required communication is completely dependent on the firmware you have setup. If you&amp;#39;re using an out-of-box demo (like the Motion and Presence Detection or mmWave Demo), the Pi can absolutely interact with the IWRL6432FSP EVM over UART. These demos are setup to use UART to receive ASCII CLI commands. The Pi just needs open the UART connection at 115200 baud, send radar configuration commands, and then the radar will start sending data down the UART line. The configuration commands for these demos are described in the mmWave L SDK 5 documentation (not all parameters are required). I&amp;#39;d omit the baudRate command for now to simplify setup (it changes the baud of the radar UART port). There are example radar configuration files in: /examples/mmw_demo/motion_and_presence_detection/profiles/xwrL64xx-evm/ With that said, since you have Python available on the Pi, the easiest way to get started is definitely with our mmWave Data Recorder . You can run the provided Python script directly on the Pi, no protocol/sequencing needed, the script handles it for you. It&amp;#39;s a perfect reference for how you can interact with the device using Python! Best, Josh</description></item><item><title>Forum Post: RE: TDA4AH-Q1: TDA4-Findings from Camera Detection and I2C Analysis on J784S4 EVM with J7EXPA01EVM Fusion Board</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1695115/tda4ah-q1-tda4-findings-from-camera-detection-and-i2c-analysis-on-j784s4-evm-with-j7expa01evm-fusion-board/6544742</link><pubDate>Fri, 20 Nov 2026 17:31:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c5fc6f5e-ebf9-4573-9a0c-51d1f8caa66b</guid><dc:creator>Jared McArthur</dc:creator><description>Hi Prachi Paithankar , This seems like a hardware issue to me. Are you able to test the second deserializer on the board? Best, Jared</description></item><item><title>Forum Post: RE: TMP6EVM: TMP6EVM – Request for Daughterboard 3D CAD Model</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699451/tmp6evm-tmp6evm-request-for-daughterboard-3d-cad-model/6544741</link><pubDate>Fri, 20 Nov 2026 17:31:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:600b63ab-a831-4f7c-9213-922a7a5fb707</guid><dc:creator>Meredith McKean</dc:creator><description>Hi Ciara, I sent you an email. Best Regards, Meredith McKean</description></item><item><title>Forum Post: RE: IWRL6432AOPEVM: I am trying to use it for object detection but unable to start it</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699368/iwrl6432aopevm-i-am-trying-to-use-it-for-object-detection-but-unable-to-start-it/6544732</link><pubDate>Fri, 20 Nov 2026 17:25:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:06107c4b-a44c-4e79-9f29-81a54768ae26</guid><dc:creator>Josh Deardorff</dc:creator><description>HI Kiran, Sorry for the confusion, you actually need the MMWAVE-L-SDK 5 (current version 5.5.4.2) for the IWRL6432AOP. We have a guide dedicated to first time bring-up of the IWRL6432AOP ! In general, we have many resources on developing with the mmWave Radar in our Radar Toolbox , with lots of demos and examples. The Motion and Presence Detection demo (in both the Toolbox and SDK) is the best demo to start with. I recommend using our Industrial Visualizer to get started. You actually don&amp;#39;t need CCS to get started - we ship binaries you can flash straight to the device in both the SDK and Toolbox. However, you can use the &amp;#39;Resource Explorer&amp;#39; view in CCS to directly import projects when you want to start modifying firmware. Let me know if you run into any issues! Best, Josh</description></item><item><title>Forum Post: TMP116: RESET content of TMP116 EEPROM3</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699511/tmp116-reset-content-of-tmp116-eeprom3</link><pubDate>Fri, 20 Nov 2026 16:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9b140f99-9a95-413e-9136-c40bbe8bce87</guid><dc:creator>Thomas LE BIVIC</dc:creator><description>Part Number: TMP116 Hello, Can you clarify the EEPROM[4:1] content out of the box because informations in datasheet are unclear : It&amp;#39;s written that EEPROM[4:1] are preprogrammed during manufacturing with the unique ID that can be overwritten. In order to support NIST traceability, do not delete or reprogram EEPROM[4:1]. are preprogrammed during manufacturing with the unique ID that can be overwritten. In order to support NIST traceability, do not delete or reprogram EEPROM[4:1]. But later for EEPROM3 reset value is said to be 0x0000 ? Thank you, Regards, Thomas,</description><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/TMP116">TMP116</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/Test%2b_2600_amp_3B00_%2bMeasurement">Test &amp;amp; Measurement</category></item><item><title>Forum Post: RE: TMP411: MSL level</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699085/tmp411-msl-level/6544704</link><pubDate>Fri, 20 Nov 2026 16:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ee8e65f3-4dd5-401b-b28d-21fad611570b</guid><dc:creator>Meredith McKean</dc:creator><description>Hi Jeff, Yes, we are planning to update the datasheet. I can&amp;#39;t give you an exact date. Best Regards, Meredith McKean</description></item><item><title>Forum Post: AWR2544LOPEVM: Support for advanced frames</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699505/awr2544lopevm-support-for-advanced-frames</link><pubDate>Fri, 20 Nov 2026 16:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:12e4df6b-4ef6-4e36-90c5-a9d13826ecec</guid><dc:creator>Ljubo Mercep</dc:creator><description>Part Number: AWR2544LOPEVM Other Parts Discussed in Thread: AWR2544 , Hello, Does the AWR2544 MMIC support advanced frames, and does the application included with the AWR2544LOPEVM devkit support it as well? If so, is there example code using this feature? Thank you.</description><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/Advanced%2bDriver%2bAssistance%2bSystems%2b_2800_ADAS_2900_">Advanced Driver Assistance Systems (ADAS)</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2544LOPEVM">AWR2544LOPEVM</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2544">AWR2544</category></item><item><title>Forum Post: AWR2544LOPEVM: Reference radar processing pipeline for AWR2544</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1699504/awr2544lopevm-reference-radar-processing-pipeline-for-awr2544</link><pubDate>Fri, 20 Nov 2026 16:15:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:78b7c35b-3cd0-47bb-9073-555e3875a934</guid><dc:creator>Ljubo Mercep</dc:creator><description>Part Number: AWR2544LOPEVM Other Parts Discussed in Thread: AWR2544 , AWR2243 , AWR2944 Hello, Is there a reference radar processing pipeline for the AWR2544 devkit, written in Matlab/Python or C/C++, which can be executed on a computer or on a DCA1000, and produces point clouds? We worked with similar reference code for the AWR2243 cascade devkit, which included a windows software package to interface with the DCA1000. Alternatively, we would interested in reference code for the AWR2944, such as the one demonstrated in this video: https://www.ti.com/en-us/design-development/educational-resources/video/6387477023112 Thank you.</description><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2243">AWR2243</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2944">AWR2944</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/Advanced%2bDriver%2bAssistance%2bSystems%2b_2800_ADAS_2900_">Advanced Driver Assistance Systems (ADAS)</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2544LOPEVM">AWR2544LOPEVM</category><category domain="https://e2e.ti.com/support/sensors-group/sensors/tags/AWR2544">AWR2544</category></item><item><title>Forum Post: RE: IWR6843ISK-ODS: AWR6843AOP In-Cabin Occupancy Detection: Documentation Reference for CLI Configuration Parameters</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1697303/iwr6843isk-ods-awr6843aop-in-cabin-occupancy-detection-documentation-reference-for-cli-configuration-parameters/6544595</link><pubDate>Fri, 20 Nov 2026 15:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4992e834-698b-4571-834e-2b51dda5c98b</guid><dc:creator>Ryan Brown1</dc:creator><description>Thanks. I notice that you are missing &amp;quot;profileCfg 1&amp;quot; that is included in all \tools\visualizers\InCabin_CPD_w_Classification_GUI\config_file files. There are also several CLIs after &amp;quot;fovCfg&amp;quot; which have been left out. Is there a specific reason for this? Also, I&amp;#39;ve noticed that the Radar device is not calibrated ( compRangeBiasAndRxChanPhase) which could affect your results. You can review /packages/ti/demo/xwr68xx/mmw/docs/doxygen/html/index.html and \docs\mmwave_sdk_user_guide.pdf, however these have no guidance on the Cfar and Angle Cfgs. Regards, Ryan</description></item></channel></rss>