Testing the eeprom pointer accesses, I think I've found a bug:

Simulating with Proteus VSM: "Attemp to write to EECON2 without setting WREN bit is ignored."

WREN can be found in EECON.2 and not in EECON.3 (WERR).

BSF _EECON1, 3, 0 ; WREN = 1: enable write access

Thanks a lot

On Fri, Apr 20, 2012 at 12:52 PM, Diego Herranz <diegoherranz@diegoherranz.com> wrote:
Thanks Raphael!

I'll try to test it this weekend and I'll let you all know.

Thanks a lot!

On Fri, Apr 20, 2012 at 8:37 AM, Frieder Ferlemann <frieder.ferlemann@web.de> wrote:
Hi Raphael,

Am 20.04.2012 01:05, schrieb Raphael Neider:
> starting with svn 7610, sdcc/pic16 allows read/write access EEPROM via
> generic pointers in the range of 0x40_0000 to 0x7F_FFFF (though only

Please add a compiler warning for write access (where possible).

It is _very_ easy to get the writes wrong (by concept and
(to a lesser extent) by accident within the application program).


For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
Sdcc-user mailing list