Problem with variables in memory

[Hristo]

For 24 hours uninterrupted work I was unable to repeat the problem from yesterday.
Tomorrow I will continue with the additional peripherals modules that add RS485 communication to the main program.

Hristo

[janni]

Well, I haven't traced any sure source of S_PulsesCoin overwriting, so maybe there isn't any (wishful thinking ).

I had more detailed response ready when the forum logged me out and erased it (seems that mE's IT guys finally found a way to discourage the use of the forum - I'm certainly not going to log in several times a day). As I have no time to write it all again, here's only a suggestion of another safeguard - move f16_fileDesc variable in the FAT16 library file __Lib_MmcFat16_Defs.mpas to the end of RAM:

Code: Select all

var f16_fileDesc    : array [MAX_FILES] of F16_FILE;  absolute 0xC00+SizeOf(SECTOR);

[filip]

Hi.

@janni,

I had more detailed response ready when the forum logged me out and erased it (seems that mE's IT guys finally found a way to discourage the use of the forum - I'm certainly not going to log in several times a day)

We apologize for the issue with the forum, please find the more detailed answer here :
viewtopic.php?f=11&t=76330

Regards,
Filip.

[DarkWolf]

Hi,

I also had variable errors at a certain level of optimization. It worked when this variable was excluded from optimization. The volatile modifier does this.