Strange Behaviour - Simple code+DT_INT+16F676

[financecatalyst]

Thanks for the help.

Interesting software, is this simulation software available to buy anywhere?

You mentioned

DEFINE OSCCAL_1K 1
Assuming the chip still has it's calibration value

I use MPLAB wit PBP, could you advise me what settings are required in the software(MPLAB) so it does not delete this value in the PIC please or guide me to any article explaining such detail. Thanks

[Darrel Taylor]

The simulator is Proteus.
http://www.labcenter.co.uk/index.cfm

And whether it keeps the calibration intact or not depends on the Programmer.
PBP, MCS or MPLAB cannot control that.

Both the PICkit and meLabs programmers will retain the OSCCAL values, but it does it by re-writing the value after erasing.
If a program cycle fails after erasing, the value can still be lost.

The PICkit software allows you to recreate an OSCCAL value if lost.
(I've never tried it though)
<br>

[financecatalyst]

Hello Darrel, I tried adding "DEFINE OSCCAL_1K 1" once above the @_Config....statement and once below it, both cases my PIC went dead. Is it that any other statement goes along with this?

[financecatalyst]

I tried whole day today to make this code work via my PC but unfortunately it didn't worked. The serin command is not working at all. I tried using MAX232 and sent data via PC after setting correct baud rate and other settings, but no results at all.

The interrupt and whatever is in ISR, is working fine. Though the weak internal pullup for PortA.0 & 1 didn't worked (I wonder why), but I managed with external pullups for them.


Sending o9* via my PC does not put pin5 high. I tried it nearly million times today.
Can oscillator be the culprit?

As explained in the above post, my PIC went dead when I tried using DEFINE OSCCAL_1K 1. So I removed that statement and kept trying but

I really need some help to make it work with Serin command.

[Darrel Taylor]

Hello Darrel, I tried adding "DEFINE OSCCAL_1K 1" once above the @_Config....statement and once below it, both cases my PIC went dead. Is it that any other statement goes along with this?

That means the OSCCAL value is gone.
Without the calibration's RETLW, using OSCCAL_1K creates an infinite loop.

And without the calibration, SERIN has a snowball's chance ...

You could try random OSCCAL values, you might get lucky.
Or, stick a crystal or resonator on it, and it should be able to SERIN.
<br>

[financecatalyst]

Hi, I tried it with another PIC with the define statement on top of the code. It worked fine. I can't use external resonator, as I am using those pins.

How do I know which PICs need this DEFINE statement and which don't?
I am trying to serout with 12F635 & serin at 16F676. It is still giving problems, does 635 also needs some kind of calibration? Thanks

[Darrel Taylor]

How do I know which PICs need this DEFINE statement and which don't?

The same way you know about all the other things the chip does ... the Datasheet. (Oscillator section)
Only the really OLD chips need OSCCAL calibration.

I am trying to serout with 12F635 & serin at 16F676. It is still giving problems, does 635 also needs some kind of calibration? Thanks

No, the 635 doesn't need an OSCCAL.
It has a precision multi-speed internal oscillator, and you can select the speed with OSCCON. But it defaults to 4Mhz.
It's factory calibrated, and the calibration can not be erased.

The 635 has a comparator that needs to be turned off though.
CMCON0 = 7
<br>