Skip to main content
Visitor II
June 26, 2025
Question

STM32U5A5QJI6Q (BGA Package): How to solve missing I2C Pull-Up ?

  • June 26, 2025
  • 2 replies
  • 771 views

Hi Team,

We are currently working on a design using the STM32U5A5QJI6Q microcontroller in a BGA package, implemented on a 4-layer PCB. During the hardware development phase, we inadvertently omitted the external pull-up resistors on the I2C lines, specifically on PB6 (A5) and PB9 (A4), which are configured for I2C_SCL and I2C_SDA respectively.

Our software team has informed us that there is no option to enable internal pull-up resistors for these specific pins through software configuration. Given the constraints of the BGA package and the complexity of reworking inner-layer routing, we are seeking your expert guidance on the following:

  1. Is it possible to enable internal pull-up resistors on PB6 and PB9 via software or alternate configuration?
  2. If not, what are the recommended rework strategies for adding external pull-ups in a BGA-based 4-layer PCB design?
  3. Any best practices or application notes that could assist in resolving this issue without a complete board redesign would be greatly appreciated.

We would be grateful for your support in helping us resolve this issue efficiently.

Thank you for your time and assistance.

Best regards,
Sathiya

    This topic has been closed for replies.

    2 replies

    Super User
    June 26, 2025

    You can use the internal ~40 kOhm pullup resistors with reduced I2C clock rate, maybe 10 kHz, and it'll work just fine.

    TDK_0-1750949671887.png

    I'd put a scope on SDA/SCL to verify edges are sufficiently fast for the clock rate you choose.

     

    It's not ideal because your bus will be floating before the pins are initialized, but this will likely not be a problem. If it is and slaves are holding SDA low, SCL can be toggled to free up slaves.

    Visitor II
    June 27, 2025

    Hi,

    Thanks for the detailed explanation!  You mentioned  detail for STM32U5A5QJI6Q (BGA package).  we used STM32U5A5QJI6Q (BGA package) and using PB6 (A5) and PB9 (A4) as I2C lines for interfacing with a battery charger IC and fuel gauge chip. Since the I2C lines are routed internally without vias, you're unable to add external pull-up resistors, and we wondering:

    1. Can pull-ups be enabled via STM32CubeIDE or firmware?
    2. Can we switch to software I2C if needed?

    Is Possible to configure the  PB6 (A5) and PB9 (A4)  pin to Software I2C, if is possible how to change ?

     

    Regards,

    Sathiya

     

    Super User
    June 27, 2025

    This post makes no sense. AI slop? Just not reading?

    This is what I wrote:

    > You can use the internal ~40 kOhm pullup resistors with reduced I2C clock rate, maybe 10 kHz, and it'll work just fine.

    This is what you asked (again)

    > Can pull-ups be enabled via STM32CubeIDE or firmware?

    The answer is still yes.

    Super User
    June 26, 2025

    Internal pullups are not suitable as I2C pullups - much too high resistance.

    Does the I2C slave device(s) have accessible pins?

    Are there testpoints on the I2C lines? Vias?

     

    Nothing specific to STM32 here - this is just general prototype/rework stuff.

     
     

    AndrewNeil_2-1750949838692.png

    Image credit: https://www.circuitrework.com/services/circuit-board-modification.html

    Visitor II
    June 27, 2025

    Thank you for your response. Unfortunately, we cannot rework the board because it is very small, and there are no vias or external pads available to add a pull-up resistor.

    If possible, we would like to use the same pin for software I²C with the internal pull-up resistor enabled. Could you please confirm if this is feasible?

    Graduate II
    June 27, 2025

    As TDK has pointed out, You can enable the internal week pullup (worst case is 50K Ohm) this is about 10 times the resistor value normaly used on I2C. So this is only a work around for the prototype (You have to modify the schematics / PCB for a stable product), and requires that You reduce the I2C clock!