Hi,
I'm trying to read the factual and the predictive values from the internal registers of the BQ2060A which is embedded on a recently bought SAFT battery 2s1p package (app. 7.8VDC-6000mAh) without any EEPROM installed on it. The hardware connections between the BQ2060A and the MSP430G2553 (LaunchPad) are consisting of three SMBUS signals, i.e. GND, SMBUS-DATA (with 10K pull-up to VCC (3.45V) of the LaunchPad) and SMBUS-CLK (with 10K pull-up to VCC (3.45V) of the LaunchPad) ones. I have also used a few hardware setup cases, such as battery pack with a load only, battery pack without any load and any charger and finally battery pack with a load and a charger together.
In addition to the hardware setup mentioned above, I have used the below TI based software items by means of using TI's Code Composer Studio/ Version 6.2.0.00048 and the SLAVE_ADDRESS of 0x0b for the BQ2060A on the battery as well as disabling the PEC by means of commenting the related line, i.e. editing it like " //#define SMB_DEFAULT_PEC_ENABLED /*! Define to enable PEC */ ":
SMB_Master00_AllProtocols (especially for the cases "READ_WORD_TEST" and "READ_BYTE_TEST"/with 2 bytes' selection)
SMB_Master01_ReadByte_Echo (with 2 bytes' selection)
While inserting a breakpoint at the end of the test case of the code of SMB_Master00_AllProtocols (especially for the cases "READ_WORD_TEST" , I sometimes see 1, 32, 80, 592 values for the value of "ret" in the expression window while I see "., ., ., ," (various commas and dots) for the value of the "Resp_Buff" and these values are not changing in an accordance with the battery function commands, such as 0x08, 0x09, 0x14, 0x16, etc. That is, I write a command of 0x08 for reading the "Temperaure Value", but I always read "., ., ., ," (various commas and dots) for the value of the "Resp_Buff" even I change this command into the other options, such as 0x09, 0x10, 0x14, 0x16, 0x1c, etc.
On the other hand, I still see "., ., ., ," (various commas and dots) for the value of the "Resp_Buff" and these values are not changing in an accordance with the battery function commands, such as 0x08, 0x09, 0x14, 0x16, etc. while inserting a breakpoint at the end of the test case of the code with SMB_Master01_ReadByte_Echo (with 2 bytes'selection).
I'd be very glad if you let me know what to do from now on.
Thanks in advance for your very valuable feedback,
Kind Regards,
R.K. Arikan
P.S. I have also used 220 Ohm serial line termination resistors for SMBUS-DATA and SMBUS-CLK lines on the LaunchPad part and removed the protection diodes from each signal mentioned above in terms of minimizing the bad capacitance effects of them according to the knowledge on the pdf document of "SMBus-made-simple 5F00 v6".