Hi Seb,
It might better to specify 'pragma target iol1way disabled'
(in case this sample will be used as base for a program with more
dynamic changes; do not rely on default fuse settings)
by default, 1way is enabled. Do you mean you want to specify it as
disabled ?
I would not be so sure that IOL1WAY is enabled by default!
The device files contain config bits settings which (in general) are not
necessarily the factory or datasheet defaults. The Jallib defaults
(specified in 'devicespecific.json') were originally the datasheet
settings, but later modified to become more commonly usable. This was
done by analysing the datasheet tables for each individual PIC, since
even PICs with the same datasheet have frequently different settings. I
have tried to automate this several times, but I didn't succeed (yet).
I'm afraid I saved myself a lot of time lately: when I add a new PIC to
devicespecific.json I copy a setting from a similar, existing PIC and
only check it with the datasheet incidentally. This is almost certainly
a source of 'wrong' defaults!
I would appreciate suggestions and offers to help with this task!
Anyway, indeed in samples I think it is good to set 'pragma target
IOL1WAY disabled'
I think I'll have one procedure, as in your lib & Vasile's example:
pps_lock(true|false).
Good! This is also in line with the rtcc_hw library!
One remark: in Vasile's code the 'movlb 0x0E' is not in the same place
as in the datasheet code. Maybe this doesn't matter in practice, but to
follow the datasheet as close as possible I have put an 'asm bank ....'
in both the 'if' and 'else' branch of the corresponding procedure in
rtcc_hw libary.
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.
