Hi Charlie, everyone,
On 3/28/23 11:33, Karoly Balogh wrote:
[cut]
If you want to export a variable without name mangling, you must declare a
public name for it, something like:
var
foobar: integer; public name '_myfoobar';
Then reference it as:
var
foobar: integer; external name '_m
On Mon, 03 Apr 2023 15:09:38 -0400, Dennis Lee Bieber via fpc-pascal
wrote:
>On Mon, 03 Apr 2023 20:55:43 +0200, Bo Berglund via fpc-pascal
> declaimed
>the following:
>
>>I just tested by writing four 0x00 bytes in a row, then verifying that the
>>memory read shows these, then writing other data
On Mon, 3 Apr 2023 14:37:48 -0400, "Jeffrey A. Wormsley via fpc-pascal"
wrote:
>I noticed you put the part number in the original email.
>
>Interestingly, the data sheet mentions 64 byte pages, and 1,000,000 erase
>cycles, but does not mention the need to erase a page before writing. So
>perhaps
On Mon, 03 Apr 2023 20:55:43 +0200, Bo Berglund via fpc-pascal
declaimed
the following:
>I just tested by writing four 0x00 bytes in a row, then verifying that the
>memory read shows these, then writing other data and again verifying that the
>data is there.
>
Which may only mean the chi
Is there some way I can programmatically use FreePascal to save and Restore
all the settings found in the Windows 10 Display settings such as the
resolution and position of each monitor and if they are enabled or not?
___
fpc-pascal maillist - fpc-p
On Mon, 03 Apr 2023 20:55:43 +0200, Bo Berglund via fpc-pascal >On Mon, 3 Apr
2023 14:26:17 -0400, "Jeffrey A. Wormsley via fpc-pascal"
> wrote:
>
>>I've been using i2c and SPI eeproms for almost two decades. All of them
>>can read/write a single byte if that's what you want to do, but the
>>write
>On Mon, Apr 3, 2023 at 10:53?AM Bo Berglund via fpc-pascal <
>fpc-pascal@lists.freepascal.org> wrote:
>
>> On Mon, 3 Apr 2023 08:42:12 -0400, "Jeffrey A. Wormsley via fpc-pascal"
>> wrote:
>>
>> >>
>> >> i2c_read_reg works too inasmuch as it does not error out, but it
>> returns FF
>> >> whatever
I noticed you put the part number in the original email.
Interestingly, the data sheet mentions 64 byte pages, and 1,000,000 erase
cycles, but does not mention the need to erase a page before writing. So
perhaps this part does not have that restriction.
If you're making a library specifically fo
I've been using i2c and SPI eeproms for almost two decades. All of them
can read/write a single byte if that's what you want to do, but the
write/erase restrictions I noted are there for any parts I've ever used.
If you write a byte to $00, you cannot write it to $01 without first
erasing the enti
On Mon, 3 Apr 2023 08:42:12 -0400, "Jeffrey A. Wormsley via fpc-pascal"
wrote:
>>
>> i2c_read_reg works too inasmuch as it does not error out, but it returns FF
>> whatever addres I read like the i2c-tools command does.
>> I am not sure that it is correct though...
>>
>
>Yes this is expected, as
>
> i2c_read_reg works too inasmuch as it does not error out, but it returns FF
> whatever addres I read like the i2c-tools command does.
> I am not sure that it is correct though...
>
Yes this is expected, as eeproms erase to $FF. You can write to the same
byte as many times as you want, as long
11 matches
Mail list logo
