Hi Karin
On 2011/04/21 15:23, Karin Willers wrote:
I am using jalv2 and jallib (currently jallib-pack-2.4n-0.6.0) on a
PIC10f206 for a few weeks. What I found is that in the sample file
'10f206_blink.jal' and the corresponding include-file '10f206.jal',
which will probably be used by people as a starting point for their own
programs, OSCCAL is never set.
True! And it has been discussed before here (or in Jallist).
There is a section in 'devicefiles.html' about how to use the
calibration word in high memory (of some PICs) and the danger when that
word is not a RETLW instruction (anymore).
I don't remember when I last updated this OSCCAL section, so you may
have to download that file to get the latest state.
Maybe this section needs further instructions?
This issue affects all 10fxxx devices. In my opinion, the include files
should be changed accordingly.
No! By design a Jallib device file 'does' nothing (does not change any
register by itself), the user program may suppose it gets the PIC in the
state as after a reset.
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.
