Hi Rob, If I understand what you're saying, you basically agree that the 'right' place for such aliasing is in the 18F device files, to provide a sort of 'legacy' MSSP mode.
I don't think I want to get into such deep waters just yet. I suspect if I procrastinate, you won't be able to resist doing it yourself. :-) William On Sep 2, 4:38 am, Rob Hamerling <[email protected]> wrote: > Hi William, > > William wrote: > > The more I think about it, perhaps the best place to truly 'resolve' > > the issues is in the device files themselves -- there is already A/D > > stuff and PORT I/O stuff, why not some aliases to help with MSSP > > issues? > > > Time to sleep on that one... > > In my view the aliases for registers as done in some libraries are sort > of temporary fixes (or 'tricks'). For example in pwm_hardware.jal the > ECCPxCON registers are aliased as CCPxCON. So Extended CCP modules are > handled as classic CCP modules and thus those libraries support only a > subset of the possibilities of the extended CCP modules. That is fine > for 'simple' PWM work, and good that simple PWM can be used with > extended CCP modules. > However these libs do not support the 'extended' PWM facilities. > Eventually an epwm_hardware library might be needed. > > Now back to MSSP: You'll have to make a design for the restructuring of > device files w.r.t. the MSSP modules (register names and/or aliases). > That may cause you headaches, but also bring you everlasting fame! > Looking forward! > > 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 -~----------~----~----~----~------~----~------~--~---
