On Sun, 2 Apr 2023 23:14:25 +0200, Christo Crause via fpc-pascal
wrote:
>On Sun, Apr 2, 2023 at 9:30?PM Bo Berglund via fpc-pascal <
>fpc-pascal@lists.freepascal.org> wrote:
>
>> Is there a reason that there is no i2c_write_reg demo in the github
>> package?
>>
>
>I haven't gotten round to that,
On Sun, Apr 2, 2023 at 9:30 PM Bo Berglund via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> Is there a reason that there is no i2c_write_reg demo in the github
> package?
>
I haven't gotten round to that, waiting for hardware to test the code with.
I will try to write one so I can
On Sun, 02 Apr 2023 15:07:48 -0400, Dennis Lee Bieber via fpc-pascal
wrote:
>On Sun, 02 Apr 2023 16:16:46 +0200, Bo Berglund via fpc-pascal
> declaimed
>the following:
>
>
>>
>>
>>Byte Write
>
>>a location within a 64 byte
On Sun, 2 Apr 2023 07:31:43 +0200, Christo Crause via fpc-pascal
wrote:
>On Sat, Apr 1, 2023 at 9:57?PM Bo Berglund via fpc-pascal <
>fpc-pascal@lists.freepascal.org> wrote:
>
>> Question:
>> Can I use Linux file system commands to read/write the data on the i2c
>> EEPROM
>> memory device and if
On Sun, 02 Apr 2023 16:16:46 +0200, Bo Berglund via fpc-pascal
declaimed
the following:
>
>
>Byte Write
>a location within a 64 byte page. A byte following the
>address bytes will be interpreted as data. The data will be
On Sun, 02 Apr 2023 10:23:24 +0200, Bo Berglund via fpc-pascal
wrote:
>On Sun, 2 Apr 2023 07:31:43 +0200, Christo Crause via fpc-pascal
> wrote:
>
>>On Sat, Apr 1, 2023 at 9:57?PM Bo Berglund via fpc-pascal <
>>fpc-pascal@lists.freepascal.org> wrote:
>>
>>> Question:
>>> Can I use Linux file
On Sun, 2 Apr 2023 07:31:43 +0200, Christo Crause via fpc-pascal
wrote:
>On Sat, Apr 1, 2023 at 9:57?PM Bo Berglund via fpc-pascal <
>fpc-pascal@lists.freepascal.org> wrote:
>
>> Question:
>> Can I use Linux file system commands to read/write the data on the i2c
>> EEPROM
>> memory device and if
On Sat, 1 Apr 2023 20:30:02 -0400, Travis Siegel via fpc-pascal
wrote:
>Generally, raspberry pi devices connected to other devices will (by
>default) use python for their programming. The python libs have all the
>setup and tear down code built in. You can use C as well, so I see no
>reason
