On 05/12/2015 12:54 PM, Jacques Nilo wrote:
@Rob: appendix B (p12) of AN1673 gives all the necessary information
about space location for different chips: first and last address of
HEFM + size of row.
I have done some more reading....
1. It seems all midrange PICs with HEF have 128 bytes of HEF at high
code memory.
2. Row size seems a relation of code memory: 16 bytes with 1K and 2K, 32
bytes with 4K and 8K.
If this is true then these constants can easily be derived from already
present info for the device file generation script, and thus can easily
be added to the device files (when it is known that a PIC has HEF!)
If the value of code size is available to the user at compile time (I'm
not sure about that) then the HEF library can derive these values itself
and no device file change is required.
It would be nice if the compiler accepts and honors a second pragma
code, but if not an overlap is easily checked with the compiler log.
But I do not see in flash_data.jal how the space reservation issue is
handled.
Well, it is a limited implementation! It assumes that the user checks
(with the compiler log) if program code overlaps the block reserved for
data.
Regards, Rob.
--
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.
