On Wed, 5 Apr 2023 17:57:00 +0200, Christo Crause via fpc-pascal
wrote:
>The use of WriteBytesToReg in the TI2c_eeprom.WriteData method seems fine,
>perhaps retest with the updated WriteBytesToReg method.
I pulled the i2c.pas file from GitHub (actually downloaded the zip since I don't
really
On Wed, Apr 5, 2023 at 12:43 PM Bo Berglund via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> On Wed, 5 Apr 2023 11:40:09 +0200, Christo Crause via fpc-pascal
> wrote:
> >Looking at the datasheet for CAT24C128, Fig. 6 Byte Write Sequence, shows
> >no repeated start condition between
On Wed, 5 Apr 2023 11:40:09 +0200, Christo Crause via fpc-pascal
wrote:
>Looking at the datasheet for CAT24C128, Fig. 6 Byte Write Sequence, shows
>no repeated start condition between register address and data bytes. I
>suspect that the second i2c message should contain the I2C_M_NOSTART flag,
On Wed, Apr 5, 2023 at 11:22 AM Jean SUZINEAU via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> May be you could get the source code of i2ctransfer from i2c-tools and
> compare it with the code in i2c.pas ?
>
Good idea, that led to the suggestion to try the WriteBytes method which is
On Wed, Apr 5, 2023 at 7:55 AM Bo Berglund via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> On Wed, 05 Apr 2023 00:33:50 +0200, Bo Berglund via fpc-pascal
>
> I *can* write a sequence of bytes into the EEPROM succsessfully using an
> i2c-tools command like this:
>
> i2ctransfer -y 1
May be you could get the source code of i2ctransfer from i2c-tools and
compare it with the code in i2c.pas ?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
