If the calibration data is still intact, you try to add
Before ANSEL=0Code:DEFINE OSCCAL_1K 1
If the calibration data is still intact, you try to add
Before ANSEL=0Code:DEFINE OSCCAL_1K 1
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi,
thanks for the replys, I thought it might be something to do with the internal osc. Tried the program code on a 16f819 worked fine.
So i got a brand new 12f675, checked the osc cal and band gap values, loaded the code and rechecked them. I did this because I have had other timing issues with these 12f675's. Some of which were down to me I think.
I like to stick with an 8 pin chip because I aim to fit the board into a keyfob, so space is tight.
First I will try the soloutions you have offered.
Thanks for your time.
Nick
Hi,
Thanks for the info regarding the DEFINE OSCCAL_1K 1
Adding that to the program code has solved my little problem.
I have found referances about this define in the pbp manual, for some reason I thought that DEFINE OSC 4mhz was correct.
I assume that DEFINE OSCCAL_1K 1 means
org 0
movwf OSCCAL
Thanks for your time........Nick
Bookmarks