<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SMBus between bq78350-R1A and nRF5340 - communication is not stable</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/98473/smbus-between-bq78350-r1a-and-nrf5340---communication-is-not-stable</link><description>Hello everybody, 
 We have a battery management system here based on TI bq78350-R1A with SMBus (slave, PEC disabled). 
 Logic I2C levels now = 2.5V . (we tried 3.3V but with same issues). 
 Time to time we see using oscilloscope that bq78350-R1A sends</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 15 Jun 2023 09:20:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/98473/smbus-between-bq78350-r1a-and-nrf5340---communication-is-not-stable" /><item><title>RE: SMBus between bq78350-R1A and nRF5340 - communication is not stable</title><link>https://devzone.nordicsemi.com/thread/431194?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2023 09:20:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3768559e-7902-4557-b07d-4f0271f2b7ec</guid><dc:creator>SimpleSoft</dc:creator><description>&lt;p&gt;THank you, indeed. Problem was inside of TI chip, SMBus works fine.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SMBus between bq78350-R1A and nRF5340 - communication is not stable</title><link>https://devzone.nordicsemi.com/thread/419566?ContentTypeID=1</link><pubDate>Tue, 11 Apr 2023 08:26:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:562fd3b0-a791-471e-9da2-54a24e771b22</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;My suggestion would be to look at the datasheet for the sensor in question to try to find if there for instance are timing specifications (e.g. between I2C transactions) that you are not following. I think you may contact the sensor manufacturer to get their comment on what may cause the sensor to NACK communication if the address is correct.&lt;/p&gt;
&lt;p&gt;Clock stretching is fully handled in hardware, and will work automatically.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>