This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Thursday, November 8, 2007

[oopic] OOPic-R limits?

Hi,
I have just reached the object memory limit (Error 20 - Memory
overflow) by using ~12 oServo objects (hexapod robot) and ~10 oByte
variables. Not much, isn't it?

Following Clark's book (p.20) OOPic-R has:
- 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 :)


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:

http://docs.yahoo.com/info/terms/

No comments: