SMBUS communication is performed with BQ78350-R1.
Communication with SBS command 0x0055 (chargingStatus) is different from other communication.
0x0055 command is Block communication.
For block communication, the LSB is the first to communicate.
0x0055 command, MSB is communicated first.
Does the 0x0055 command behave differently from other commands?
Different movements could not be found in the Technical Reference.
Am I seeing the wrong thing?
The ChargingStatus (0x0055) command is one of the ManufacturerBlockAccess commands and returns data as little endian. To get the ChargingStatus, write a value of (0x55 + 0x00) to command 0x44. Then do a block read of 0x44. Here is an example below I did on the EVM:
This indicates the ST and FCHG bits are high and I confirm this on the Registers screen of bqStudio:
Best regards,
Matt
Thank you for your response.
It is stated in the Technical Reference that the ManufacturerBlockAccess and the SMBBlockAccess are the same.
This problem was noticed when checking the ChargingStatus's PCHG behavior.
PCHG is in bit 0 of ChargingStatus.
Data of I2C communication at the time of test is attached.
Communication will start from 0x01 if it is little endian.
Do you need special communication only for ChargingStatus?
Best regards.
