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,
> gsec

Clock 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.

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 ?
> 
> -jg

You 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

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

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