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.

Friday, April 4, 2008

[oopic] Re: Extra memory (Future plans for robot to map room details)

--- In oopic@yahoogroups.com, "jon_mark_go" <jonmarkgo@...> wrote:
>
> So basically the 256k EEPROM chip I installed is only really usable by
> the oEEPROM object, not by the oopic itself for storing the program?

Even the oEEPROM object is limited to a 16 bit (64kB) address.

About the only way to use I2C based EEPROMs is in 64kB devices with
different I2C addresses. You can have 8 such devices. The OOPic S
board has a socket for a 2d device (E1). The R board has just one
device so the other 7 would need to be somewhere else.

But, are we talking bits or bytes? A 64kB (byte) device is 512kb
(bits). The largest device from Microchip is 1Mbit or 128kB and it
uses a bizarre control sequence. Further, only 4 devices can be
addressed. In the end, it just saves package space over 2 of the 64kB
devices at the cost of a complex control strategy - block switching.

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:

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

No comments: