Hi guys,
Just for the record... Since I began with my dev2jal script I have been struggling with converting the configuration bits descriptions (literally!) in the MPLAB .dev files to 'reasonable' keywords for the pragma fuse_defs. Frequently configuration bits with exactly the same meaning have different descriptions, OSC being the worst case. So far I didn't see a systematical approach to tackle the 'normalization' of fuse_def declarations, but I think I saw a light (or led ;-) ) which could be the end of the tunnel. I wrote a script to collect from all PIC1xxxxx.dev files in MPLAB all combinations of config-bit names and their possible meanings (descriptions): in total about 17000. After a sort I counted about 900 different combinations. Some combinations occur many times (more than 100), others are unique and many in between. Many combinations are already handled by dev2jal script, but now I have a complete picture and know also the 'exceptional' combinations. A recent change in the dev2jal script makes it relatively easy to add new combinations, and I will gradually add the necessary routines to handle these. So beware that many fuse_defs will change in the near future. This will have its effect on compilability of samples and other existing programs, especially those who contain more_than_100_characters_long_and_not_easy_to_remember keywords! The lucky ones are those who work with a bootloader and don't have to specify fuse settings. Regards, Rob. -- Rob Hamerling, Vianen, NL (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 -~----------~----~----~----~------~----~------~--~---
