https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/1686227/lmx2694-ep-some-lmx2694-devices-lose-lock-when-mash_seed-is-set-to-a-non-zero-value/6502192Mon, 05 Oct 2026 22:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:57fdf029-bb65-4bd5-8edf-af56d0f14b76Noel FungHi There, I tried 5 boards, I don't have the unlock issue. Since you said the issue could be fixed by changing the mash to 1st order, looks like this is related to the situation as described in the datasheet. I also tried 1st order mash with the same mash_seed value of 0xC8. I need to program R41 4 times to get the phase shifted. The phase shifted is equal to 4 times the phase shift as produced by 2nd order mash. Since the phase adjustment was not fully characterized, I don't have a known good solution to fix this behavior. One thing you can try, set FCAL_HPFD_ADJ to 0x2 to reduce the phase detector frequency during calibration. We have seen this trick works when IncludedDivide = 6.https://e2e.ti.com/support/amplifiers-group/amplifiers/f/amplifiers-forum/1686855/vca810-output-swing-voltage-range/6502193Mon, 05 Oct 2026 22:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:177fb450-2c21-4ec6-845a-4e0968b1f0f7Evan KirkbrideIt will not just increase until it hits the rail, no. It'll likely stop at around the 4Vpp at 500ohms like you are seeing. Thanks, Evanhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1687193/bq25756evm-charge-current-not-working-as-expected-when-starting-up-at-different-input-voltagesMon, 05 Oct 2026 22:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e5cc77b1-8342-4c9e-88eb-fac9f20a5303Mike HubertPart Number: BQ25756EVM Other Parts Discussed in Thread: BQ25756 , I'm evaluating the BQ25756 for an 8S LiFePO4 charger with a 17-60V input. The problem is that the charge current doesn't always match the set point, and the result depends on the input voltage at which the converter is started (or restarted). When it starts with VIN below about 32V, the charge current is very unstable and oscillates at certain input voltages. Occasionally it lets the full input current limit through to the battery. The higher the startup voltage is above 32V, the cleaner the regulation is down to about 18V. I've even observed that if I startup the charger at 40V with HW limiting the charge current to 2.1A, and then lower the charge current to 1.5A, the output current is even more stable and clean than if I startup at 1.5A and leave it there. I found this after a lot of testing in which the charger was stuck in the bad state without my realizing it. I've listed the tests in the order I did them. The marked-up schematic, matching the exact configuration of my eval kit, is attached. Charger Hardware and Settings: BQ25756EVM (SLUUCT7D). All power-stage parts (FETs, input and output capacitors) are stock. Modifications are marked on the attached schematic Inductor L1: Bourns SRP1038A-150M, 15uH. DCR 40mOhm typ/45mOhm max, Irms 6.25A, Isat 10A Switching frequency: 250kHz (R_FSW = 133k) DRV_SUP: Tried with stock setup as well as with external 10V DC supply - same results R66 (ILIM_HIZ) = 4.99k, about 4A input current limit (5mOhm R_AC_SNS) R67 (ICHG) = 24k, about 2.1A hardware charge current limit (5mOhm R_BAT_SNS) ACUV/ACOV divider: R21 = 1.00M, R27 = 54.9k, R30 = 19.1k. Calculated UV about 16V (17.5V by measurement when charging) falling, OV about 67V rising. I have not applied more than 55V to VIN to verify yet as the eval kit has a max input voltage spec of 55V. FB divider: R26 = 249k, R64 = 14k (VBATREG about 29V) TS network: R34 = 4.99k, R68 = 25.5k Load: 8S LiFePO4 battery at about 26.5V, which can accept Icharge up to 10A Bench supply current limit setting: 5A Tests and Results: 1. Initial testing: started at 36V input voltage Powered up at a VIN=36V with the charge current set to 1A. Everything worked as expected. Charge current was stable and matched the set point. Changing the current with ICHG_REG worked. Changing the charge current limit with the registers also worked. 2. Startup at 25V Powered up at 25V with the same settings. The current behavior was wrong. While lowering VIN from 25V, at about 22V the charger drew 4.1A from the input and charged at about 3.3A, despite 1A set in HW and in the register. It stayed there until UVLO. When I raised VIN back to about 24.4V the current dropped back to 1A and held it up to 55V. At some input voltages there is a lot of noise on the current waveform. The dominant frequency was about 945Hz. I did a lot of other testing in this state to figure out what was going on with the charge current and why it wasn't following my set point. 3. Finding the startup voltage dependence After a full power cycle (input off and battery disconnected) and powering up at 40V the charger worked correctly again. I then turned the input off and back on at 25V with the battery still connected, so the chip was presumably powered from the output. It went straight back into the bad state. Starting at 40V with the current set to 1.5A, it regulates correctly but has some slightly noisy spots (see below). At any startup voltage below about 32V, the output current is below the set point and unstable, or the chip goes into input current limiting and the Ichg is slightly below the input current limit. The charger seems to recalibrate every time I disable and enable it. Startup from fully off at 40V with 2.1A set in HW, then lowering VIN: a few noisy spots, but the current stays in the 1.6A to 1.9A range. Then lowering the current to 1.5A in software after the startup at 40V: rock solid DC all the way down to 18V. Disabling and enabling the charger at 40V with 1.5A already set: noisy spots appear. Starting at a higher current and then lowering it in SW seems to be more stable than starting at the final current. With the ICHG HW pin disabled, setting ICHG_REG to 2.5A, disabling the charger, setting VIN to 25V and enabling it: ICHG is stuck at 1.2A, and setting 1.5A has no effect. Then cycling VIN up and down gives the odd behavior from before (sometimes below the set point, sometimes above, sometimes jumping to the input current limit). A high current setting at startup does not fix a low-VIN startup. Summary: If the converter starts at 32V or higher, it regulates correctly from 18V to 55V (the highest I've tested), and regulation is cleaner the higher the startup voltage. If it starts below about 32V, it stays in a bad state until the charger is restarted with VIN above 32V. Questions: The datasheet (6.3.3.3) says the converter toggles the SW node for about 40ms at startup to calibrate the compensation. Is it expected that this calibration depends on VIN relative to VBAT, or on the charge current at startup? Is there a minimum VIN/VBAT for good calibration? My guess is that it needs headroom, around 1.2×VBAT. Or maybe I need a different inductor to improve stability and calibration (L/DCR=0.375uH/mOhm so it seems to be suitable)? Is there a recommended startup sequence or register setting that gives reliable calibration at any VIN from 17V to 60V? Can the calibration be read back, saved, reloaded or bypassed? I'm thinking I could have production techs power up the charger at 40V, save the calibration in the processor, and then have the processor apply that calibration every time after the charger restarts. This is a lot of information to process. I'm hoping it's clear enough and you are able to help. Thanks. BQ25756EVM Schematic Mods.pdfpower deliveryBQ25756BQ25756EVMhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686918/bq25750-bq25750-bq25690-over-discharged-battery-pack-recovery/6502188Mon, 05 Oct 2026 22:44:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:49771137-165f-4a8d-a11a-771d84690fb1Ethan GallowayHello Hao, I don't recommend using the BQ25750 for this setup. I think the BQ25756 would be better to use here. The BQ25756 does not have battery pack detection. The BQ25756 goes into trickle charge mode when the battery is below 3V. Trickle charge mode charges the battery at ≈100mA. Best Regards, Ethan Gallowayhttps://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1683364/am263p4-q1-the-application-image-write-via-uniflash-version-9-3-0-5401-is-actually-only-completed-up-to-the-fisrst-1mb/6502186Mon, 05 Oct 2026 22:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e9200c46-afbf-4ee6-b9a1-eb228fb2106bATSUKI IMADAHi Aswin, I tried Test 1 through Test 3 with both flasher binaries you suggested. Results: - custom_flasher_sdk_v26.out → NG - custom_flasher_sdk_v11.01.out → NG Unfortunately, the issue was reproduced with both binaries. I confirmed this with UniFlash 9.6.0. If there are any other points I should check, please let me know. Also, I would appreciate it if you could answer the following questions I asked previously again: >・When flashing an Application Image built in the SDK 11.00 environment, is it acceptable to continue using the SDK 9.02-based Custom Flasher? >・In the SDK 11.00 environment, is it necessary to use UniFlash 9.6.0? If there is a recommended UniFlash version for SDK 11.00, please let us know. Requested response date: October 8, 2026 Imadahttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1686723/pga900-pga900-pga900-pga900evm-software-is-missing/6502187Mon, 05 Oct 2026 22:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a9258008-e825-42f5-862b-bcf7107fda44Eric.PreissHi Ihor, I sent you a friend request. Please accept it and we can discuss this question offline. Thanks, Erichttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1686898/ads1261-ads1261-sampling-rate-per-channel/6502184Mon, 05 Oct 2026 22:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:559288eb-641b-43c1-a94b-aa33cdee8435Eric.PreissHi Narendra, Please reference the following application note describing conversion latency and system cycle time. There are examples for ADS1261 in the document: https://www.ti.com/lit/an/sbaa535a/sbaa535a.pdf Use this as well as the ADS1261 datasheet to determine sample rates achievable with your 10 input design. Use Table 8 for the conversion latency due to filter settling time. You are subject to this latency time each time you switch channels, since the filter has to settle. Let me know if you have further questions. Thanks, Erichttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686351/tps25751-usbcpd-application-customization-tool-initial-setup-and-gpio-event/6502181Mon, 05 Oct 2026 22:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:96c5ea2d-1dd1-4804-b146-56a9919dbae5Kweku KorsahHi Katilynn, I look forward to your response tomorrow. As for your question, any USB-C device could be plugged into the port, but the intent is to only provide power. Please refer to the attached file. I have limited space and would like to keep the flexibility that the TPS25751D provides. From what I've read on other posts and the datasheet (also from the customization tool), it should be able to operate as source only. e2e.ti.com/.../E2E1686351_5F00_TPS25751D_5F00_System-Block-Diagram_5F00_10_2D00_5_2D00_2026.pdfhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686140/bq25886-request-to-check-the-circuit-diagram/6502180Mon, 05 Oct 2026 22:34:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6ce3acb0-234d-49e4-96b8-c30e72bb6f7fNing THi Nishie, Accepted. Thanks, Ninghttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686334/bq25619-clarification-required-on-bq25619-batsns-open-detection/6502176Mon, 05 Oct 2026 22:31:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8bcb1742-1704-4cf4-9640-0ba65585e03eNing THi Sneha, BQ25619 should behave similar in host-controlled mode for BATSNS_STAT. Do you have any local TI support team? Thanks, Ning.https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1686882/hdc1080-hdc1080-application-support/6502175Mon, 05 Oct 2026 22:29:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b78d9da7-4a11-426b-bab0-ae0df0dabb1ajoseph lyIs there someone I can talk to about ordering a dozen for engineering trials?https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1686882/hdc1080-hdc1080-application-support/6502172Mon, 05 Oct 2026 22:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:40c3454e-b3ee-49db-97cb-a333311fb6d0joseph lyHi Alex, This HDC3120-Q1 looks extremely interesting and will look into it. It would be ideal if it was already packaged in protective enclosure but maybe thats not so challenging in the end. Will look into the flex pcbs you mention. great suggestion thank you very much. -Joehttps://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1686839/afe11612-sep-afe11612-sep-d--terminal/6502171Mon, 05 Oct 2026 22:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:d5e2af40-67bc-4e48-a2ed-4266bc0f1e8fErin BowrieHi David, I've asked our designer to take a look to see if shorting the internal bias will cause any issues, I'll let you know what he says when he gets back to me. Thanks, Erinhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1685004/drv8334-drv8334-3x-pwm-how-to-support-different-bldc-blowers-with-different-hall-phase-commutation-relationships/6502165Mon, 05 Oct 2026 22:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b4874d70-d95b-426b-9843-25882c14bba8Joseph FerriHello, The 6-step Hall sequence order (5→4→6→2→3→1) can be identical across motors, but the specific U/V/W excitation tied to each Hall code is motor-specific. You can store this in your STM32 as motor specific commutation tables selected by whichever blower is being used. Then, the following inputs from the halls will be correctly interpreted by the STM32. So in this case, you need the halls to first go to the STM, go through the selection to determine which table to follow, then generate the correct outputs to go to the DRV. Thanks, Josephhttps://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1686982/drv8334-basic-clarification-on-hall-to-phase-commutation-for-different-bldc-motors/6502164Mon, 05 Oct 2026 22:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3c170c4a-4c62-40ef-a649-84a802c7df7eJoseph FerriHello, The 6-step Hall sequence order (5→4→6→2→3→1) can be identical across motors, but the specific U/V/W excitation tied to each Hall code is motor-specific. You can store this in your STM32 as motor specific commutation tables selected by whichever blower is being used. Then, the following inputs from the halls will be correctly interpreted by the STM32. So in this case, you need the halls to first go to the STM, go through the selection to determine which table to follow, then generate the correct outputs to go to the DRV. Thanks, Josephhttps://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1686971/dlpc3479-bit-partition-in-a-frame-for-an-8-bit-color-on-the-dlpc3479-dlp4700/6502162Mon, 05 Oct 2026 22:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:535429e9-0c25-4211-afbe-8dc30953b55dAaron BlackHello Tatsu, Thank you for reaching out to the E2E community with your question! An 8-bit color depth is achieved by displaying specific bitplanes for a calculated duration of time. You can think of the final color value as a combination of these individual bits. For example, if you want to display a red level of 200, you would utilize the combination of 8 + 64 + 128, or the bitplanes for Bit 3, Bit 6, and Bit 7 would be displayed in the 'on' position. Any unused bitplanes will be displayed as "dark time," or mirrors in the 'off' position. I hope this helps clarify the concept! Best, Aaronhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686954/uc2843a-request-for-replacement-for-uc2843ad8/6502157Mon, 05 Oct 2026 22:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a26efaca-7b6c-4361-b78c-5f04eb22b35cAdhvaidh AravindHi Vijay, Thanks for reaching out via E2E. This device belongs to the UC284x family of devices. We have only NRND'd the tube variant of the UC284xA family (In your case - UC2843AD8). The tape and reel variant ( UC2843AD8TR ) is still active as highlighted below. Even though both these OPNs (Orderable Part Numbers) belong to the same family, only UC2843AD8TR went through 300 mm wafer refresh, and will follow the new datasheet - Rev. H (which can be found on the main product folder). In other words, UC2843AD8 that you currently have in your system would be following the old datasheet (Revision G). For difference between both these revisions, please refer to the Revision History section of the new datasheet (pg. 24). For sample requests for the new 300 mm material, please reach out to your assigned Field Applications Engineer. Please let me know if you need any help with that. If you have any further technical questions, please get back to me. Thanks. Best, Adhvaidhhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1687163/lm60440-no-load-condition-stable-voltage/6502155Mon, 05 Oct 2026 22:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:bd684811-ec4f-494c-bfbe-35eae5631e47Andrew KutzlerHi Filipe? Is using an FPWM an option. If they operate at a higher FSW and use a minimal of COUT that could also help with the transient overshoot if they want to pursue PFM operaiton. Thanks, Andrewhttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1687088/tps3705-tps3705-recommended-handling-of-unused-pfo-and-wdo-pins/6502150Mon, 05 Oct 2026 22:03:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:852c3465-fccc-480f-87b6-67dbefe9d3d5Sila AtalarHi Raita, It seems like you don't need watchdog and PFO, please let me know would you be interested newer simpler supervisor that can monitor single channel. If you can provide your requirement, I can recommend couple of our devices. Please find my answer in below. 1. You can refer the below E2E answer for PFO. PFO can be left open. TPS3705: Can PFI leave float? 2. If you want to disable the watchdog, you must leave the WDI floating. If the WDI pin is open, WDO will be high. It's an push-pull output so if you don't want use WDO output you can leave open. Best, Silahttps://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1686055/bq4050-bq4050-programming/6502149Mon, 05 Oct 2026 22:02:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:573cbb97-c834-4fd9-9101-84c45891f87dAlan FriasHello Mike, For the most part we recommend using EV2400 during development use and there is no other recommend way for the user to program the gauge for there application. You could possibility try to write the device parameter through i2c but we don't support this type of development. Thank you, Alan