<?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>Sub-1 GHz</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/</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: CC1312PSIP: CC1312PSIP: current consumption of COMPB + Reference DAC in standby</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1697731/cc1312psip-cc1312psip-current-consumption-of-compb-reference-dac-in-standby/6539614</link><pubDate>Mon, 16 Nov 2026 10:58:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2ee65430-010d-4660-a27b-a4b632683203</guid><dc:creator>Daniel Guarecuco Aguiar</dc:creator><description>Hi Yaşar, The reported current consumption for the datasheet is: Ultra low-power sensor controller consumption: * 30 μA in 2 MHz mode * 808 μA in 24 MHz mode You can measured the current consumption when using COMPB by flashing a Sensor controller project, these guides are very useful Sensor Controller Fundamentals I don&amp;#39;t believe there is an example that uses COMPB, however the documentation should help you getting started with a demo. Open Sensor Controller Studio &amp;gt; F1 to open the Help Viewer &amp;gt; Task Event Handling &amp;gt; COMPB Event Trigger Best regards, Daniel</description></item><item><title>Forum Post: CC1312PSIP: CC1312PSIP: current consumption of COMPB + Reference DAC in standby</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1697731/cc1312psip-cc1312psip-current-consumption-of-compb-reference-dac-in-standby</link><pubDate>Sat, 14 Nov 2026 20:29:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:38d11af5-ebec-4e53-be02-988b2a9d7b41</guid><dc:creator>Yaşar BOLATeX</dc:creator><description>Part Number: CC1312PSIP Other Parts Discussed in Thread: CC2650 Hello, We plan to use the low-power clocked comparator (COMPB) on CC1312PSIP to wake up the Sensor Controller, and then the System CPU, from standby. The Sensor Controller is idle and only COMPB with the Reference DAC as its reference is enabled. The CC1312PSIP data sheet (SWRS293) gives 0.9–1.0 &amp;#181;A for standby, but section 8.15.4.1 has no current consumption value for the clocked comparator. The CC2650 data sheet listed 362 nA for it. Could you please tell us: 1. What is the typical additional standby current with COMPB enabled? 2. What is the additional current of the Reference DAC and the LPM bias module when they provide the COMPB reference in standby? 3. Is there an example project (Sensor Controller Studio or SDK) that uses the COMPB event trigger to wake up from standby? Conditions: VDDS = 3.0–3.6 V, 25 &amp;#176;C, DC/DC enabled, SCLK_LF from XOSC_LF. Thank you. Yaşar</description><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC1312PSIP">CC1312PSIP</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC2650">CC2650</category></item><item><title>Forum Post: CC1312PSIP: CC1312PSIP: DIO state during power-up / reset / boot, nRESET RC, pin leakage</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1697626/cc1312psip-cc1312psip-dio-state-during-power-up-reset-boot-nreset-rc-pin-leakage</link><pubDate>Fri, 13 Nov 2026 13:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b83f9b46-f9b4-465e-a80c-61ab6fb8c76b</guid><dc:creator>Yaşar BOLATeX</dc:creator><description>Part Number: CC1312PSIP Hello, This is related to an earlier thread (E2E 1690754), where Bun Kuch kindly answered our first questions on the CC1312PSIP on October 20. Our follow-up in that thread (open points 4a-4c and 6, October 21) has not been answered by TI yet, so we are opening a new question. Since then we have simulated the power-up of our board in detail and need a few clarifications to close the design. The open points are restated below together with new ones. Context: four DIOs of the CC1312PSIP (DIO17..DIO20) drive the address and enable inputs of an analog multiplexer and the shutdown input of an op-amp. Each line has an external pull-down (1 MOhm on DIO18..DIO20, 220 kOhm on DIO17). We want these lines to stay low from power-up until the application drives them, so the multiplexer stays disabled at the lowest gain. In addition, DIO_5 (from our earlier thread) starts a self-test pulse of a protection stage; an unintended high level on DIO_5 during power-up, reset or boot would trigger it, so DIO_5 must also stay low until the application drives it. 1) Internal pull-up during reset / boot (open points 4a-4c) The TRM (SWCU185G, p.1133-1134 and p.1223-1233) gives IOCFGn reset value 0x00006000 (PULL_CTL = no pull, IE = 0), and section 13.5 (p.1096) says the pins are tri-stated at power-on and reset. In the earlier reply a ~100 kOhm pull-up on the DIOs was mentioned. a) Is there any pull-up (or pull-down) active on DIO_5 and DIO17..DIO20 between power-on, reset release, ROM boot and the first application write? If yes, in which phase, on which DIOs, and is it enabled by hardware or by ROM / bootloader code? Can ROM or bootloader code actively drive any of these DIOs as an output? Please answer phase by phase if possible: power-on and brown-out reset, pin reset (nRESET) and SYSRESET, ROM boot, serial bootloader (including entry through the CCFG backdoor), standby wake-up. b) Its value: SWRS293 p.34 (section 8.15.6.1) gives 73 uA at VDDS = 1.8 V and 282 uA at VDDS = 3.8 V (pad at 0 V, typical, 25 C), i.e. about 25 kOhm and 13 kOhm, not 100 kOhm. Which is correct? c) We understand these are typical values only. Please give the guaranteed maximum pull current over -40..105 C at VDDS = 3.6 V (and the minimum, if specified). 2) nRESET internal circuit (T-1) The module datasheet (SWRS293 p.11, p.13) shows 100 kOhm and 100 nF on nRESET. Is the 100 nF between nRESET and GND? What are the tolerances of the 100 kOhm and 100 nF, and the nRESET input thresholds (VIH / VIL, hysteresis)? Was the &amp;quot;100 kOhm pull-up&amp;quot; in the earlier reply this nRESET resistor rather than a DIO pull-up? 3) Reset to Active timing (T-2) Does &amp;quot;Reset to Active 850-4000 us&amp;quot; (SWRS293 p.23) include the module&amp;#39;s nRESET RC delay at power-up, or does it start after nRESET is released? 4) Pin state below the POR threshold (T-3) While VDDS is below the POR threshold (0 to about 1.55 V), are the DIOs guaranteed high-impedance, or can they be driven transiently? 5) Leakage and capacitance of a high-impedance pin (T-4) For a DIO with IE = 0 and no pull, what is the maximum leakage current over -40..105 C at VDDS = 3.6 V, and what is the pin capacitance? (With our 1 MOhm pull-down, more than about 0.8 uA of leakage would lift the line above VIL.) 6) DIO16 / DIO17 reset values (T-5) IOCFG16 and IOCFG17 reset to 0x00086000 and 0x00106000 (TRM p.1218), i.e. bit 19 / bit 20, shown as RESERVED in the field table, is set. What do these bits do, and do they change the electrical state of DIO16 / DIO17 during reset or boot (DIO17 is also the JTAG TDI pin)? 7) Output edges and 2 mA drive (T-6, and open point 6) Rise / fall times versus IOCURR, IOSTR and SLEW_RED, VOH / VOL in 2 mA mode, and the VDDS levels at which IOSTR = AUTO changes drive strength. An IBIS model would answer several of these at once; we understand none is planned, so datasheet-level values are enough for us. Thank you very much for your help.</description><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC1312PSIP">CC1312PSIP</category></item><item><title>Forum Post: RE: CC1312PSIP: Which FCC grant covers the Wi-SUN Mode #5 (300 kbps) PHY that SWRA797 lists as certified?</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1695088/cc1312psip-which-fcc-grant-covers-the-wi-sun-mode-5-300-kbps-phy-that-swra797-lists-as-certified/6538451</link><pubDate>Fri, 13 Nov 2026 10:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4c747a9d-219e-464c-92a9-d97f1a9f7b35</guid><dc:creator>Omid Ghaffari</dc:creator><description>This was very helpful - thank you so much, Richard!</description></item><item><title>Forum Post: RE: CC1312PSIP: CC1312PSIP: IBIS model, high-drive GPIO characteristics over temperature/VDDS, and pin state during reset/boot</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1690754/cc1312psip-cc1312psip-ibis-model-high-drive-gpio-characteristics-over-temperature-vdds-and-pin-state-during-reset-boot/6538216</link><pubDate>Fri, 13 Nov 2026 04:51:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7d1cfe07-b0d0-4098-921e-1302300c1dc9</guid><dc:creator>Zain Nasir</dc:creator><description>Your distinction between the IOC register’s reset value and subsequent ROM/SDK configuration is the key point. The reset value you quoted does not establish what DIO_5 does throughout bootloader execution or after every type of reset. For the transistor circuit, I’d define “off” as a maximum acceptable collector current at the highest operating temperature, rather than assuming that any base voltage below 0.6 V guarantees it. If the pin has only a weak pull-up, a first estimate—while base conduction and other leakage currents are negligible—is: VBE ≈ Ipull-up &amp;#215; RBE Here, RBE is your resistor from base to emitter. For background, this ULN2003 driver walkthrough discusses how base-emitter pull-down resistors help prevent floating bases and unwanted conduction. Your discrete NPN still needs its own calculation using the GPIO’s worst-case pull-up current and the transistor’s temperature characteristics. The 73 &amp;#181;A and 282 &amp;#181;A figures in TI’s CC1312PSIP datasheet, section 8.15.6.1 are typical values at 25&amp;#176;C under specified supply and pad-voltage conditions. They do not establish a guaranteed resistor value across your operating range. Treating the pull-up as a fixed 100 kΩ resistor would also need clarification from TI. A stronger base-emitter pull-down takes current away from the transistor base during normal operation. With your 1 kΩ series resistor: IB ≈ (VOH − VBE) / 1 kΩ − VBE / RBE Check that against the collector current and required saturation performance, using the GPIO’s loaded VOH at the lowest supply voltage. Crucially, a pull-down sized to overcome an internal pull-up does not guarantee the transistor stays off if ROM or bootloader code actively drives DIO_5 high. That makes TI’s confirmation of the complete pin-state sequence essential. A state-by-state answer for DIO_5, together with a guaranteed maximum pull-up current, would make this design decision much clearer. Measurements across reset and boot modes would help validate the implementation, but would not replace those worst-case specifications.</description></item><item><title>Forum Post: CC1101: TEP Proteus libraries for TI devices and modules - technical feedback welcome</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1697499/cc1101-tep-proteus-libraries-for-ti-devices-and-modules---technical-feedback-welcome</link><pubDate>Fri, 13 Nov 2026 04:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c9016471-78ed-4e05-9d3f-8c4b4180284a</guid><dc:creator>Zain Nasir</dc:creator><description>Part Number: CC1101 Other Parts Discussed in Thread: DRV2605L , ADS1115 , INA219 , DRV8833 Hello everyone, We’re the team behind The Engineering Projects (TEP) . We’ve developed several free Proteus libraries for TI devices and common breakout modules, and we’d welcome feedback from engineers who work with the actual hardware. The libraries include simulation models, interactive displays and example projects to help explore device configuration and circuit behaviour: CC1101 RF transceiver ....... SPI control, packet communication between simulated modules, and OOK experiments. ADS1115 ADC ...... analog inputs, programmable gain, differential measurements, conversion settings and ALERT/RDY behaviour. INA219 current/power monitor ...... a shunt resistor within the analog circuit, bus/shunt measurements, calibration and current/power registers. DRV8833 motor driver ...... dual H-bridge operation, forward/reverse control, brake/coast and PWM decay demonstrations. DRV2605L haptic driver ..... I&amp;#178;C configuration, effect sequencing, calibration and functional ERM/LRA actuator behaviour. INA128 instrumentation amplifier and LM358 dual op-amp ..... analog circuit demonstrations with selected gain, bandwidth and operating-range limitations. We also have a BeagleBone Black library for the TI AM3358-based board. It runs Python programs through supported GPIO, ADC, bus and virtual-network APIs. Debian, native processor execution and PRU firmware are outside its scope. The modelling boundaries are important: CC1101 radio propagation is simplified and excludes interference and collisions. ADS1115 and INA219 omit selected analog errors and physical effects. DRV8833 uses averaged PWM without switching ripple or dead time. DRV2605L effects are approximations; they do not reproduce TI’s proprietary ROM waveforms. Each article documents the corresponding limitations. The example projects have been tested in Proteus 8.5 . These are independently developed TEP models, without TI or Labcenter endorsement, intended for learning and functional prototyping. Hardware measurements remain necessary for electrical, timing and thermal validation. We’d particularly appreciate feedback on register behaviour, example clarity and the limitations that matter most in practical use. Which model would be useful in your workflow, and which missing feature should we prioritise? If you encounter a discrepancy, please include the library and Proteus versions, a small reproducing project, and the expected versus observed behaviour. A relevant datasheet section would help us investigate. Thank you for taking a look. The Engineering Projects team</description><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/INA219">INA219</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/DRV8833">DRV8833</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/LM358">LM358</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/INA128">INA128</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/ADS1115">ADS1115</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/DRV2605L">DRV2605L</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/cc1101">cc1101</category></item><item><title>Forum Post: RE: CC1120: CC1200 / CC1120 Operation at 240.4 MHz Outside the Specified Frequency Range</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1696956/cc1120-cc1200-cc1120-operation-at-240-4-mhz-outside-the-specified-frequency-range/6536607</link><pubDate>Wed, 11 Nov 2026 18:20:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:a2bd3b20-2133-4dda-b4e2-4624b9d54e85</guid><dc:creator>RGW</dc:creator><description>Hi, This is outside the frequency band for CC120x and CC112x. Can you use CC14xxP ? www.ti.com/.../CC1407P https://www.ti.com/lit/ds/symlink/cc1407p.pdf</description></item><item><title>Forum Post: RE: CC1312PSIP: CC1312PSIP: IBIS model, high-drive GPIO characteristics over temperature/VDDS, and pin state during reset/boot</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1690754/cc1312psip-cc1312psip-ibis-model-high-drive-gpio-characteristics-over-temperature-vdds-and-pin-state-during-reset-boot/6536204</link><pubDate>Wed, 11 Nov 2026 11:18:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:32a8e50b-9679-4fe1-beb8-b57715825734</guid><dc:creator>Yaşar BOLATeX</dc:creator><description>Hi Bun, A gentle reminder on my follow-up of October 20. The open points are: 4a) Is the ~100 kOhm pull-up on the DIOs enabled by hardware at reset, or set by software (ROM boot code, BSL, or SDK / SysConfig defaults)? The TRM (SWCU185G, IOCFGn reset value 0x00006000) shows PULL_CTL = 3 (no pull) and IE = 0. 4b) If it is set by software: in which phase, and for which DIOs? In particular DIO_5 during power-on / brown-out reset, ROM boot, BSL (including CCFG backdoor entry), pin reset / SYSRESET, and standby. 4c) Worst-case (maximum) pull-up current over -40 C to +105 C at VDDS = 3.6 V. The datasheet (SWRS293, page 34) gives 73 uA at 1.8 V and 282 uA at 3.8 V (25 C). 6) IOSTR = AUTO: at which VDDS levels does the drive strength change, and how often is it re-evaluated? DIO_5 drives the base of an NPN transistor, so the pull-up state before the application configures the pin matters for the safety of our design. Thank you, Yasar Bolat</description></item><item><title>Forum Post: CC1120: CC1200 / CC1120 Operation at 240.4 MHz Outside the Specified Frequency Range</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1696956/cc1120-cc1200-cc1120-operation-at-240-4-mhz-outside-the-specified-frequency-range</link><pubDate>Wed, 11 Nov 2026 08:39:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:27753460-36cf-4171-a199-ed87240a4b32</guid><dc:creator>Hori Shota</dc:creator><description>Part Number: CC1120 Other Parts Discussed in Thread: CC1200 Hi team, I reviewed the documentation for CC1200 and CC1120, and the supported frequency range is specified up to 240 MHz. Our target operating frequency is 240.4 MHz. Since 240.4 MHz is slightly above the specified upper limit of 240 MHz, is my understanding correct that operation at 240.4 MHz is outside the guaranteed operating range for both CC1200 and CC1120? Best Regards, Shota</description><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC1200">CC1200</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/cc1120">cc1120</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC1407P">CC1407P</category></item><item><title>Forum Post: RE: CC1354P10: multicasting alerts</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1693057/cc1354p10-multicasting-alerts/6536046</link><pubDate>Wed, 11 Nov 2026 08:30:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6ad64fcf-73e8-4c06-bfe1-81cb2e3d6caf</guid><dc:creator>Roshan Shenoy</dc:creator><description>Ahh okay, Thank you for your help and effort Daniel. I think it was a stretch, i think at least the ability for it to do it 30 minutes is still a good thing.</description></item><item><title>Forum Post: CC1311P3: CC1311P3: TX output power drops by ~1 dB at 40 °C and ~1.5 dB at 50 °C (set to +10 dBm)</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1696886/cc1311p3-cc1311p3-tx-output-power-drops-by-1-db-at-40-c-and-1-5-db-at-50-c-set-to-10-dbm</link><pubDate>Wed, 11 Nov 2026 04:54:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:e6463d3f-f9fb-4118-b55e-3d82e06a2bd5</guid><dc:creator>Theiv B</dc:creator><description>Part Number: CC1311P3 Hi TI team, We are seeing the PA output power of the CC1311P3 degrade as temperature rises, and we would like your guidance on whether this is expected and how to compensate for it. Observation: At room temperature (24 &amp;#176;C) the output power is close to the 10 dBm setting exclude cable loss. As the temperature goes above 40 &amp;#176;C, the output power drops noticeably. We also measured at -30 &amp;#176;C, where the power is higher than at room temperature. Measured output power (dBm) vs. temperature: TX Frequency (MHz) | -30 &amp;#176;C | 1 &amp;#176;C | 24 &amp;#176;C | 40 &amp;#176;C | 50 &amp;#176;C 406.125 | 10.36 | 9.58 | 9.20 | 9.11 | 8.36 435.5 | 9.66 | 8.55 | 8.92 | 8.34 | 7.81 469.975 | 9.56 | 8.60 | 8.63 | 8.36 | 8.19 Drop from 40 &amp;#176;C to 50 &amp;#176;C: -0.75 dB (406.125 MHz), -0.53 dB (435.5 MHz), -0.17 dB (469.975 MHz). Total variation from -30 &amp;#176;C to 50 &amp;#176;C is roughly 2 dB. Questions: Is this output power variation over temperature (about 2 dB from -30 &amp;#176;C to +50 &amp;#176;C) expected for the CC1311P3 at the +10 dBm setting? What is the typical and maximum variation in the datasheet? Does the RF driver or the HPOSC_OVERRIDE(0) temperature compensation also compensate the PA output power, or only the frequency synthesizer / HPOSC? Is there a recommended method to keep output power constant over temperature, for example adjusting txPower at run time based on the on-chip temperature sensor, or using RF_setTxPower()? Can you share the recommended txPower table entries for a +10 dBm output at high temperature, and whether the matching network or supply voltage affects this temperature behavior? Are there any recommended overrides for the PA ramp or DCDC settings that improve power stability at higher temperatures? (Our overrides include DCDC IPEAK = 7 and the PA ramp override.) We can share our full RF configuration if needed. Thanks, Theiv</description><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/CC1311P3">CC1311P3</category><category domain="https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/tags/Industrial%2bAutomation">Industrial Automation</category></item><item><title>Forum Post: RE: CC2340R5: CC2340R53 – Unexpected 2.2 mA Current Consumption in Shipment Mode After Long Runtime</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1687555/cc2340r5-cc2340r53-unexpected-2-2-ma-current-consumption-in-shipment-mode-after-long-runtime/6535436</link><pubDate>Tue, 10 Nov 2026 19:48:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b04a62b4-ca85-4ddc-8089-bca6aac71877</guid><dc:creator>desouza</dc:creator><description>Hiren, Please apologize for the delay; this thread went under my radar. [quote userid=&amp;quot;680243&amp;quot; url=&amp;quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1687555/cc2340r5-cc2340r53-unexpected-2-2-ma-current-consumption-in-shipment-mode-after-long-runtime/6523326&amp;quot;]We have identified and corrected a potentially problematic GPIO configuration in Shipment Mode and are validating the change across multiple devices. In parallel, we are investigating the external low-frequency crystal and the MCU&amp;#39;s standby behavior.[/quote] Were you able to reach further conclusions about your long term tests? [quote userid=&amp;quot;680243&amp;quot; url=&amp;quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1687555/cc2340r5-cc2340r53-unexpected-2-2-ma-current-consumption-in-shipment-mode-after-long-runtime/6523326&amp;quot;] External crystal validation: What measurements or register checks should we perform to determine whether the 32.768 kHz crystal, its load capacitors, or the oscillator circuit is unstable during long-term Shipment Mode operation? [/quote] You could check CKMD:LFCLKSTAT to see if there are any differences between units with different power consumption numbers. In addition, you could use an oscilloscope active probe (very low capacitance) to see if the 32kHz crystal waveform is distorted. [quote userid=&amp;quot;680243&amp;quot; url=&amp;quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1687555/cc2340r5-cc2340r53-unexpected-2-2-ma-current-consumption-in-shipment-mode-after-long-runtime/6523326&amp;quot;] Clock-loss investigation: How should we interpret LFCLKLOSS = 1 when LFXT remains selected and LFCLKGOOD = 1 ? What is the recommended procedure to identify the underlying cause? [/quote] The CKMD:RIS.LFCLKGOOD is based on the limits defined by the register CKMD:LFQUALCTL and is periodically evaluated. As for the CKMD:RIS.LFCLKLOSS, it will indicate that a clock loss happened in the past and it is not cleared unless the bit CKMD:ICLR.LFCLKLOSS is set. [quote userid=&amp;quot;680243&amp;quot; url=&amp;quot;~/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1687555/cc2340r5-cc2340r53-unexpected-2-2-ma-current-consumption-in-shipment-mode-after-long-runtime/6523326&amp;quot;] Standby entry and wake-up investigation: What additional registers, APIs, or debugging methods should we use to identify why the MCU remains at approximately 2.2 mA while BLE advertising and connections continue to work? [/quote] You could potentially try to enable your system to generate an interrupt at CKMD:ISET.LFCLKLOSS and trap the system status when this issue happens. You could also set your interrupt to set a DIO pin to trigger an external oscilloscope to see if such loss can track with an externality such as a voltage sag or any spike. These are the ideas that occur to me to help you progress further. Hope this helps, Rafael</description></item><item><title>Forum Post: RE: CC1354P10: multicasting alerts</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1693057/cc1354p10-multicasting-alerts/6535035</link><pubDate>Tue, 10 Nov 2026 13:59:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:43a9c795-833f-4484-9066-f8b80b0cbef5</guid><dc:creator>Daniel Guarecuco Aguiar</dc:creator><description>Hi Roshan, I think unfortunately that it just the &amp;quot;intended&amp;quot; behavior, as only the BR manages the network, all other RN will eventually start disconnecting and looking for a new parent once the BR dies. So at some point the devices are not really part of a network and the multicasts are not sent. Best regards, Daniel</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533948</link><pubDate>Mon, 09 Nov 2026 15:57:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:12845cb5-de2e-4754-9677-68d5a189f66d</guid><dc:creator>RGW</dc:creator><description>Just sent a webex invite for tomorrow afternoon at 15:00 CET. Speak to you more tomorrow but take a look at the ACP data with 4-GFSK 9.6 kbps in a 12.5 kHz channel that has -75 dBc which should meet your requirements.</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533907</link><pubDate>Mon, 09 Nov 2026 15:28:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:0addbb4f-e804-42cd-a2b2-4328e0b1f774</guid><dc:creator>RGW</dc:creator><description>The TX equivalent (Adjacent Channel Power) is in section 4.11 I&amp;#39;ll send you a webex link via your email so we can discuss this on a call.</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533831</link><pubDate>Mon, 09 Nov 2026 14:13:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d8cbb0f9-b9f8-46c9-a2eb-38fb8f725a1e</guid><dc:creator>jeroen wilbers</dc:creator><description>This is all about the Rx side. That is fine. The Tx side is not within spec. The Adjacent Channel Power is well above the ETSI 300-113 spec. It should be &amp;lt;-60dBc and it only reaches -40(ish) dBc Do you have any Tx measurements? Is it otherwise possible to have a teams call (or similar) as this feels like a really slow chat :) Regards Jeroen</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533827</link><pubDate>Mon, 09 Nov 2026 14:07:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2aa7214c-0159-454c-be50-5d45061bc9e3</guid><dc:creator>RGW</dc:creator><description>Hi, This is documented in the CC1125 datasheet and additional information is available in the app note: https://www.ti.com/lit/an/swra424/swra424.pdf Page 13 in the datasheet: https://www.ti.com/lit/ds/symlink/cc1125.pdf Regards, Richard</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533799</link><pubDate>Mon, 09 Nov 2026 13:14:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2ddcc218-900c-419f-991d-102c7cc8d826</guid><dc:creator>jeroen wilbers</dc:creator><description>Hi Richard Do you have any documentation/measurements on the ACP of these modes? So we can test and reproduce Thank you!</description></item><item><title>Forum Post: RE: CC1352P7: CC1352P7: ACP about 30 dB short of the EN 300 113 / EN 300 224 limit in a 12.5 kHz channel</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1692698/cc1352p7-cc1352p7-acp-about-30-db-short-of-the-en-300-113-en-300-224-limit-in-a-12-5-khz-channel/6533797</link><pubDate>Mon, 09 Nov 2026 13:06:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2f2e6a2c-83a2-4434-a852-faff40a2eaa0</guid><dc:creator>RGW</dc:creator><description>Hi, All PHYs will comply with ETSI specification (ETSI EN 300 220) but only PHYs that are narrowband will pass ETSI EN 300 113. For the best blocking performance follow the CAT 1 PHYs. Test with &amp;quot;1.2 kbps, 2-GFSK, ETSI CAT1, Sync word: D9CC&amp;quot; PHY since this is ideal for 12.5 kHz channel spacing. There is also a 1.2 kbps, 2-GFSK, ETSI CAT 1 for 25 kHz channel spacing as well.</description></item><item><title>Forum Post: RE: LP-CC1312R7: RF Differential Pair Impedance for CC1312R7 / CC1311P3 / CC1352P7 Custom PCB Design</title><link>https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1694566/lp-cc1312r7-rf-differential-pair-impedance-for-cc1312r7-cc1311p3-cc1352p7-custom-pcb-design/6533773</link><pubDate>Mon, 09 Nov 2026 12:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ef1d5263-6406-4f98-8cb1-7cabc1d6d2e3</guid><dc:creator>RGW</dc:creator><description>Hi, Your PCB stackup is quite similar to our ref design stackup but not exactly the same with the main difference being the 175 um vs 300 um for the prepreg. We traditionally use 150 um line width and 150 um separation for our standard ref designs with a prepreg thickness of 175 um. The component values will be the dominant factor and not so much the trace thickness since there lengths are very short. If changing the trace thicknesses to compensate for a thicker prepreg, then I would maintain the 150 um separation design rule and for the RF traces increase from 150 um to 250 um where possible. I would not go wider than 250 um. For the 50 ohm characteristics impedance, 524 um sounds right for a microstrip with a prepreg of 300 um. However, keep into account the ground fill besides the trace that will effectively make the microstrip to a Coplanar (CPW Ground) waveguide. For a CPW 524 um is OK with a 500 um gap on the top layer to the GND fill. If the gap on the top layer is 150 um; then the 50 ohm trace should be reduced to around 400 um instead.</description></item></channel></rss>