<?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 /><link>https://e2e.ti.com/</link><description>&amp;lt;p style=&amp;quot;display:none;&amp;quot;&amp;gt;blank&amp;lt;/p&amp;gt;</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>Forum Post: TCA9511A: TRA mis-triggered issue</title><link>https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1642922/tca9511a-tra-mis-triggered-issue</link><pubDate>Wed, 06 May 2026 08:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1633416b-0a26-462e-a0ec-06f8cdc6454d</guid><dc:creator>Hang Yang</dc:creator><description>Part Number: TCA9511A Hi Experts, My customer is using TCA9511 + F280039(slave) combination for I2C interface, they are seeing an unexpected fake clock on the SCL line, which is possibly a result of RTA mis-trigger. This issue happens when master send the address to F280039 to request a read. The address has matched the one in the F280039 so the F280039 should send a ACK to inform the master, Below is the waveform: For better illustration, here&amp;#39;s the same picture without any marking Our theory is the RTA is mis-triggered. Since TCA9511 already states the risk of RTA mis-triggering, when the Vol is too high (in this case, the low level onput of TCA9511 is 0.68V), customer should consider lowering the Vol. However, The TCA9511 is on the end-user board, not the customer board, so they can only suggest the end user to decrease the Vol. Before they gives the suggestion, they want to comfirm that if this is the result of RTA, and if droping the Vol to 0.6 (or other recommend threshold) can solve the issue. Could you please comfiming the below item? Is this a behaviour of RTA casuing the false rising edge? If the end-user decrease the Vol to below 0.6V (or other recommend threshold), can it make sure that the RTA won&amp;#39;t be triggered? Regards, Hang</description><category domain="https://e2e.ti.com/tags/power%2bdelivery">power delivery</category><category domain="https://e2e.ti.com/tags/TCA9511A">TCA9511A</category></item><item><title>Forum Post: IWRL6432AOP: Flashing guide for IWRL6432AOP - JTAG</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1642921/iwrl6432aop-flashing-guide-for-iwrl6432aop---jtag</link><pubDate>Wed, 06 May 2026 08:15:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8c2504a2-1de8-4312-aac2-b83a53ab5f81</guid><dc:creator>Ankit Nandha</dc:creator><description>Part Number: IWRL6432AOP Hi TI team, I want to flash my mmwave radar sensor using JTAG connector (10 pin). Can you please tell which debugger i need to flash and also provide the flashing guide?</description><category domain="https://e2e.ti.com/tags/Wireless%2bInfrastructure">Wireless Infrastructure</category><category domain="https://e2e.ti.com/tags/IWRL6432AOP">IWRL6432AOP</category></item><item><title>Forum Post: RE: AM62A7-Q1: SOC Package Length Information For AM62A</title><link>https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642573/am62a7-q1-soc-package-length-information-for-am62a/6334285</link><pubDate>Wed, 06 May 2026 08:14:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:aeef7081-6695-4c78-b5e7-42be2c483b9e</guid><dc:creator>Kallikuppa Sreenivasa</dc:creator><description>Hello Gibbs, Thank you for the note. Regards, Sreenivasa</description></item><item><title>Forum Post: TPS922052: EMC test reports available?</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1642920/tps922052-emc-test-reports-available</link><pubDate>Wed, 06 May 2026 08:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3e288f3f-5991-4e75-8b5b-5ce3465f37ba</guid><dc:creator>Andreas Marti</dc:creator><description>Part Number: TPS922052 Hi Are there any EMC (conducted and/or radiated) test reports, based on the evaluation board TPS922055EVM, available?</description><category domain="https://e2e.ti.com/tags/TPS922052">TPS922052</category></item><item><title>Forum Post: RE: AM2434: Ref: [FAQ] AM2434: Custom Flash Attach Database</title><link>https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642561/am2434-ref-faq-am2434-custom-flash-attach-database/6334284</link><pubDate>Wed, 06 May 2026 08:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a81f1de7-0960-40ed-97e6-f32f6ae18d01</guid><dc:creator>Aryamaan Chaurasia</dc:creator><description>By default, the MCU+ SDK only supports Serial NOR OSPI Flash - S28HS512T and Serial NOR QSPI Flash - S25HL512T from Infineon and NAND OSPI Flash - W35N01JWTBAG. The Flash parts mentioned in the FAQ are not supported by the MCU+ SDK by default, hence, the FAQ contains the values for Flash. The information is provided so that the users can modify the MCU+ SDK. Regards, Aryamaan Chaurasia</description></item><item><title>Forum Post: TAS5805M: Device gets very hot</title><link>https://e2e.ti.com/support/amplifiers-group/amplifiers/f/amplifiers-forum/1642916/tas5805m-device-gets-very-hot</link><pubDate>Wed, 06 May 2026 08:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a8e462b4-33bd-4ea7-bcfe-d84999f1d17f</guid><dc:creator>Hans van Daal</dc:creator><description>Part Number: TAS5805M When playing audio the device temperature goes up to 127 degr.C, even without connecting speakers. PVDD = 24V. When PDN = low, the temperature is good.</description><category domain="https://e2e.ti.com/tags/TAS5805M">TAS5805M</category><category domain="https://e2e.ti.com/tags/Energy%2binfrastructure">Energy infrastructure</category></item><item><title>Forum Post: TPS922052: thermal foldback function</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1642915/tps922052-thermal-foldback-function</link><pubDate>Wed, 06 May 2026 08:09:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f665a8e7-c488-4907-86c4-4210f90e6b1c</guid><dc:creator>Andreas Marti</dc:creator><description>Part Number: TPS922052 Hi Performs the device a complete shutdown at Ttsd=typ 165C even the thermal foldback function is not used and disabled (TEMP pin to AGND pin)?</description><category domain="https://e2e.ti.com/tags/TPS922052">TPS922052</category></item><item><title>Forum Post: PGA970: PGA970 SPI data transfer consistency</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1642913/pga970-pga970-spi-data-transfer-consistency</link><pubDate>Wed, 06 May 2026 08:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:e7523aa2-5e8d-496b-b3f1-679dcea0e9f3</guid><dc:creator>Davide Scarabattoli</dc:creator><description>Part Number: PGA970 Dear TI Team, We have used the PGA970 in some of our projects. Following reports from end customers, we have noticed issues with the consistency of the data provided by the PGA970. In general, we use this component to read LVDT sensors without any further processing. Therefore, the ARM is turned off, and data transfer occurs only via SPI (configured at approximately 900 kHz). Our analysis revealed that the demodulation registers (32 bits wide) read via SPI are corrupted by the PGA970 itself. Specifically, reading the entire register requires two 16-bit SPI requests. Apparently, the PGA lacks a mechanism to prevent these registers from being updated during the read operation. Therefore, when reading a 32-bit register, the first 16 bits (MSB) belong to the first sample, while the second 16 bits belong to the next sample. This issue is most evident when the value straddles the 16-bit boundary (as a raw numerical position). For example (for a generic demodulation register), given two consecutive samples as follows: 0x0000 FFEA 0x0001 0023 sometimes the SPI read result is: 0x0001 FFEA or 0x0000 0023 As seen in the example, the two acquisitions made by the PGA970 may, at the SPI transfer level, be mixed in certain cases, corrupting the final data. Since these issues were identified in a safety-critical project (under DO-178C), I need to provide definitive documentation to submit to the certifying authority (EASA). Is it possible to obtain an “errata” document or an official document confirming this behavior (with a tracking number)? Thanks in advance. DS</description><category domain="https://e2e.ti.com/tags/PGA970">PGA970</category></item><item><title>Forum Post: SN65DSI86: Inquiry regarding upscaling solution from DP (4K) to eDP (7860)</title><link>https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1642912/sn65dsi86-inquiry-regarding-upscaling-solution-from-dp-4k-to-edp-7860</link><pubDate>Wed, 06 May 2026 08:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:66b03f24-2c37-489d-b0c7-2a0204f4d2d8</guid><dc:creator>JH Shin</dc:creator><description>Part Number: SN65DSI86 Hello, My customer is looking for a product that can support upscaling conversion from DP(4K) to eDP(7860). Please recommend any TI products that support the features required by the customer. Thank you.</description><category domain="https://e2e.ti.com/tags/SN65DSI86">SN65DSI86</category></item><item><title>Forum Post: RE: TX7332: TX7332: The Issue with the TX7332ZBX spi read from die2 (group 2 channels)</title><link>https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1642898/tx7332-tx7332-the-issue-with-the-tx7332zbx-spi-read-from-die2-group-2-channels/6334276</link><pubDate>Wed, 06 May 2026 08:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:cded0326-5fd7-4f8e-9316-a390643862d7</guid><dc:creator>Roshan Divakar</dc:creator><description>As these devices are NDA restricted, kindly reach out to us at support_us_afe_tx@list.ti.com for further support.</description></item><item><title>Forum Post: RE: UCC33410: Regarding the IEC 60747-17 (VDE 0884-17) certification of the UCC33410/UCC33020</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1641754/ucc33410-regarding-the-iec-60747-17-vde-0884-17-certification-of-the-ucc33410-ucc33020/6334275</link><pubDate>Wed, 06 May 2026 08:05:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:de3f2924-b957-479f-ad0d-6344ed6a02b1</guid><dc:creator>zi wang</dc:creator><description>Please confirm if PUCC33410 complies with VDE 0884-17 isolation requirements in design, and whether a formal compliance statement can be provided.</description></item><item><title>Forum Post: RE: TCAN1044V: Schematic Review - TCAN1044V-Q1</title><link>https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1641607/tcan1044v-schematic-review---tcan1044v-q1/6334274</link><pubDate>Wed, 06 May 2026 08:04:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:54bc4d60-074e-435f-8a97-911aede374d7</guid><dc:creator>Amirthathaarani S</dc:creator><description>Hi Michael, Thank you for the review and recommendations.</description></item><item><title>Forum Post: RE: LMR38020: HV to LV switching frequency</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1639523/lmr38020-hv-to-lv-switching-frequency/6334265</link><pubDate>Wed, 06 May 2026 08:01:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a4cc2e2c-3c63-411b-a528-16dd081f4103</guid><dc:creator>Che Wen Yeh</dc:creator><description>Hi Niranjan, We have adjusted the output capacitor and Cff to meet our Bode requirements. Another issue is that there is a glitch during power-on, as shown in the waveform below. I noticed the datasheet shows similar behavior— is this normal? Thanks.</description></item><item><title>Forum Post: RE: AM625: Enabling SPI Support in BeaglePlay using TI SDK Image</title><link>https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642572/am625-enabling-spi-support-in-beagleplay-using-ti-sdk-image/6334262</link><pubDate>Wed, 06 May 2026 08:00:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3fed8cdd-c559-471b-97b3-ecc946ffb933</guid><dc:creator>Aparna C Nair</dc:creator><description>I think the SPI driver is enabled in the kernel. Please check. root@beagleplay-ti:~# zcat /proc/config.gz | grep SPI CONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y CONFIG_LOCK_SPIN_ON_OWNER=y CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y CONFIG_QUEUED_SPINLOCKS=y # CONFIG_NFC_NCI_SPI is not set # CONFIG_NFC_ST_NCI_SPI is not set CONFIG_REGMAP_SPI=y CONFIG_MTD_SPI_NAND=y CONFIG_MTD_SPI_NOR=y # CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set # CONFIG_MTD_SPI_NOR_SWP_DISABLE is not set CONFIG_MTD_SPI_NOR_SWP_DISABLE_ON_VOLATILE=y # CONFIG_MTD_SPI_NOR_SWP_KEEP is not set # CONFIG_SENSORS_LIS3_SPI is not set # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_NET_DSA_VITESSE_VSC73XX_SPI is not set # CAN SPI interfaces # end of CAN SPI interfaces # CONFIG_WILC1000_SPI is not set # CONFIG_CC33XX_SPI is not set # CONFIG_WLCORE_SPI is not set CONFIG_TOUCHSCREEN_GOODIX_BERLIN_SPI=m # CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set CONFIG_TCG_TIS_SPI=m CONFIG_TCG_TIS_SPI_CR50=y # CONFIG_TCG_TIS_ST33ZP24_SPI is not set CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y CONFIG_SPI_MEM=y # SPI Master Controller Drivers # CONFIG_SPI_ALTERA is not set # CONFIG_SPI_AXI_SPI_ENGINE is not set # CONFIG_SPI_BITBANG is not set # CONFIG_SPI_CADENCE is not set CONFIG_SPI_CADENCE_QUADSPI=y # CONFIG_SPI_CADENCE_XSPI is not set # CONFIG_SPI_CH341 is not set # CONFIG_SPI_DESIGNWARE is not set # CONFIG_SPI_GPIO is not set # CONFIG_SPI_FSL_SPI is not set # CONFIG_SPI_MICROCHIP_CORE_QSPI is not set # CONFIG_SPI_OC_TINY is not set CONFIG_SPI_OMAP24XX=m # CONFIG_SPI_PCI1XXXX is not set # CONFIG_SPI_PL022 is not set # CONFIG_SPI_SC18IS602 is not set # CONFIG_SPI_SIFIVE is not set # CONFIG_SPI_SN_F_OSPI is not set # CONFIG_SPI_SG2044_NOR is not set # CONFIG_SPI_MXIC is not set # CONFIG_SPI_THUNDERX is not set # CONFIG_SPI_VIRTIO is not set # CONFIG_SPI_XCOMM is not set # CONFIG_SPI_XILINX is not set # CONFIG_SPI_ZYNQMP_GQSPI is not set # CONFIG_SPI_AMD is not set # SPI Multiplexer support # CONFIG_SPI_MUX is not set # SPI Protocol Masters CONFIG_SPI_SPIDEV=m # CONFIG_SPI_LOOPBACK_TEST is not set # CONFIG_SPI_TLE62X0 is not set # CONFIG_SPI_SLAVE is not set CONFIG_SPI_DYNAMIC=y # CONFIG_ZL3073X_SPI is not set # SPI GPIO expanders # end of SPI GPIO expanders # CONFIG_SENSORS_LTC2947_SPI is not set # CONFIG_MFD_CS40L50_SPI is not set # CONFIG_MFD_DA9052_SPI is not set # CONFIG_MFD_MC13XXX_SPI is not set CONFIG_MFD_RK8XX_SPI=y # CONFIG_MFD_TPS65912_SPI is not set # CONFIG_MFD_TPS6594_SPI is not set # CONFIG_MFD_ARIZONA_SPI is not set # CONFIG_MFD_WM831X_SPI is not set # CONFIG_MFD_INTEL_M10_BMC_SPI is not set # CONFIG_MFD_RSMU_SPI is not set # Media SPI Adapters # CONFIG_CXD2880_SPI_DRV is not set # end of Media SPI Adapters # CONFIG_SND_SPI is not set CONFIG_SND_SOC_I2C_AND_SPI=m # CONFIG_SND_SOC_ADAU1372_SPI is not set # CONFIG_SND_SOC_ADAU1761_SPI is not set # CONFIG_SND_SOC_CS35L41_SPI is not set # CONFIG_SND_SOC_CS35L45_SPI is not set # CONFIG_SND_SOC_CS35L56_SPI is not set # CONFIG_SND_SOC_CS4271_SPI is not set # CONFIG_SND_SOC_ES8328_SPI is not set # CONFIG_SND_SOC_PCM179X_SPI is not set # CONFIG_SND_SOC_PCM186X_SPI is not set # CONFIG_SND_SOC_PCM3060_SPI is not set # CONFIG_SND_SOC_PCM3168A_SPI is not set # CONFIG_SND_SOC_PCM512x_SPI is not set # CONFIG_SND_SOC_SSM2602_SPI is not set # CONFIG_SND_SOC_TLV320AIC23_SPI is not set # CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set # CONFIG_SND_SOC_TLV320AIC3X_SPI is not set # CONFIG_SND_SOC_WM8731_SPI is not set # CONFIG_SND_SOC_WM8804_SPI is not set # CONFIG_HID_GOODIX_SPI is not set CONFIG_MMC_SPI=y # CONFIG_LEDS_SPI_BYTE is not set # SPI RTC drivers CONFIG_RTC_I2C_AND_SPI=y # SPI and I2C RTC drivers CONFIG_HWSPINLOCK=y CONFIG_HWSPINLOCK_OMAP=m # CONFIG_ADXL313_SPI is not set # CONFIG_ADXL345_SPI is not set # CONFIG_ADXL355_SPI is not set # CONFIG_ADXL367_SPI is not set # CONFIG_ADXL372_SPI is not set # CONFIG_ADXL380_SPI is not set # CONFIG_FXLS8962AF_SPI is not set # CONFIG_IIO_KX022A_SPI is not set # CONFIG_MMA7455_SPI is not set # CONFIG_AD7606_IFACE_SPI is not set CONFIG_IIO_ST_SENSORS_SPI=m # CONFIG_AD5624R_SPI is not set # CONFIG_AD5686_SPI is not set # CONFIG_BMI160_SPI is not set # CONFIG_BMI270_SPI is not set # CONFIG_BMI323_SPI is not set # CONFIG_FXOS8700_SPI is not set # CONFIG_INV_ICM42600_SPI is not set # CONFIG_INV_MPU6050_SPI is not set CONFIG_IIO_ST_LSM6DSX_SPI=m # CONFIG_BMC150_MAGN_SPI is not set CONFIG_IIO_ST_MAGN_SPI_3AXIS=m # CONFIG_SENSORS_HMC5843_SPI is not set # CONFIG_SENSORS_RM3100_SPI is not set # CONFIG_MPL115_SPI is not set # CONFIG_FPGA_MGR_ALTERA_PS_SPI is not set # CONFIG_FPGA_MGR_XILINX_SPI is not set # CONFIG_FPGA_MGR_ICE40_SPI is not set # CONFIG_FPGA_MGR_MACHXO2_SPI is not set # CONFIG_FPGA_MGR_MICROCHIP_SPI is not set # CONFIG_FPGA_MGR_LATTICE_SYSCONFIG_SPI is not set # CONFIG_DEBUG_SPINLOCK is not set</description></item><item><title>Forum Post: RE: TMS320F28P650DK: Error during import and compilation of the f28p65x_cpu1_echoback_solution routine</title><link>https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1642900/tms320f28p650dk-error-during-import-and-compilation-of-the-f28p65x_cpu1_echoback_solution-routine/6334261</link><pubDate>Wed, 06 May 2026 07:59:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7b12f8e5-439a-4d68-8602-0f5289a26441</guid><dc:creator>Kunal Wasnik</dc:creator><description>Hi , You will need to generate stack files generated from Beckhoff SSC tool in the project directory before importing the project in CCS. EtherCAT Technology Group | EtherCAT Slave Stack Code (SSC) ET9300 You can refer : C:\ti\c2000\C2000Ware_6_00_01_00\libraries\communications\Ethercat\f28p65x\docs for detailed steps. Regards Kunal.</description></item><item><title>Forum Post: RE: AM2434: Ref: [FAQ] AM2434: Custom Flash Attach Database</title><link>https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642561/am2434-ref-faq-am2434-custom-flash-attach-database/6334257</link><pubDate>Wed, 06 May 2026 07:58:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:47eb29c4-440a-4126-8598-c811e33fac64</guid><dc:creator>Andrew Kirby1</dc:creator><description>That&amp;#39;s not what I asked, Does the SDK support all of these devices without requiring modification, or is this information provided so that end users can modify the SDK ? I am more interested in the SBL than the runtime.</description></item><item><title>Forum Post: RE: TPS552852: Suitable for this application?</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1642660/tps552852-suitable-for-this-application/6334254</link><pubDate>Wed, 06 May 2026 07:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4075d6ba-1c73-4d96-bf0a-478558e4e6d4</guid><dc:creator>Fredrick Ze Tiong</dc:creator><description>Hi Bryce. Thanks for assisting me. 2.7V battery is for backup? -Yes. This is a backup system and the 2.7V is a battery for backup . is the 12V system from 12V car battery -No. The 12V system is not a car battery. It can be assumed that the 12V is a very stable power source with minimal voltage ripple. does this device need to startup with 2.7Vin with Vout=0V -Not really. Since this is a backup system. The 2.7V Vin will only be selected by the power MUX if the 12V power fails This info might be useful. I am using a TPS2121 power MUX. The 12V power will either be 0V(when fail) or 12V(when normal). The MUX will switchover to the battery when 12V fails. It can be assumed that the DCDC at the output never sees 2.7V as that is the battery&amp;#39;s voltage when the capacity is low. The battery will mostly be fully charged in an event that the12V rail fails. I am also considering putting the DCDC at the input path instead of the output. That way I can toggle EN to only ON the DCDC whenever 12V rail fails. This is to prevent the DCDC unnecessary power loss when the battery path is not needed. Maybe I should be using the TPS61088 instead if I am opting for this concept. Can you recommend me any boost converters for 3V to 12V @ 500mA too, please? Thanks!</description></item><item><title>Forum Post: RE: CC1352P7: Is there a DMM example pairing TI 15.4 with sub-1 GHz proprietary RF?</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1642678/cc1352p7-is-there-a-dmm-example-pairing-ti-15-4-with-sub-1-ghz-proprietary-rf/6334250</link><pubDate>Wed, 06 May 2026 07:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:21d64a60-890c-49c6-bad8-bb2698eeeee7</guid><dc:creator>Marie H</dc:creator><description>Hi Sharan, As Ryan says, we don&amp;#39;t have any example for this. I am honestly not sure whether this would work, since DMM expects one of the two stacks to be the BLE-Stack. There may be some configurations in DMM that are not possible to adjust. Can you do a comparison of the TI 15.4.Stack DMM example (sensor.c etc) and the BLE DMM example (simple_peripheral.c etc) and see how they initialize DMMPolicy/DMMSch? Cheers, Marie H</description></item><item><title>Forum Post: RE: TMP6-THERMISTOR-DESIGN: The RBias resistor of the TMP6 Thermistor cannot be changed in the Thermistor Design Tool</title><link>https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1636241/tmp6-thermistor-design-the-rbias-resistor-of-the-tmp6-thermistor-cannot-be-changed-in-the-thermistor-design-tool/6334249</link><pubDate>Wed, 06 May 2026 07:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:8ef6ea60-a8a3-484f-8818-94e50c58d88c</guid><dc:creator>Suning Li</dc:creator><description>Hi Alex， Thank you for your reply. Did a storm occur? I hope everything is well with you! Regarding this table, it is perfect. I would like to ask what this average voltage means? Did you test it using the voltage divider method with two resistors? If so, what is the pull-up voltage? i guess it&amp;#39;s 5V? So does the average voltage mean the voltage of the temperature sensing resistor to ground? Thanks!</description></item><item><title>Forum Post: LMK05318BEVM: spikes observed in the phase noise of 100 MHz output from LMK05318B eval board</title><link>https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/1642907/lmk05318bevm-spikes-observed-in-the-phase-noise-of-100-mhz-output-from-lmk05318b-eval-board</link><pubDate>Wed, 06 May 2026 07:52:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f235cdc7-b4fd-4ea0-8f90-f0f6048afc1b</guid><dc:creator>Suchitra  Ramamoorthy</dc:creator><description>Part Number: LMK05318BEVM Other Parts Discussed in Thread: LMK05318B Hello, We are using the LMK05318B eval board to generate 100 MHz from OUT0_P and OUT7_P of LMK05318B. The eval board is operated on a +5V supply, which is connected to Vin1. 10 MHz OCXO(+2dBm) is given at PRIREF_P and 48 MHZ OCXO (0dBm) is given at XO_P connectors on the eval board respectively. The OUT0_P and OUT7_P are enabled to give 100 MHz. When the reference input switching mode is set as Auto Non-Revertive, we get a 100MHz output with a clean phase noise with no spikes in the phase noise plot. The image is attached below. Whereas, when we set the switching mode to manual holdover, we observe spikes in the phase noise of 100 MHz. The image is also attached below. The eval board is being programmed using TICSPro GUI. The programming files of both cases are attached below. 100 MHz auto non revertive.txt 100 MHz manual holdover.txt We want to get a clean phase noise in the manual holdover mode as well. Any insights into this issue would be greatly helpful. Regards, Suchitra Ramamoorthy.</description><category domain="https://e2e.ti.com/tags/LMK05318BEVM">LMK05318BEVM</category><category domain="https://e2e.ti.com/tags/LMK05318B">LMK05318B</category></item></channel></rss>