Author |
Message |
Topic: Wizzard Error? Undefined Identifiers WDT_ON & WDT_DIV_16 |
SherpaDoug
Replies: 2
Views: 9251
|
Forum: General CCS C Discussion Posted: Tue Feb 26, 2019 10:06 am Subject: Wizzard Error? Undefined Identifiers WDT_ON & WDT_DIV_16 |
Please pardon a very rusty PIC CCS programmer. I am trying to write new code for an old product using PIC16C58A chips. My 20 year old code doesn't compile under (PCWH) PCB 5.058 so I am trying to st ... |
Topic: #ID generates compiler internal error |
SherpaDoug
Replies: 3
Views: 12578
|
Forum: General CCS C Discussion Posted: Wed Oct 10, 2018 1:46 pm Subject: #ID generates compiler internal error |
It seems to be specifically the spaces after the digits and before the commas that are the problem. |
Topic: #ID generates compiler internal error |
SherpaDoug
Replies: 3
Views: 12578
|
Forum: General CCS C Discussion Posted: Wed Oct 10, 2018 10:56 am Subject: #ID generates compiler internal error |
Does anyone use the #ID compiler directive?
I am trying to resurrect a system which compiled and ran fine under PCB version 2.213 around 1998. It uses the #ID directive to put the serial number in ... |
Topic: Ancient vs current CCS struct differences? |
SherpaDoug
Replies: 8
Views: 18540
|
Forum: General CCS C Discussion Posted: Mon Sep 24, 2018 9:00 pm Subject: Ancient vs current CCS struct differences? |
For future readers, here is a fully compilable example of how to use a struct in a union. #include <16F877.h>
#fuses HS,NOWDT,NOPROTECT,NOLVP
#use delay(clock=10000000)
#use rs232( ... |
Topic: Ancient vs current CCS struct differences? |
SherpaDoug
Replies: 8
Views: 18540
|
Forum: General CCS C Discussion Posted: Sat Sep 22, 2018 1:18 pm Subject: Ancient vs current CCS struct differences? |
Ttelmah, would this be proper by-the-book and easily understood C syntax?
struct {
short LEDBlink; /* 1 enables blinking of LEDs */
short Redbit; /* 1 turns on Red LED ... |
Topic: Ancient vs current CCS struct differences? |
SherpaDoug
Replies: 8
Views: 18540
|
Forum: General CCS C Discussion Posted: Tue Sep 11, 2018 6:43 pm Subject: Ancient vs current CCS struct differences? |
Thanks, that fixed things. But trying to understand the problem, I guess a struct doesn't have a data type unless you force one upon it by casting? I guess the old compiler didn't check and just did ... |
Topic: Ancient vs current CCS struct differences? |
SherpaDoug
Replies: 8
Views: 18540
|
Forum: General CCS C Discussion Posted: Mon Sep 10, 2018 8:25 pm Subject: Ancient vs current CCS struct differences? |
About 1998 I wrote this code which compiled and ran fine under PCB version 2.213.
struct {
short LEDBlink; /* 1 enables blinking of LEDs */
short Redbit; /* 1 turn ... |
Topic: Printing large numbers |
SherpaDoug
Replies: 13
Views: 26047
|
Forum: General CCS C Discussion Posted: Mon Nov 13, 2017 10:30 am Subject: For precision use ints |
I once built a sonar system to measure ship hulls. They wanted the output in decimal meters. But internally the system did the measurement in 24 bit integer tenths of millimeters. Conversion to met ... |
Topic: What is the use of port_x_pullups ( ) |
SherpaDoug
Replies: 8
Views: 24343
|
Forum: General CCS C Discussion Posted: Mon Nov 13, 2017 10:16 am Subject: Also for extreme power saving |
The software controlled pull-ups can also be useful when power savings is extremely important. You can have a pull-up when you need it but shut it off when you don't. |
Topic: What is CCS up to? |
SherpaDoug
Replies: 16
Views: 27649
|
Forum: General CCS C Discussion Posted: Mon May 30, 2016 8:41 pm Subject: What is CCS up to? |
I agree, the manual is where I wish they would put more effort. I imagine it is difficult to keep up with the features of the new chips. But the older features could use more explanation. |
Topic: Function too Large - Main (?) |
SherpaDoug
Replies: 4
Views: 12557
|
Forum: General CCS C Discussion Posted: Tue May 24, 2016 9:33 pm Subject: Function too Large - Main (?) |
With PICs all functions including main() have to fit on a memory page. Several small functions may fit on one page but no function can cross a page boundary. If your chip has 4 ROM pages then no fun ... |
Topic: Suspect errors in PIC12LF1501.h file - how to tell? |
SherpaDoug
Replies: 21
Views: 44216
|
Forum: General CCS C Discussion Posted: Mon May 23, 2016 1:06 pm Subject: Successful test program |
For anyone in the future with similar issues here is my finished test program that exercises Software Serial, DAC and Timer1 on the PIC12LF1501:
//Simple-counter-3 main.c
#include <main.h>
in ... |
Topic: Suspect errors in PIC12LF1501.h file - how to tell? |
SherpaDoug
Replies: 21
Views: 44216
|
Forum: General CCS C Discussion Posted: Mon May 23, 2016 7:51 am Subject: Suspect errors in PIC12LF1501.h file - how to tell? |
Thanks Ttelmah, that makes things much clearer. Is this device database and getenv behavior documented anywhere in the manual or is it just tribal knowledge?
I frequently examine the .sym and .lst ... |
Topic: Suspect errors in PIC12LF1501.h file - how to tell? |
SherpaDoug
Replies: 21
Views: 44216
|
Forum: General CCS C Discussion Posted: Sun May 22, 2016 3:21 pm Subject: Suspect errors in PIC12LF1501.h file - how to tell? |
Ttelmah: I saw your
#bit WPUEN=getenv("BIT:WPUEN")
but that left me puzzled. I see that it works but I don't know why. Where does getenv() get its information from? Since I am alre ... |
Topic: Suspect errors in PIC12LF1501.h file - how to tell? |
SherpaDoug
Replies: 21
Views: 44216
|
Forum: General CCS C Discussion Posted: Sun May 22, 2016 12:52 pm Subject: Suspect errors in PIC12LF1501.h file - how to tell? |
If I was doing this, I'd probably bend out the RA2 pin on the DIP package
so it's hanging in the air. Then put a scobe probe on it. Just to be sure.
Easy enough to do ... but it didn't help. |
|