Hi Michael,

Thanks for that very welcome injection of sanity, Michael. Yes, it appears that I'm most likely going to end up with an un-Godly pickle if I persist in entertaining such unconventional development strategies.

Rather than trying to create the final word in (incomprehensible) self-configuring source code collections, the more sensible approach may be to continue as I had previously always intended, and as you have suggested that I now consider doing. That was to code unsophisticated, readily understandable component modules with minimal interdependence (linkage?), and then to provide the end user with clear, detailed instructions on each individual component and sub-component's configuration requirements and use.

Declaring SFRs within my code module's headers is also starting to lose it's immediate appeal. Perhaps I ought instead reserve my module's X2 CPU clock mode functionality for circumstances in which the generic, non-clock control register inclusive register declaration header file has been replaced. There's probably a tricky pre-compiler directive sequence that will achieve this, but a more sensible approach might simply involve appropriate documentation.

I've blabbed-on too much. I should be quiet for a bit now I think.

Regards,
Murray R. Van Luyn.