Author |
Message |
Topic: Warning 202: "Variable never used rs232_errors" |
bluetooth
Replies: 8
Views: 21366
|
Forum: General CCS C Discussion Posted: Mon Mar 28, 2005 6:51 pm Subject: Warning 202: "Variable never used rs232_errors" |
And I remembered why a single #ignore_warnings 202 line wasn't acceptable in the first place without an #ignore_warnings NONE; 'cause I want to be notified about all unused variables except rs232_er ... |
Topic: Warning 202: "Variable never used rs232_errors" |
bluetooth
Replies: 8
Views: 21366
|
Forum: General CCS C Discussion Posted: Sun Mar 27, 2005 8:30 am Subject: Warning 202: "Variable never used rs232_errors" |
Mark:
RS232_errors is a variable that holds that USART status.... ERRORS is the directive for the #use RS232 command.... |
Topic: Warning 202: "Variable never used rs232_errors" |
bluetooth
Replies: 8
Views: 21366
|
Forum: General CCS C Discussion Posted: Sun Mar 27, 2005 7:56 am Subject: Warning 202: "Variable never used rs232_errors" |
If removing this annoyance is worth one instruction word, add the following early in your program:
rs232_errors = 0;
This is one of the other ways to make this error go away.... |
Topic: Seeking device suggestion--controller w/ 2 asynch counters |
bluetooth
Replies: 8
Views: 12088
|
Forum: General CCS C Discussion Posted: Sun Mar 27, 2005 12:20 am Subject: Re: Seeking device suggestion--controller w/ 2 asynch counte |
Timer0 prescaler can only be set to Divide by 2 or more so the minimum is
RTCC_DIV_2 i.e. divide by 2
So true about the prescaler.... but RTCC_DIV_1 *is* valid.
But if PSA (T0CON:3) = 1, ... |
Topic: MCP4922 D/A question |
bluetooth
Replies: 2
Views: 6349
|
Forum: General CCS C Discussion Posted: Sat Mar 26, 2005 5:55 pm Subject: MCP4922 D/A question |
This chip is nice and simple, hardly needs a "driver".
All you need to do is:
// SPI MODE 0,0 is set up earlier
DAC_CS = 0; // Drop chip select
spi_write(dac_ms_byte);
spi ... |
Topic: MPLAB gets stuck in printf I want to simulate code |
bluetooth
Replies: 4
Views: 8195
|
Forum: General CCS C Discussion Posted: Sat Mar 26, 2005 1:06 pm Subject: Re: No I can not get to the wile loop after printf w breakpo |
No I can not get to the wile loop after printf with a breakpoint.
To get around this problem, just put a "dummy" instruction after the printf, like maybe
i=0;
you can set your breakpoint ... |
Topic: 18LF452 being reported as 18F452 |
bluetooth
Replies: 9
Views: 13676
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 4:37 pm Subject: 18LF452 being reported as 18F452 |
Will:
If you believe they're all the same, simply buy the cheaper parts. But I'd keep my resume updated if I did that.... |
Topic: 18LF452 being reported as 18F452 |
bluetooth
Replies: 9
Views: 13676
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 10:45 am Subject: 18LF452 being reported as 18F452 |
Microchip's website specifically states that the LF parts are tested to different specs to get lower voltage operation. They also say that the dies between the two are identical - so they *should* pr ... |
Topic: int RC clock good enough for serial comms? |
bluetooth
Replies: 6
Views: 9006
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 10:36 am Subject: int RC clock good enough for serial comms? |
This is where I found it (old data sheet):
DS40300B-page 139
Some of the newer parts have an OSCTUNE capability - these parts have been around for a while - look at some of the newer ones. Th ... |
Topic: int RC clock good enough for serial comms? |
bluetooth
Replies: 6
Views: 9006
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 9:45 am Subject: int RC clock good enough for serial comms? |
From the 628 Data Sheet showing the min - nominal - max for INTRC:
4 INTRC Internal Calibrated ER 3.65 4.00 4.28 MHz VDD = 5.0V
For reliable async comms with, for example, 10 bits, you're a ... |
Topic: Work around for work around for FP BUG??? |
bluetooth
Replies: 13
Views: 18003
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 7:59 am Subject: Work around for work around for FP BUG??? |
There, you and I part ways. My philosophy is "get the current code right before you add any new features." - Kyle
There are levels of "right", and as the system gets more complex, you have to star ... |
Topic: #fuses options definitions |
bluetooth
Replies: 10
Views: 19623
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 7:48 am Subject: #fuses options definitions |
These two tools and the device data sheet should make the fuses fairly clear.
Emphasis added - Agreed, read the data sheet over and over and over and over....
Also, with a little time to look ... |
Topic: Work around for work around for FP BUG??? |
bluetooth
Replies: 13
Views: 18003
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 7:34 am Subject: Work around for work around for FP BUG??? |
I was just about to post that when I changed mine to int16's, I got the same "error" - so glad you've got it now.
I agree with the other guys - it would be nice of the float printf were cleaned up ... |
Topic: Work around for work around for FP BUG??? |
bluetooth
Replies: 13
Views: 18003
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 7:03 am Subject: Work around for work around for FP BUG??? |
Kyle:
In your latest code, I see:
///////////// Global Variables /////////////
signed int16 glTemp[tempsensorenumnum];
Is this right? I thought you wanted int32's?
By ... |
Topic: #fuses options definitions |
bluetooth
Replies: 10
Views: 19623
|
Forum: General CCS C Discussion Posted: Fri Mar 25, 2005 5:24 am Subject: #fuses options definitions |
The reason I am "guessing" is that I haven't built a project with the 629.
CCS can call the fuses anything they want, and I would think they used INTRC to maintain consistency with o ... |
|