<?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>Power management</title><link>https://e2e.ti.com/support/power-management-group/power-management/</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: BQ27520-G4: Design Clarification</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1645298/bq27520-g4-design-clarification/6347718</link><pubDate>Sat, 16 May 2026 08:29:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9eb275d1-11d4-42bf-8d3f-b7b99404d5cc</guid><dc:creator>Divya Visali</dc:creator><description>Hi Dominik, Thanks for your reply. So for which one I have to connect the thermistor,whether fuel gauge or charger ic? which will be better</description></item><item><title>Forum Post: BQ34Z100-R2: The maximum error remains at 100% after multiple charge and discharge cycles during the learning cycle NIMH 2P9S BP</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646473/bq34z100-r2-the-maximum-error-remains-at-100-after-multiple-charge-and-discharge-cycles-during-the-learning-cycle-nimh-2p9s-bp</link><pubDate>Sat, 16 May 2026 08:17:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b6863a9e-bfab-45ca-8d5a-a699abed82d5</guid><dc:creator>Daniele Pascali</dc:creator><description>Part Number: BQ34Z100-R2 I have a 4000mAh NIMH battery pack with 2000mAh cells in a 2P9S configuration. I followed all the documentation I could find to set the gauge parameters and run the learning cycle. The learning cycle is performed with a discharge current of 1A and a fast charge current of about 1.5A. Before starting the learning cycle, I set the IT_ENABLE register and see that the VOK and QEN flags correctly set to 1 during charging and discharging. The current and voltage measurements are correct, and the gauge seems to track the discharge and charge well. I don&amp;#39;t understand why the maximum error remains at 100% after 4 or 5 charge and discharge cycles. I&amp;#39;m attaching the contents of the memory. What am I doing wrong? Thanks. Data Memory pacchi batteria campione CHY AGGIORNATO E CORRETTO v2 con FW 2.02.gg.csv</description><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/Medical%2b_2600_amp_3B00_%2bhealthcare">Medical &amp;amp; healthcare</category><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/BQ34Z100_2D00_R2">BQ34Z100-R2</category></item><item><title>Forum Post: TPS61041: TPS61041DBVR boost converter output stuck at ~4 V instead of 16 V – schematic/layout review request</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646472/tps61041-tps61041dbvr-boost-converter-output-stuck-at-4-v-instead-of-16-v-schematic-layout-review-request</link><pubDate>Sat, 16 May 2026 08:02:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b0ed6219-70ca-4666-bf4f-47b8a96b1814</guid><dc:creator>Chetan Bidap1</dc:creator><description>Part Number: TPS61041 Hello TI Team, We are using the TPS61041DBVR boost converter to generate 16 V from a lower input supply, but currently we are only getting about 4 V at the output. Could you please review our schematic and layout and advise why this may be happening?</description><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/Industrial%2bAutomation">Industrial Automation</category><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/TPS61041">TPS61041</category></item><item><title>Forum Post: BQ27Z746: BQSTUDIO: How to generate *.bq.fs and *.df.fs for BQ27Z746</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646471/bq27z746-bqstudio-how-to-generate-bq-fs-and-df-fs-for-bq27z746</link><pubDate>Sat, 16 May 2026 07:57:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f47835ca-ab92-46ae-8780-3edbaf8bb699</guid><dc:creator>Kok Yee Sheng</dc:creator><description>Part Number: BQ27Z746 Other Parts Discussed in Thread: EV2400 , BQSTUDIO Hi, How to generate *.df.fs files for factory programming. We have golden config in the form of *bq.fs Is there any flashing method other than via BQSTUDIO and EV2400 programmer, that we can use in the factory? Regards.</description><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/BQ27Z746">BQ27Z746</category><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/EV2400">EV2400</category><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/bqStudio">bqStudio</category><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/Wearables%2b_2800_non_2D00_medical_2900_">Wearables (non-medical)</category></item><item><title>Forum Post: BQ27220: bq27220 still using default EDV thresholds after successful Data Memory update for EDV</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646464/bq27220-bq27220-still-using-default-edv-thresholds-after-successful-data-memory-update-for-edv</link><pubDate>Sat, 16 May 2026 06:37:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2b5cf472-e626-4496-882b-251531bb6522</guid><dc:creator>Manohar Thokala</dc:creator><description>Part Number: BQ27220 Hi TI Team, I am working with the bq27220 fuel gauge and configuring the EDV thresholds through MCU firmware during initialization. I updated the EDV thresholds to: EDV2 = 3200 mV EDV1 = 3000 mV EDV0 = 2900 mV The default values were: EDV2 = 3501 mV EDV1 = 3385 mV EDV0 = 3031 mV I am entering Full Access mode successfully, entering CFGUPDATE mode, writing the Data Memory block, recalculating checksum, and verifying the updated values by reading back the block after the write. From my logs, the updated EDV values are correctly stored in Data Memory. However, during runtime, the gauge still appears to behave according to the default EDV thresholds. FCC updates and SOC percentage estimation are still occurring around the original default voltages instead of my programmed thresholds. For example: Battery voltage is around 3650 mV SOC is already ~5% FCC estimation behavior also seems aligned with default EDV settings I want to understand: Are there additional parameters or flags that must be updated for new EDV thresholds to become active? Is a RESET or SOFT_RESET required after EDV Data Memory updates? Does the gauge cache EDV parameters internally until a learning cycle completes? Are EDV thresholds ignored when certain gauging modes or chem IDs are used? Is there any OTP/default configuration that overrides RAM/Data Memory EDV settings? Below are relevant initialization logs: === Waiting for INITCOMP === Attempt 1: OpStatus=0x00A6 INITCOMP=1 OK: INITCOMP set *** UNSEAL KEY FOUND: 0x0414 / 0x3672 *** === Get Full Access === OpStatus=0x00A2 SEC=CHECKING FULL ACCESS OK: Full Access granted === Enter CFG Update Mode === Before: OpStatus=0x00A2 CFGUPDATE=0 SEC=FULL ACCESS Attempt 1: OpStatus=0x04A2 CFGUPDATE=1 OK: CFGUPDATE active EDV block after update verification: DM bytes EDV [0x92B4] : 0x0B DM bytes EDV [0x92B5] : 0x54 DM bytes EDV [0x92B6] : 0x01 DM bytes EDV [0x92B7] : 0x0B DM bytes EDV [0x92B8] : 0xB8 DM bytes EDV [0x92B9] : 0x01 DM bytes EDV [0x92BA] : 0x0C DM bytes EDV [0x92BB] : 0x80 DM bytes EDV [0x92BC] : 0x01 CFGUPDATE exit and reseal: === Exit CFG Update Mode === Attempt 1: OpStatus=0x00A6 CFGUPDATE=0 INITCOMP=1 OK: Exited CFGUPDATE === Re-seal Gauge === OpStatus=0x00A6 SEC=SEALED OK: Gauge re-sealed Final runtime values: Design Capacity : 1000 mAh Full charge capacity : 872 mAh SOC : 5 % Voltage : 3650 mV Could you please help identify why the gauge still behaves as if default EDV thresholds are active even though Data Memory updates are verified successfully? Thanks.</description><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/BQ27220">BQ27220</category></item><item><title>Forum Post: RE: LM74502: COUT Cap value</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646379/lm74502-cout-cap-value/6347704</link><pubDate>Sat, 16 May 2026 06:07:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1f8c6aa8-e2c0-4b43-98e5-d2899377cf2c</guid><dc:creator>Shiven Dhir</dc:creator><description>Hi Praven, Why is the extra diode added? You can skip the 100uF capacitor there and add a small capacitor like 100nF and proceed. Regards, Shiven Dhir</description></item><item><title>Forum Post: RE: LM5050-1: ORing two different power supply levels</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1645911/lm5050-1-oring-two-different-power-supply-levels/6347703</link><pubDate>Sat, 16 May 2026 05:56:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:fc066ecd-c8ab-42d6-9508-e07f72f47df0</guid><dc:creator>Shiven Dhir</dc:creator><description>Hi Pradeep, You dont have to take any special care. Yes, when 12V supply turns-on, 7.4V supply&amp;#39;s MOSFET will turn-off automatically. Controller has that function. It will be a smooth transfer. Regards, Shiven Dhir</description></item><item><title>Forum Post: RE: BQ25173-Q1: Drop out voltage</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646328/bq25173-q1-drop-out-voltage/6347702</link><pubDate>Sat, 16 May 2026 05:44:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:d090a786-ee28-46bc-ac6c-ca7cad9f9c11</guid><dc:creator>Piotr Romaniuk</dc:creator><description>Hi Bill, [quote userid=&amp;quot;8507&amp;quot; url=&amp;quot;~/support/power-management-group/power-management/f/power-management-forum/1646328/bq25173-q1-drop-out-voltage/6347644&amp;quot;] Piotr Romaniuk said: The symbols for input and outpus transistors mean that they are n-mos and need to be polarised to open (Vgs must be positive). How it works if supercap is almost fully charged if the maximum voltage is Vin? How can be controlled input transistor if Vin = Vscap + Vdropout? Sorry we do not share design detail of the device. [/quote] The question arose out of curiosity and the suspicion that there was an error in the datasheet. I don&amp;#39;t want to access entire chip schematics, just to make sure the diagram is correct. This diagram helps to understand how the chip works and explains the behavior during each phase of the supercapacitor charge. It resembles an analog bidirectional switch configuration. In my opinion, P-MOS transistors should be present, as they are working on high side. Below you may see two diagrams (on the left) from the datasheet and (on the right) an analog switch found on stackexchange.com (by the way, the author of that post quotes Texas Instruments). Kind regards, Piotr Romaniuk PS In the datasheet n-mos transistors are in two diagrams: simplified and detailed.</description></item><item><title>Forum Post: RE: BQ25173-Q1: Drop out voltage</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646328/bq25173-q1-drop-out-voltage/6347698</link><pubDate>Sat, 16 May 2026 04:57:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7be00c0f-d985-4ab0-b2f4-14f73d26c77e</guid><dc:creator>Piotr Romaniuk</dc:creator><description>Hi Bill, thank you for the explanation. I would like to clarify a typo: [quote userid=&amp;quot;8507&amp;quot; url=&amp;quot;~/support/power-management-group/power-management/f/power-management-forum/1646328/bq25173-q1-drop-out-voltage/6347644&amp;quot;] You will see the current drop from 800mA to about 250mA when input / output is 200mA.[/quote] Did you meen: &amp;quot;[...] when input / output is 200m V &amp;quot; ? Kind regards, Piotr Romaniuk</description></item><item><title>Forum Post: RE: BQ25690: how to configure bq25690 for supercap</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1645913/bq25690-how-to-configure-bq25690-for-supercap/6347696</link><pubDate>Sat, 16 May 2026 04:52:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:12fa4eec-fe3f-4b8e-b3e9-b0754e72c35f</guid><dc:creator>Piotr Romaniuk</dc:creator><description>Hi Ryan, Thank you for this suggestion. I will check details of this chip. Kind regards, Piotr Romaniuk</description></item><item><title>Forum Post: RE: TPSM64404: Regarding the Voltage Rating of the Capacitor Connected to the SS Pin When Using TPSM64404/TLVM14404 in Single-Output Configuration</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1645364/tpsm64404-regarding-the-voltage-rating-of-the-capacitor-connected-to-the-ss-pin-when-using-tpsm64404-tlvm14404-in-single-output-configuration/6347693</link><pubDate>Sat, 16 May 2026 04:10:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:fb702dc6-2aa0-4e6d-8071-97a3ad326fa1</guid><dc:creator>Sourish Nandy</dc:creator><description>Hello Kyohei-san, The supply voltage for the current source charging the SS is a filtered version of Vcc. But as Vcc is also derived from the Vin, under extremely rare failure, Vin can appear at SS too as explained in my previous reply. Thanks and Regards, Sourish Nandy</description></item><item><title>Forum Post: RE: LM5143-Q1: LM5143QRHARQ1 VCC current consumption</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1640627/lm5143-q1-lm5143qrharq1-vcc-current-consumption/6347687</link><pubDate>Sat, 16 May 2026 02:45:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:94ed97fb-7973-4bb4-8672-6820692612eb</guid><dc:creator>Zhang Yepeng</dc:creator><description>Hi Timpthy Sorry, I don’t quite get what you mean. So if I set it to DEMB, I won’t be able to turn off EN2, right? Could you take a look at my SCH and walk me through more details—like how to design the buffer? Or maybe you have a diagram?</description></item><item><title>Forum Post: RE: TPS2373: Issues with TPS2373 in 60W PoE Application (Overheating, Handshake Failure, and Leakage Current)</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1644662/tps2373-issues-with-tps2373-in-60w-poe-application-overheating-handshake-failure-and-leakage-current/6347686</link><pubDate>Sat, 16 May 2026 02:40:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3d9e987f-305f-48c5-b388-3be1f486d84e</guid><dc:creator>huy pham</dc:creator><description>Could you recommend a way for me to fix these issues? In our production environment, the current error rate is 5/1000.</description></item><item><title>Forum Post: RE: TPS3700: TPS3700 Negative Voltage Mode - SPICE model not working</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646087/tps3700-tps3700-negative-voltage-mode---spice-model-not-working/6347679</link><pubDate>Sat, 16 May 2026 01:42:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:01f743d6-e33d-43fe-a9fb-a8b583e606b2</guid><dc:creator>John Dusatko</dc:creator><description>Henry, Many thanks for your reply. Understood about the SPICE model, hopefully it can be updated to handle negative voltage mode. Regarding the maximum input voltages: to clarify then this specification should be interpreted relative to the IC ground pin and not the system ground. So if one were to take a voltmeter and place one probe on the GND pin and the other on the INA/INB pins, it would measure 437mV/365mV. OK, got it. It makes sense now. Thanks again! John</description></item><item><title>Forum Post: RE: BQ34Z100-G1: Calibration failed</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646311/bq34z100-g1-calibration-failed/6347677</link><pubDate>Sat, 16 May 2026 01:24:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:61a6b8bb-5cec-45e3-8ee7-cf2df3c56f0e</guid><dc:creator>Alex</dc:creator><description>Hi The attachment contains a GG file and SCH, pack configuration = 4161。 calibration still cannot be completed。</description></item><item><title>Forum Post: TPS61088: Current Limiting Resistor</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646458/tps61088-current-limiting-resistor</link><pubDate>Sat, 16 May 2026 00:58:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:aeec89d1-4577-410e-aef8-f7a579737483</guid><dc:creator>Vitalii Kulik</dc:creator><description>Part Number: TPS61088 Hello, I want to reduce the current through the inductance, and I would like to know the limits within which the reliable operation of the Boost Converter is guaranteed. In the datasheet for TPS61088 I do not see the MIN - MAX range for RILIM = 100 kOhm. Link: https://www.ti.com/lit/ds/symlink/tps61088.pdf Let&amp;#39;s assume that RILIM = 100 kOhm is the minimum value. Then what is the maximum value for RILIM.</description><category domain="https://e2e.ti.com/support/power-management-group/power-management/tags/TPS61088">TPS61088</category></item><item><title>Forum Post: RE: LMQ66430-Q1: LMQ66430MC3RXBRQ1 failure at power-on</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1646071/lmq66430-q1-lmq66430mc3rxbrq1-failure-at-power-on/6347672</link><pubDate>Sat, 16 May 2026 00:35:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:9dbfd845-e1d3-4d05-a43a-ea0a10c4e919</guid><dc:creator>Narek Pezeshkian</dc:creator><description>Hi Nick, When providing power at the VOUT node, I see about 50 mA of load current, which is about right. Remember at this point in time I am supplying 8V to VOUT. If I were to raise the voltage to 8.6V the LMQ66430 turns on and draws significantly more from the power supply. Here&amp;#39;s the waveform on VIN when I supply the board with 12V. The power supply indicates 430mA of current! The oscillation occurs at about 228Hz. Thanks, Narek</description></item><item><title>Forum Post: RE: BQ25190: BQ25190 Strange Charging Behavior</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1642619/bq25190-bq25190-strange-charging-behavior/6347665</link><pubDate>Sat, 16 May 2026 00:08:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b26e0908-8ed2-407c-b13e-97600aa05d20</guid><dc:creator>Alec Lehman</dc:creator><description>Hi Tyler, Thanks for the update. I sent you an E2E friend request. I can private message you about the schematic if you accept it. I agree that the initialization likely isn&amp;#39;t the issue here. As you&amp;#39;ve mentioned, the registers are set to non-default values in the register dump. Yes, with a valid VBUS, the BQ25190 will be able to communicate. I don&amp;#39;t see any obvious cases where the device wouldn&amp;#39;t be able to communicate with the host MCU when charging is done. That&amp;#39;s helpful to know you aren&amp;#39;t seeing current into the battery being reported by the IBAT_ADC. However, the IBAT_ADC only measures current through the BATFET, so if there&amp;#39;s another path for current, it wouldn&amp;#39;t detect it. Is the battery connected to anything other than the BAT pin of the BQ25190 in your schematic? There can sometimes be unintended current paths, such as reverse current through an external LDO. Best regards, Alec</description></item><item><title>Forum Post: RE: TPS25751: TSP25751+BQ25798 VAC1+VAC2 state machine</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1639290/tps25751-tsp25751-bq25798-vac1-vac2-state-machine/6347652</link><pubDate>Fri, 15 May 2026 23:36:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:92d517f7-e4b3-4714-b4ca-015d6a639c9d</guid><dc:creator>Radek Jahoda</dc:creator><description>Hi Timothy, yes, I am using my own board. I have finally analyzed it with logic analyzer and here is the sum of the results in groups as I see in the timeline: 1. Read of the EEPROM at address 0x50 - large portion of data 2. Read of 0x3B register - VBAT voltage 3.618782458333333,0,0x6B,0x3B,Write,ACK 3.618835333333333,0,0x6B,0x0E,Read,ACK 3.618863208333333,0,0x6B,0x81,Read,NAK 3. Write to some control registers 3.618863208333333,0,0x6B,0x81,Read,NAK 3.636431666666667,0,0x6B,0x10,Write,ACK 3.636455833333333,0,0x6B,0x00,Write,ACK 3.637367541666667,0,0x6B,0x10,Write,ACK 3.637391708333333,0,0x6B,0x00,Write,ACK 3.637770500000000,0,0x6B,0x14,Write,ACK 3.637794666666667,0,0x6B,0x9C,Write,ACK 3.638198875000000,0,0x6B,0x11,Write,ACK 3.638223000000000,0,0x6B,0x00,Write,ACK 3.638601416666666,0,0x6B,0x12,Write,ACK 3.638625541666667,0,0x6B,0x00,Write,ACK 3.639003958333333,0,0x6B,0x08,Write,ACK 3.639028083333333,0,0x6B,0xC1,Write,ACK 3.639445166666667,0,0x6B,0x09,Write,ACK 3.639469333333333,0,0x6B,0x01,Write,ACK 3.639871416666667,0,0x6B,0x01,Write,ACK 3.639895541666667,0,0x6B,0x01,Write,ACK 3.639919708333333,0,0x6B,0xA4,Write,ACK 3.640302250000000,0,0x6B,0x03,Write,ACK 3.640326416666666,0,0x6B,0x01,Write,ACK 3.640350541666667,0,0x6B,0xF4,Write,ACK 3.640755166666667,0,0x6B,0x0F,Write,ACK 3.640779291666667,0,0x6B,0x82,Write,ACK 3.641200583333333,0,0x6B,0x0B,Write,ACK 3.641224708333333,0,0x6B,0x00,Write,ACK 3.641248833333333,0,0x6B,0xEA,Write,ACK 3.641626833333333,0,0x6B,0x0D,Write,ACK 3.641650958333333,0,0x6B,0x17,Write,ACK 3.642411625000000,0,0x6B,0x12,Write,ACK 3.642435750000000,0,0x6B,0x00,Write,ACK 3.643679166666667,0,0x6B,0x0F,Write,ACK 3.643703291666667,0,0x6B,0x82,Write,ACK 3.644123666666667,0,0x6B,0x0B,Write,ACK 3.644147791666667,0,0x6B,0x00,Write,ACK 3.644171875000000,0,0x6B,0xEA,Write,ACK 3.644580166666667,0,0x6B,0x0D,Write,ACK 3.644604291666667,0,0x6B,0x17,Write,ACK 3.645004666666666,0,0x6B,0x05,Write,ACK 3.645028750000000,0,0x6B,0x24,Write,ACK 3.645412541666667,0,0x6B,0x06,Write,ACK 3.645436625000000,0,0x6B,0x00,Write,ACK 3.645460750000000,0,0x6B,0x0A,Write,ACK 4. Write to 0x0f register Charger Control 0 with EN_AUTO_IBATDIS and EN_TERM 3.684486541666667,0,0x6B,0x0F,Write,ACK 3.684510708333333,0,0x6B,0x82,Write,ACK 3.685243375000000,0,0x6B,0x0F,Write,ACK 3.685267541666667,0,0x6B,0x82,Write,ACK 5. Write to 0x0b VOTG regulation register with 0x00dc value, 0x12 Charger Control 3 with EN_OTG, 0x0d IOTG register with 0x51 value and again 0x0b VOTG with 0x00dc 3.871836791666666,0,0x6B,0x0B,Write,ACK 3.871860916666667,0,0x6B,0x00,Write,ACK 3.871885041666667,0,0x6B,0xDC,Write,ACK 3.873290916666666,0,0x6B,0x12,Write,ACK 3.873315083333333,0,0x6B,0x40,Write,ACK 3.874302291666667,0,0x6B,0x12,Write,ACK 3.874326416666667,0,0x6B,0x40,Write,ACK 3.875278125000000,0,0x6B,0x0D,Write,ACK 3.875302250000000,0,0x6B,0x51,Write,ACK 3.876279791666667,0,0x6B,0x0B,Write,ACK 3.876303916666667,0,0x6B,0x00,Write,ACK 3.876328083333333,0,0x6B,0xDC,Write,ACK 6. After 100ms it seems to be disabled by write 0x12 Charger Control 3 with 0x00 (that means EN_OTG disabled) and VOTG and IOTG registers and after that 0x14 Charger Control 5 with 0x9C value (SFET_PRESENT+EN_IBAT+IBAT_REG_1:0=3 as disabled) and Charger Control 2 rgister with 0x00 3.985915916666666,0,0x6B,0x12,Write,ACK 3.985940000000000,0,0x6B,0x00,Write,ACK 3.986460541666667,0,0x6B,0x12,Write,ACK 3.986484625000000,0,0x6B,0x00,Write,ACK 3.986901500000000,0,0x6B,0x0F,Write,ACK 3.986925541666666,0,0x6B,0x82,Write,ACK 3.987308500000000,0,0x6B,0x0B,Write,ACK 3.987332583333334,0,0x6B,0x00,Write,ACK 3.987356625000000,0,0x6B,0xEA,Write,ACK 3.987735583333333,0,0x6B,0x0D,Write,ACK 3.987759625000000,0,0x6B,0x17,Write,ACK 3.988167708333333,0,0x6B,0x14,Write,ACK 3.988191791666666,0,0x6B,0x9C,Write,ACK 3.988570916666667,0,0x6B,0x11,Write,ACK 3.988595041666667,0,0x6B,0x00,Write,ACK 7. Than 666ms pause and repeating 5+6 all over again 4.654472958333334,0,0x6B,0x0F,Write,ACK 4.654497083333333,0,0x6B,0x82,Write,ACK 4.655212250000000,0,0x6B,0x0F,Write,ACK 4.655236375000000,0,0x6B,0x82,Write,ACK 4.841954916666666,0,0x6B,0x12,Write,ACK 4.841979083333333,0,0x6B,0x40,Write,ACK 4.842888375000000,0,0x6B,0x12,Write,ACK 4.842912500000000,0,0x6B,0x40,Write,ACK 4.843888833333334,0,0x6B,0x0D,Write,ACK 4.843912958333333,0,0x6B,0x51,Write,ACK 4.844868791666666,0,0x6B,0x0B,Write,ACK 4.844892958333333,0,0x6B,0x00,Write,ACK 4.844917083333334,0,0x6B,0xDC,Write,ACK 4.845888375000000,0,0x6B,0x0B,Write,ACK 4.845912500000000,0,0x6B,0x00,Write,ACK 4.845936625000000,0,0x6B,0xDC,Write,ACK 4.955873708333334,0,0x6B,0x12,Write,ACK 4.955897750000000,0,0x6B,0x00,Write,ACK 4.956388083333334,0,0x6B,0x12,Write,ACK 4.956412125000000,0,0x6B,0x00,Write,ACK 4.956790041666666,0,0x6B,0x0F,Write,ACK 4.956814083333334,0,0x6B,0x82,Write,ACK 4.957222750000000,0,0x6B,0x0B,Write,ACK 4.957246791666667,0,0x6B,0x00,Write,ACK 4.957270875000000,0,0x6B,0xEA,Write,ACK 4.957648083333333,0,0x6B,0x0D,Write,ACK 4.957672166666667,0,0x6B,0x17,Write,ACK 4.958049916666667,0,0x6B,0x14,Write,ACK 4.958074000000000,0,0x6B,0x9C,Write,ACK 4.958486750000000,0,0x6B,0x11,Write,ACK 4.958510791666667,0,0x6B,0x00,Write,ACK 8. And after 666ms again with some minor changes 5.624589541666666,0,0x6B,0x0F,Write,ACK 5.624613666666667,0,0x6B,0x82,Write,ACK 5.625327166666667,0,0x6B,0x0F,Write,ACK 5.625351291666667,0,0x6B,0x82,Write,ACK 5.812071250000000,0,0x6B,0x12,Write,ACK 5.812095375000000,0,0x6B,0x40,Write,ACK 5.813004208333333,0,0x6B,0x12,Write,ACK 5.813028375000000,0,0x6B,0x40,Write,ACK 5.814015916666667,0,0x6B,0x0B,Write,ACK 5.814040041666667,0,0x6B,0x00,Write,ACK 5.814064166666666,0,0x6B,0xDC,Write,ACK 5.814997166666667,0,0x6B,0x0B,Write,ACK 5.815021291666667,0,0x6B,0x00,Write,ACK 5.815045416666667,0,0x6B,0xDC,Write,ACK 5.816015875000000,0,0x6B,0x0D,Write,ACK 5.816040000000000,0,0x6B,0x51,Write,ACK 5.917249958333334,0,0x6B,0x0F,Write,ACK 5.917274125000000,0,0x6B,0x82,Write,ACK 5.925928750000000,0,0x6B,0x12,Write,ACK 5.925952791666667,0,0x6B,0x00,Write,ACK 5.926470458333333,0,0x6B,0x12,Write,ACK 5.926494500000000,0,0x6B,0x00,Write,ACK 5.926892291666666,0,0x6B,0x0F,Write,ACK 5.926916375000000,0,0x6B,0x82,Write,ACK 5.927325041666666,0,0x6B,0x0B,Write,ACK 5.927349083333334,0,0x6B,0x00,Write,ACK 5.927373166666666,0,0x6B,0xEA,Write,ACK 5.927750416666667,0,0x6B,0x0D,Write,ACK 5.927774458333333,0,0x6B,0x17,Write,ACK 5.928159250000000,0,0x6B,0x14,Write,ACK 5.928183333333333,0,0x6B,0x9C,Write,ACK 5.928570333333333,0,0x6B,0x11,Write,ACK 5.928594416666667,0,0x6B,0x00,Write,ACK And goes forever after 666ms gap OTG is enabled and after 186ms disabled. Actually there are no reads from BQ25798 so I don&amp;#39;t think that the problem is related to it but probably somehow related to USB-C PD? I can send the whole communication via email or private message and also schematic if needed. Thank you very much for feedback. Best regards Radek</description></item><item><title>Forum Post: RE: BQ76930: I2C Communication Problem</title><link>https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1643112/bq76930-i2c-communication-problem/6347649</link><pubDate>Fri, 15 May 2026 23:26:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6ddb386f-7fa7-4f6e-86ef-d5668a04f693</guid><dc:creator>Alexis_H</dc:creator><description>Hi Kamel, Please give me some time to review what you have shared and capture some waveforms on my end. Best Regards, Alexis</description></item></channel></rss>