Yes. SMbus introduced PEC error checking probably due to such issues. As far as the original issue, a bug was possible since the issue was resolved through an updated SDK.Sorry, my bad, I meant read timeout, as on the scope the last operation is a READ.
On write it's the slave acknowledging the data.
Or it might be that the scope screenshot is not related to the glitch ...
Or could be an SDK bug ... you can check the changelog of SDK.
As a side note, I cannot say I2C signaling is very robust, just forget a pull-up and everything is ACK
The newsest SMBus 3.x can go 400 kHz, I think. At least I have a device that seems to specify use at that speed.
It started as a battery thing of course but moved into other devices, as you well may know.
EDIT: As far as smart batteries I would use a good old TI MSP430 because it's a low power device and there's a library for SMbus. For that I usually use the recommended "Code Composer Studio" but you can do it from the command line as well. I believe there's a free download for that as well. That is, their compiler.
https://www.ti.com/tool/MSP430-SMBUS
Statistics: Posted by breaker — Wed Jan 15, 2025 8:16 pm