Other Parts Discussed in Thread: BQ79616, USB2ANY
The Bridge_FAULT_COMM1 register is read to identify any problems with the comm frame (FCOMM_DET). This fault byte does not clear when the fault has been removed using the simulator, as confirmed using the logic analyzer. If the bridge faults are cleared periodically by writing to the Bridge_FAULT_RST register, the fault is not being identified when present. This makes it difficult to recover from any COMM faults. Am I missing something in the BQ79600 register setup?
Today morning (5/30/23), I tried the same thing with the USB2ANY, BQ79600 EVM and BQ79616. After initial measurements started, I unhooked the cable connecting the BQ79600 an the BQ79616. No faults were reported on the BQ monitor. Voltage readings just froze and stayed unchanging. FCOMM_DET bit was set. I reconnected the cable. Voltage readings resumed. But the FCOMM_DET bit stayed set, it did not auto clear. I have the fault generation in the firmware based off the status of the FCOMM_DET bit. How does this need to change?
I also powered off the BQ79600 and re-did the wakeup, auto address sequence and started polling from the BQ GUI. The FCOMM_DET bit stayed set. Why is this value persistent?