Author |
Message |
Topic: No code produced for 'write_program_memory' for PIC18F4620. |
brianj
Replies: 7
Views: 14860
|
Forum: General CCS C Discussion Posted: Wed Dec 01, 2004 11:49 am Subject: No code produced for 'write_program_memory' for PIC18F4620. |
Thanks for all the suggestions. I can't get it to produce code with any of the recent versions I've tried. I've just had to write it in assembler, which is annoying. I can understand bugs in functions ... |
Topic: No code produced for 'write_program_memory' for PIC18F4620. |
brianj
Replies: 7
Views: 14860
|
Forum: General CCS C Discussion Posted: Sun Nov 28, 2004 8:30 am Subject: No code produced for 'write_program_memory' for PIC18F4620. |
I'm porting a working application from an 18F452 to an 18F4620. On looking at the .lst file, no code has been produced for 'write_program_memory' - the compiler has just ignored it! There's no code pr ... |
Topic: Array's at FLASH-ROM |
brianj
Replies: 6
Views: 20175
|
Forum: General CCS C Discussion Posted: Sat Oct 11, 2003 9:53 am Subject: Array's at FLASH-ROM |
Sorry, the last post was from me (brianj). I forgot to log in.
Brian |
Topic: Array's at FLASH-ROM |
brianj
Replies: 6
Views: 20175
|
Forum: General CCS C Discussion Posted: Sat Oct 11, 2003 5:46 am Subject: Array's at FLASH-ROM |
You could try the 'volatile' keyword.
volatile const char string[] = "HELLO" ;
x = string [0] ;
I haven't tried it in operation, but I can see from the assembler output that it's passing a pa ... |
Topic: Bug in write_program_memory? |
brianj
Replies: 3
Views: 10211
|
Forum: General CCS C Discussion Posted: Tue Oct 07, 2003 6:38 am Subject: Bug in write_program_memory? |
Will do - I just wanted to see if this was already known. How current is version 3.177d of the compiler?
Brian |
Topic: Bug in write_program_memory? |
brianj
Replies: 3
Views: 10211
|
Forum: General CCS C Discussion Posted: Mon Oct 06, 2003 2:06 pm Subject: Bug in write_program_memory? |
I'm evaluating the CCS C compiler at the moment (v3.177d) with a 16F877. I had a problem using write_program_memory where it seemed to be taking too much time and causing some data corruption.
On ... |
|