Search found 41 matches

The things for which I find the list file to be most useful are:

- Optimizing code produced by the compiler.
- Divining the nature of compiler bugs.

On the first one, consider the following two ...

I see that you are using the flag "rx_flag" to indicate when a character is ready.

In your main() function, you haven't included the reset of that flag within the conditional statement so ...

The first time I used a 32.768 kHz crystal in an RTCC application (it wasn't even on a PIC) I had a problem with the crystal being too slow by 15-20 seconds a day, but I'd neglected to pay attention t ...

Very good point about the organization of the code - and were it organized that way, that would explain it: Although *I* know that those RAM locations aren't going to conflict if re-used in another m ...

The math used in the DSP to just shifts and adds, so the 18F part really would not be of much benefit from the standpoint of increased execution time: More RAM would be of help, of course, but one of ...

I have a head-scratcher:

Using a 16F1847 along with the current V5 compiler, I have a project that does two separate things:

- Tone generation, etc.
- DSP filtering of audio.

When operating, ...

I've implemented "software" UARTs inside ISRs, but it takes a bit of planning before-hand.

If at all possible, set the ISR rate to be an integer multiple of the baud rate of the UART. If ...

I'm happy to report that as of 5.013, the bug where interrupts are disabled when sprintf() is used has been fixed.

I didn't test it extensively with all possible combinations, but I do know that va ...

I reported this problem to CCS and this is what they sent back:

"The problem you reported has been fixed and will be in the next compiler release. "

As soon as >5.012 appears, I'll ...

Since the compiler with which this occurred (Version 5.012) *is* the newest version of the compiler as of today's date, I guess that I will report this "feature" and wait, doing work-arounds ...

I recently updated from the V3/V4 compiler to V5.012 and was surprised when some code that I'd compiled for the PIC16F88 with the older versions blew up.

Tracking it down, I figured out that " ...

I have a hair-pulling problem:

I'm using a PIC18F2620 with both PWM's enabled in the standard (not "enhanced" mode and I have the timing/divisors set up so that all 10 bits of resolution ...

I see the problem: You *can't* turn on OSCCON bits 0 or 1 and expect it to work. In other words, "Primary Oscillator" should be enabled, and NOT "Internal Oscillator Block."

S ...

Ok, I've pulled out my hair for long enough.

I've searched the forms and can find nothing obvious, but I've not been able to figure out why I can't get the '4620 to run at 32 MHz using the internal ...

>... I am indeed using a PTC thermistor,

That's interesting. It must be a special-purpose PTC: A lot of PTC thermistors have rather nasty curves that don't nicely follow formulas (possibly exp ...