Hi guys,
I felt the need for a reorganisation of my Dev2jal script with which the
Jallib device files are generated. During this I discovered a possible
improvement with respect to the use of data memory.
As you probably know the compiler allocates data for variables
exclusively in unshared memory. Most of the midrange PICs have shared
memory in the range 0x70-0x7F and their device files have it declared as
such (with some exceptions). The bytes at 0x7E and 0x7F are reserved for
_pic_accum and pic_isr_w, but the other 14 bytes
are not available for the application program.
It crossed my mind to specify the range 0x70-0x7D as unshared data
memory, so 14 more data bytes would become available to the user program.
Note: This is already done for some PICs with only shared memory!
Something similar is going on with the baseline. In general these have
fewer shared data bytes, thus less bytes wasted, but on the other hand
these PICs have less unshared data memory too! So also for this group it
would be better to use the otherwase wasted shared memory a unshared
memory.
I'm (off list) in discussion with Kyle to check if this is OK!
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
