> - 86 bytes of Object memory
> - 72 bytes of variable memory space
> - 8KB of program code space
> - 256 bytes of fast internal EEPROM variable space
>
> Now when I open Memory map it seems that all my program occupies 86
> bytes of object memory.
> So how can I take an advantage of variable memory and EEPROM?
> BTW, how can the code space be extended?
>
> In the end, could anyone just simply explain me where physically are
> all those memories located (there is just PIC chip and EEPROM, right?)
> and how should the be properly used and what about access time issues?
>
> Thanks is advance :)
>
Programs are stored in the EEPROM and access is slow. You can also
store data in the unused space of the EEPROM but, again, access is
SLOW. You can install a larger EEPROM for program code and data
storage but it won't solve your object memory problem.
The PIC starts out with 368 bytes of RAM. That's all there is and
there won't be any more. So, it is divided up into object memory and
variable memory storage plus whatever the OOPic interpreter needs.
There is a small EEPROM inside the PIC that can be used for data storage.
But, in the end, there are 86 bytes of object memory and that is all
there will be and increasing the EEPROM size won't solve this.
External servo controllers are the way to go if you want to stay with
the OOPic.
Richard
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment