Search found 9 matches

I get a compile error when trying to use INTRC_IO with a PIC18F26J50 / PIC18F25J50 / PIC18F24J50. The fuse is not recognized by the compiler.

In the PIC18F26J50 header file, "INTRC" appe ...

This solution you suggest does indeed fix the test prorgram.[quote]
#build(interrupt=0x028)
#org 0x0020, 0x002f {}
[/quote]

However the actual program has inte ...

I see what you're talking about. Adding the #ROM indeed changes the .HEX file, but not the .LST file. Unfortunately, the compiler version I'm using (3.141) doesn't actually reserve the memory declar ...

Inserting the "#rom()" actually makes no difference in the LST file. The compiler seems to ignore this and still puts an instruction at location zero.

Looking at low memory, adding the #build() co ...

Sorry about that -- the links should work now.

I agree this is a bizzare problem. We also have hundreds of this exact PIC in the field with PLL enabled with zero problems. I thought I had pretty ...

I posted some additional information, .C .LST and .HEX files with and without this "#build()" fix. This post includes crystal specs, rev, version, etc.

http://web.media.mit.edu/~benres/picbug/
...

Thanks for the response, but I'm having a different (and far more evil) problem. Yes, enabling and disabling the PLL doesn't take effect until the chip is power cycled. However, once the chip has be ...

I just ran into this problem using the PLL mode with an 18F242. About 30% of the time, the processor doesn't start. I have good powerup time, and the 10MHz XTal is about 4.5v p-p (Vcc is 5 volts). ...

We have the 3.137 version of the compiler and I'm curious to see what the 3.202 version does to our code.

Is there an easy way to switch between multiple compiler versions, or do we need to de-inst ...