Author |
Message |
Topic: Undefined identifier: rs232_errors |
object01
Replies: 5
Views: 11715
|
Forum: General CCS C Discussion Posted: Thu May 12, 2005 2:23 pm Subject: Undefined identifier: rs232_errors |
Wasn't all of this gone over back in March ?
http://www.ccsinfo.com/forum/viewtopic.php?t=22342&highlight=rs232errors
In fact, this was your thread.
Different chip, different month, differ ... |
Topic: Undefined identifier: rs232_errors |
object01
Replies: 5
Views: 11715
|
Forum: General CCS C Discussion Posted: Thu May 12, 2005 2:11 pm Subject: Undefined identifier: rs232_errors |
Can anyone get this code to compile in 3.224 without the compiler complaining that rs232_errors doesn't exist?
#include <18F4620.h>
#device ICD=TRUE
#fuses intrc,nowdt,nobrownout,nolvp,nopr ... |
Topic: Instruction 0x0000 jumps to wrong address |
object01
Replies: 6
Views: 9240
|
Forum: General CCS C Discussion Posted: Thu May 12, 2005 1:38 pm Subject: Instruction 0x0000 jumps to wrong address |
Talked with Kampurath at CCS and he found a workaround for the jump problem. He had me alter the ICD style for the 18Fx620 using the device editor, such that the forced fuses included NOSTVREN instea ... |
Topic: Instruction 0x0000 jumps to wrong address |
object01
Replies: 6
Views: 9240
|
Forum: General CCS C Discussion Posted: Wed May 11, 2005 6:02 pm Subject: Instruction 0x0000 jumps to wrong address |
1) It does point to main starting, but the actual jump moves the program counter to 002A, not 0068.
2) The compiler implicitly adds the necessary ICD code when we enter debug mode. I generally kee ... |
Topic: Instruction 0x0000 jumps to wrong address |
object01
Replies: 6
Views: 9240
|
Forum: General CCS C Discussion Posted: Wed May 11, 2005 12:49 pm Subject: Instruction 0x0000 jumps to wrong address |
When I debug the following program (PIC-C v3.223, ICD FW v1.39), and reset while looking at the listing, then step, I'm observing that the first instruction, GOTO 0068, does not actually go to 0068. ... |
Topic: MOVLF xC5 putting to wrong xC5 |
object01
Replies: 4
Views: 13662
|
Forum: General CCS C Discussion Posted: Tue May 10, 2005 7:48 pm Subject: MOVLF xC5 putting to wrong xC5 |
It's still tough to get this into a smaller, compilable program, but I found a workaround. The variables stopPoint and i are both unsigned int8.
Here's the listing of the erroneous section:
..... ... |
Topic: MOVLF xC5 putting to wrong xC5 |
object01
Replies: 4
Views: 13662
|
Forum: General CCS C Discussion Posted: Tue May 10, 2005 5:02 pm Subject: MOVLF xC5 putting to wrong xC5 |
Post a program that we can compile. Post your compiler version.
I knew you were gonna say that.
I can't reproduce the problem yet using anything other than the ginormous program in question. ... |
Topic: MOVLF xC5 putting to wrong xC5 |
object01
Replies: 4
Views: 13662
|
Forum: General CCS C Discussion Posted: Tue May 10, 2005 4:57 pm Subject: MOVLF xC5 putting to wrong xC5 |
(ok, so I got the subject line wrong...) |
Topic: MOVLF xC5 putting to wrong xC5 |
object01
Replies: 4
Views: 13662
|
Forum: General CCS C Discussion Posted: Tue May 10, 2005 4:49 pm Subject: MOVLF xC5 putting to wrong xC5 |
This line,parserState = opcode; compiles to 3D64: MOVLW 04
3D66: MOVWF xC5.
(opcode is the 5th member of an enum)
The symbol map shows parserState at location 0x0C5. But instead, 0 ... |
Topic: #serialize (oh not again) |
object01
Replies: 2
Views: 5265
|
Forum: General CCS C Discussion Posted: Tue Apr 19, 2005 3:32 pm Subject: #serialize (oh not again) |
The answer!
From CCS Tech Support:
The problem is the compiler expects the ID in a #serialize to be all upper case if #case is active. This will be fixed in the next release. Meanwhile make the ... |
Topic: #serialize (oh not again) |
object01
Replies: 2
Views: 5265
|
Forum: General CCS C Discussion Posted: Tue Apr 19, 2005 3:31 pm Subject: #serialize (oh not again) |
The answer!
From CCS Tech Support:
The problem is the compiler expects the ID in a #serialize to be all upper case if #case is active. This will be fixed in the next release. Meanwhile make the ... |
Topic: #serialize (oh not again) |
object01
Replies: 2
Views: 5265
|
Forum: General CCS C Discussion Posted: Wed Mar 30, 2005 3:53 pm Subject: #serialize (oh not again) |
I've decided to give #serialize another try, but still can't get it to work. Wrote my code as follows:
unsigned int32 getUnitID() {
const unsigned int32 serialNumA = 200;
#ser ... |
Topic: Warning 202: "Variable never used rs232_errors" |
object01
Replies: 8
Views: 21412
|
Forum: General CCS C Discussion Posted: Mon Mar 28, 2005 9:38 am Subject: Warning 202: "Variable never used rs232_errors" |
Not sure what you mean by a "block". The placement shown below
stops the warnings.
#include <16F877.h>
#fuses XT, NOWDT, NOPROTECT, BROWNOUT, PUT, NOLVP
#use delay(clock = 4000000& ... |
Topic: Warning 202: "Variable never used rs232_errors" |
object01
Replies: 8
Views: 21412
|
Forum: General CCS C Discussion Posted: Mon Mar 28, 2005 8:26 am Subject: Warning 202: "Variable never used rs232_errors" |
Not sure what you mean by a "block". The placement shown below
stops the warnings.
"Block" = the habit of including #ignore_warnings NONE after any #ignore_warnings x directive.
*smack* I' ... |
Topic: Warning 202: "Variable never used rs232_errors" |
object01
Replies: 8
Views: 21412
|
Forum: General CCS C Discussion Posted: Sun Mar 27, 2005 1:55 am Subject: Warning 202: "Variable never used rs232_errors" |
Is there a way to ignore this warning? Wrapping my #use rs232 declarations in an #ignore_warnings 202 block doesn't seem to do the trick. I keep "errors" in those declarations because it's my unders ... |
|