Hi Matt,
On 07/26/11 06:58 am, mattschinkel wrote:
The problem is caused by a wrong fuse_dev CPUDIV setting. Somewhere between
jalpack 0.6 and 0.7 the meaning of the keywords of this fuse_def has
changed.
Never mind... I just read the other topic/issue. I guess microchip
does change these things? :(
For general understanding: I often curse Microchip for changing things
in MPLAB from version to version because of the consequences for my
interpretation of the MPLAB .dev files. And it is not always ovbious if
the change is a correction of a previous error or a simple improvement
(esp. in the case of description fields).
For the fuse_def definiton in the Jallib device files the dev2jal script
has to interpret a description (which is frequently a whole sentence!)
in the MPLAB .dev file and 'translate' it to a single keyword. This is a
tricky operation! Even a tiny change of the description (and Microchip
changes these descriptions often) may invalidate my interpretation. What
makes it even more tricky is that frequently the descriptions of the
same fuse are different for different groups of PICs.
Most of the time I catch these changes, certainly when there are few.
But when there are many - even tiny - changes I may overlook one (or
more). I think this was the case with CPUDIV.
Since some time I copy the original description of fuse settings in
MPLAB as comment in the Jallib device files. This is not meant as
replacement for the datasheet, but only as reminder for those who really
read the datasheet. My main purpose was however to help me (us) with
catching errors.
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.
