Jan_Erik,
     I'm not going to worry about the individual bits at this point. It=20
also sounds like the compiler will actually generate better code if I=20
use the whole register. I am also using the free version and my=20
understanding is that the paid for pro version generates better code. At=20
this point I am using 8.7% of the program space and 21.1% of the data=20
space. So I still have plenty of room left.
     I have my 684 prototype board built. The program runs. The 684 chip=20
I have won't run at 20MHz so I changed the code to use 4MHz. No, I can't=20
read the printing on the chip. So I can't tell if it is a 4 or 20MHz=20
unit.     I was trying to figure out how to use binary. I was trying to=20
use b'xxxxxxxx' were x are the individual bits. You showed me that the=20
format is 0bxxxxxxxx. I prefer binary over either hexadecimal or decimal=20
for setting the bits on a port.
     David's hint about using the CTRL+Space for a drop down list is great.
     Why is there a setting for the starting point of the counter in=20
both the Interrupt handler function and in the InitTimer function? This=20
code came from the MicroElektronika timer calculator. I just used the=20
code and changed a few variable descriptors that weren't compatible with=20
the XC8 compiler.
Thanks,
rich!

On 7/23/2014 4:37 AM, Jan-Erik Soderholm wrote:
> James Cameron wrote 2014-07-23 04:20:
>
>>> T1CONbits.T1GINC  =3D 0;
>>> T1CONbits.TMR1GE  =3D 0;
>>> T1CONbits.T1CKPS  =3D 0b11;
>>> T1CONbits.T1OSCEN =3D 0;
>>> T1CONbits.T1SYNC  =3D 0;
>>> T1CONbits.TMR1CS  =3D 0;
>>> T1CONbits.TMR1ON  =3D 1;
>> Yes, I guessed that both were possible, and for multiple bit fields
>> there is some advantage, but apart from that is there any other reason
>> for using the longer form over the shorter form?
>>
>

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.