Hi, Can someone share some tips on how to increase the performance of an I2C driver code . My driver code do an EEPROM access via cpld, and performance is not as expected. rgds, gsec
need Tips on increasing performance of an I2C driver
Started by ●June 7, 2007
Reply by ●June 7, 20072007-06-07
Gsec wrote:> Hi, > > Can someone share some tips on how to increase the performance of an > I2C driver code . > My driver code do an EEPROM access via cpld, and performance is not as > expected.Which CPLD, and what does "not as expected" mean ? -jg
Reply by ●June 8, 20072007-06-08
On 08/06/2007 Jim Granville wrote:> Gsec wrote: > > Hi, > > > > Can someone share some tips on how to increase the performance of an > > I2C driver code . > > My driver code do an EEPROM access via cpld, and performance is not > > as expected. > > Which CPLD, and what does "not as expected" mean ? > > -jgYou could also add: Which processor? Hardware or bit-banged interface? What language? The OP could certainly benefit from reading this: http://www.catb.org/~esr/faqs/smart-questions.html -- John B
Reply by ●June 9, 20072007-06-09
On 8 Jun, 00:52, Gsec <Gaurav.Sai...@gmail.com> wrote:> Hi, > > Can someone share some tips on how to increase the performance of an > I2C driver code . > My driver code do an EEPROM access via cpld, and performance is not as > expected. > > rgds, > gsecClock out the data as fast as the I2C chip will take it. If your micro is not upto that then increase micro clock or find a better micro.