Oshonsoft memories

Thread Starter

camerart

Joined Feb 25, 2013
3,830
Hi,
I'm looking at the different memories in Oshonsoft. RAM, ROM EEPROM etc
If I write to a memory, or save a VARIABLE etc, it goes into different memories.
I can view the VARIABLE in 'watch variables' and other drop downs.
Here is a screen shot, showing lots of 0X40 memories.
Can anyone describe what they all are and how to address them, please. I'm not seeing the results, I would expect.

I'm experimenting, so don't try to make too much sense out of it!
 

Attachments

sagor

Joined Mar 10, 2019
1,049
Variables are stored in ram, not eeprom. The address of the variable is determined by the compiler at compile time.
Hence you should never use direct ram address access, as one simple change in code may cause the variables to be compiled into totally different addresses.
Always use variable names or arrays to access the value. That always works.
 

nsaspook

Joined Aug 27, 2009
16,322
EEPROM, on a typical controller, is modeled as a computer peripheral (like a hard-drive) that uses EEPROM module registers to store and retrieve information in bytes. It's not a memory location that variables can normally directly access.
 

Thread Starter

camerart

Joined Feb 25, 2013
3,830
Hi M and S,
I'm using PICs and they do have EEPROM, that can be written and read, but I've been advised to use them carfully, as they wear out.

I can see the Variable RAM addresses in the drop down.

I have been testing a few ideas out, and not seen the exact results, I was expecting. I've played recently with pointers, which may be what I should try again next.
Thanks.
C
 

nsaspook

Joined Aug 27, 2009
16,322
Hi M and S,
I'm using PICs and they do have EEPROM, that can be written and read, but I've been advised to use them carfully, as they wear out.

I can see the Variable RAM addresses in the drop down.

I have been testing a few ideas out, and not seen the exact results, I was expecting. I've played recently with pointers, which may be what I should try again next.
Thanks.
C
The normal PIC internal EEPROM endurance is usually over 100,000 cycles with retention of over 30 years.
Yes, they can be accessed but not using program direct memory variable semantics on a PIC.
https://exploreembedded.com/wiki/PIC_Internal_Eeprom
 
Top