Sebastien Lelong wrote:
> This is due to board files defining aliases. I tried to fix them, but
> we have a problem with 16F88. One board "_js" is defines
> pin_ccp1_direction as pin_b3_direction, another board "_sl" defines
> pin_ccp1_direction as pin_b0_direction. This is the CCP1MUX fuse def
> problem we talked about.
> 
> As I suggested, defining two aliases would help:
> 
> pin_ccp1_b0_direction is pin_b0_direction
> pin_ccp1_b3_direction is pin_b3_direction
> 
> (same withou "_direction").
> 
> Since there's no pin_ccp1_direction in this case, this will be added
> in board files: the normalization is done in board file (and any other
> program) not in device files, until we got a clean solution.
> 
> Ex:
> 
> pragma fuse_def CCP1MUX RB0
> pin_ccp1_direction is pin_ccp1_b0_direction
> 
> 
> 
> What's your opinion on this ?

I think providing 2 'qualified' aliases in the device files as per your 
suggestion could lead to a workable situation. However it is somewhat 
difficult in my current script, it would require to 'look ahead' to know 
in advance that functional pins are multiplexed. I understand that some 
sort solution it needed, and I'll think it over.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to