Hi Albert,

[email protected] wrote:

> For the RC5 stuff I was attempting to use the timer0_isr_interval
> jallib library, but I ran in the following issue (using a 18f device):
> 
> The INTCON_T0IE var is not recognized in the 18f device file, just
> took a quick look in a 16f628 device file and compared it with the
> 18f2450 device file and noticed the following
> 
> 16f628 device file
> 
> var volatile bit   INTCON_TMR0IE        at INTCON : 5
> var volatile bit   INTCON_T0IE          at INTCON : 5
> 
> 
> 18F device file
> var volatile bit    INTCON_TMR0IE        shared at INTCON : 5
> var volatile bit    REG_T0IE             shared at INTCON : 5
> 
> 
> So my question, is the REG_T0IE var wrongly declared in the 18f device
> (s) file or should the timer lib use INTCON_TMR0IE instead of file
> INTCON_T0IE? This is also applicable for more variables in the device
> file.

You hit bug (typo) in my dev2jal script, REG_T0IE should have been 
INTCON_T0IE.  And not only INTCON_T0IE is wrongly declared, also 
INTCON_T0IF for the 18Fs. Will be fixed ASAP!

FYI: When I started with the development of the Dev2Jal script to 
generate device files I discovered that T0IE was used in one and TMR0IE 
in another existing library. So I decided to declare both names to be 
able to use all existing libraries (that was before Jallib time!).
When I look in the .dev files of MPLAB 8.20 now I see Microchip also 
uses this kind of aliasing. It seems to me that TMR0IE and TMR0IF are 
the primary names and T0IE and T0IF the aliases. So I would like suggest 
to use TMR0IE and TMR0IF in Jallib libraries. I'll remove the names T0IE 
and T0IF when the timer0_isr_interval library has changed (it is 
currently the only lib using T0IE and t0IF).

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