This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BQ76PL536A: SPI communication: no SDO activity

Part Number: BQ76PL536A

Single IC to monitor 4 cells with ESP32-s2 host.

Observation:

  • SDO goes high when HSEL is pulled low, then it stays high all the time
  • when sending a read or a write command, SDO stays high
  • write commands do not seem to register (reset, address claim...)
  • both ALERT_H and FAULT_H stay high all the time (ALERT_N and FAULT_N are connected to VBAT) - but of course I cannot read the registers!

Write RESET

Write ADDRESS_CONTROL

Read DEVICE_STATUS

I have tried to increase the delay between CS active (low) and start of clock, but that has no effect.

Is there something wrong in the command I send and that could create the problem?

Any idea on what I can do / check to further diagnose?

Thank you for any guidance you can provide

Philippe

BBy the way, MOSI timing looks right for SPI mode1:

  • I did follow instructions section 7.3.1.12 (p.25):

    FAULT_N should always be connected to the FAULT_S of the next higher device in the stack. If no higher device exists, it should be tied to VBAT of this bq76PL536A, either directly or via a pullup resistor from approximately 10 kΩ to 1 MΩ.

    After reading the datasheet again and again, I found the answer in the VBUS section 7.3.5 (p.29) that I skipped up to now as I do not use VBUS:

    NOTE
    Designer Note: North (_N) pins of the top, most-positive device in the stack should be connected to the BAT1(2) pins of the device for correct operation of the string. South (_S)
    pins of the lowest, most-negative device in the stack should be connected to VSS of the device

    After connecting those pins it now works as expected: