Comment #4 on issue 194 by [email protected]: Device files with MPLAB-X
http://code.google.com/p/jallib/issues/detail?id=194
Well, we may assume that the MCHP generates the .dev and .inc files by some
parsing of the .pic file.
The .pic file contains all the information, the MCHP parser may have
glitches so the .dev file contains some surprises, the .inc and .dev files
are sometimes not coherent to each other.
If you parse the .pic your way, you may correct that or introduce your own
inconsistencies, but generally speaking the .dev problems may be avoided by
cross comparing some data that are in the .pic and not in the .dev (or
differently shown or dispatched between .dev and .inc files).
There is still a few name conflicts between some assembler reserved words,
register names, register field names and pin names, you still have to use
your own logic to solve that...
For the next version of PMP I definitely adopted the .pic parsing way.
Since PMP is still using an external assembler, it generates the
processor's .inc file automatically to be consistent with the .pic parsing
and the MCHP's .inc files are no more used.
Regards,
Philippe.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
