Kiste, Assuming the memory will be placed at the end of the flash (1F80-1FFF), the only trick is to check that memory is not over written by the compiler.
Vasile On Tue, May 12, 2015 at 8:41 AM, 'Oliver Seitz' via jallib < [email protected]> wrote: > Thinking again... > > IF a "pragma code" statement can change a previously defined code space > size without issuing a warning or error, it may be possible to write such a > library without compiler modification. It would however need a list of > chips which support the high endurance flash, and that list would also need > information which would generally belong in the device files. > Greets, > Kiste > > ------------------------------ > *Von:* 'Oliver Seitz' via jallib <[email protected]> > *An:* "[email protected]" <[email protected]> > *Gesendet:* 6:28 Dienstag, 12.Mai 2015 > *Betreff:* Re: [jallib] JAL library for managing High Endurance Memory ? > > Hi! > > > It's nextto impossible to write a stable library for that. The high > endurance memory is within the code memory space. It must be assured, that > locations which are used as EEPROM replacement are not occupied by program > code. That means, the more EEPROM space is needed, the smaller the machine > code program needs to be. > > And that's the problem: A high level language program can't know what size > the compiled code will be. It needs to be checked manually after > compilation. The jallib libraries are somewhat like "If it compiles, it > runs." A library making use of the high endurance flash can't provide that > level of safety. > > Sorry for that. > > Greets, > Kiste > > > > ------------------------------ > *Von:* Jacques Nilo <[email protected]> > *An:* [email protected] > *Gesendet:* 23:55 Montag, 11.Mai 2015 > *Betreff:* [jallib] JAL library for managing High Endurance Memory ? > > Hi all > I am currently working on the possibility to use the High Endurance > memory on the 16F1xxx as a replacement for non existing EEPROM on these > chips (e.g. 16F1509 or 16F1709) > There is an application note describing this (Microchip AN1673 > <http://ww1.microchip.com/downloads/en/AppNotes/00001673A.pdf>). > I was wondering if any one has ever work on porting the C library > described in this note in JAL ? > Jacques > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib. For more options, visit https://groups.google.com/d/optout.
