Author |
Message |
Topic: getenv("PROGRAM_MEMORY") |
pirev
Replies: 3
Views: 6174
|
Forum: General CCS C Discussion Posted: Mon Jan 22, 2007 5:19 am Subject: getenv("PROGRAM_MEMORY") |
I found a reason for this, this is a directive #device ICD=TRUE, after removing directive CCS always return right vaue for available program memory. Compiler version is 3.249 |
Topic: getenv("PROGRAM_MEMORY") |
pirev
Replies: 3
Views: 6174
|
Forum: General CCS C Discussion Posted: Sun Jan 21, 2007 3:21 pm Subject: getenv("PROGRAM_MEMORY") |
Why some times (for PIC16F873 processor) CCS C function getenv("PROGRAM_MEMORY") return 4095 words, some times return 4096 words, 4046 words ?
CCS Help say that getenv("PROGRAM_MEMORY& ... |
Topic: Version 4 Comments |
pirev
Replies: 270
Views: 411532
|
Forum: General CCS C Discussion Posted: Fri Dec 22, 2006 5:07 am Subject: 4 is to ugly and and uncomroftable |
Versions 4.xxx are horror IDE, I can't see such IDE from yers They are to ulgy and uncomfortable Why CCS was drop IDE interface from previous versions ? After every switch to another ... |
Topic: Bug in CCS 3.245 for interrupt vectors |
pirev
Replies: 4
Views: 8317
|
Forum: General CCS C Discussion Posted: Mon May 15, 2006 11:30 pm Subject: Bug in CCS 3.245 for interrupt vectors |
Thanks PCM programmer,
Your code is not compilable, as posted. It's missing the declarations
for STATUS, PCLATH, TMR0, etc. Also, the pre-processor statements
for "inline" are missing the "#" ... |
Topic: Bug in CCS 3.245 for interrupt vectors |
pirev
Replies: 4
Views: 8317
|
Forum: General CCS C Discussion Posted: Mon May 15, 2006 4:10 pm Subject: Bug in CCS 3.245 for interrupt vectors |
Thanks Ttelmah,
enable_interrupts(GLOBAL) generate the same code as
INTCON |= 0xC0; in my function InitHardware();
Also I set #OPT 0, but situation are not changed. At address 0x0004 compile ... |
Topic: Bug in CCS 3.245 for interrupt vectors |
pirev
Replies: 4
Views: 8317
|
Forum: General CCS C Discussion Posted: Mon May 15, 2006 1:37 pm Subject: Bug in CCS 3.245 for interrupt vectors |
Hi all,
here is piece from my program:
#include <16f913.h>
#CASE
int8 frtcc, catod, Display, i,
rtcc10ms, rtcc100ms,
rtcc1s, rtcc1m,
iTemp;
char const szLedTable=29;
cha ... |
Topic: Upgrading FROM PIC18F452 to bigger PIC? |
pirev
Replies: 2
Views: 4676
|
Forum: General CCS C Discussion Posted: Sat Nov 12, 2005 10:07 am Subject: Upgrading FROM PIC18F452 to bigger PIC? |
Try with PIC18F4525(48kB) or PIC18F4620(64kB). |
Topic: How to decode device ID returned from ICD-S |
pirev
Replies: 1
Views: 25988
|
Forum: CCS ICD / Mach X / Load-n-Go Posted: Wed Oct 19, 2005 4:59 am Subject: How to decode device ID returned from ICD-S |
I have PIC18F2520 and ICD unit. I'd like to see what is silicon revision of PIC18F2520 from ICD Control Program V2.25/Advanced/Device ID. ICD returns: "PIC18 Device ID: 1101". I see from MicroChip doc ... |
Topic: miror byte |
pirev
Replies: 3
Views: 6515
|
Forum: General CCS C Discussion Posted: Sat Oct 15, 2005 12:54 pm Subject: miror byte |
/*
Mirror byte for PIC12/14/16
For PIC18 will not work
*/
#bit _C=STATUS.0
#define _RLF_F(data) #asm rlf data,F #endasm
#define _RRF_F(data) #asm rrf data,F #endasm
int8 Mi ... |
Topic: Microchip i2c EEProm Chips |
pirev
Replies: 6
Views: 71585
|
Forum: Code Library Posted: Tue Oct 11, 2005 7:25 am Subject: Microchip i2c EEProm Chips |
Here is my software I2C implementation:
//
// I2C Master interface for PIC16/PIC18, software implementation
//
// Written by Svetoslav Pirev, Bulgaria, Plovdiv, [email protected], ICQ: 321848589
... |
Topic: Microchip i2c EEProm Chips |
pirev
Replies: 6
Views: 71585
|
Forum: Code Library Posted: Tue Oct 11, 2005 7:25 am Subject: Microchip i2c EEProm Chips |
Hi, I thing that WriteExtMem() function will not work properly in all of situations. Here is a quote from MicroChip document DS21203M.PDF ( 24xx256 ) , page 9 :
Note: Page write operations are limi ... |
Topic: Not enough ram for all variables???? |
pirev
Replies: 4
Views: 5805
|
Forum: General CCS C Discussion Posted: Thu Oct 06, 2005 8:49 am Subject: Not enough ram for all variables???? |
Hi, problem was in directive #DEVICE *=8, because my source is ported from PIC16F873 to PIC18F252 and I was forget to remove this directive. |
Topic: Not enough ram for all variables???? |
pirev
Replies: 4
Views: 5805
|
Forum: General CCS C Discussion Posted: Wed Oct 05, 2005 4:52 am Subject: Not enough ram for all variables???? |
Hi all,
I have a problem with "Not enough RAM for all variables",
processor is PIC18F252 with 1536 byte RAM, but the complier counting only 256 bytes. Here is my header of listing:
Filename: C:my ... |
Topic: recover ICD-U40 firmware |
pirev
Replies: 16
Views: 113078
|
Forum: CCS ICD / Mach X / Load-n-Go Posted: Wed Sep 28, 2005 3:34 pm Subject: recover ICD-U40 firmware |
I have a home maded ICD-S40 and work fine. But when I try to update firmware with icd.exe, failed with message:"Cannot start firmware reload: Did not ack message 31".
I am removing PIC18F252 from ICD ... |
Topic: Code to store tables in code memory |
pirev
Replies: 1
Views: 34472
|
Forum: Code Library Posted: Fri Jun 24, 2005 5:48 pm Subject: Code to store tables in code memory |
// For PIC16F8xx
#bit _C=STATUS.0
#bit GIE=INTCON.7
#bit RD=EECON1.0
#bit WR=EECON1.1
#bit WREN=EECON1.2
#bit EEPGD=EECON1.7
#define _NOP() #asm nop #endasm
void WrPrgMem ... |
|