10F222 no response?

[Acetronics2]

Oooops, my fault ... wrong chip selected

this one looks to work fine...

'   set parameters
'
ADCON0=0 'all digital I/O
TRISIO=0 'all outputs (GPIO.3 is input only so it's ignored)
DEFINE OSC 8
DEFINE OSCCAL_1K 1


'*************************************
'     variables and constants
'
tempvar var byte
'***********************************
'    Other housekeeping
'peekcode $1FF, tempvar 'OSCCAL calibration value
'POKE $05, tempvar      'OSCCAL register location


'**************************************************************
'     begin program


GPIO.0=0


loophere:
GPIO.0=1
pause 500
GPIO.0=0
pause 500


goto loophere


end

But you should use PEEKCODE along with POKECODE ... but POKECODE needs a CONSTANT to be stored !

[picster]

Oooops, my fault ... wrong chip selected

this one looks to work fine...

'   set parameters
'
ADCON0=0 'all digital I/O
TRISIO=0 'all outputs (GPIO.3 is input only so it's ignored)
DEFINE OSC 8
DEFINE OSCCAL_1K 1


'*************************************
'     variables and constants
'
tempvar var byte
'***********************************
'    Other housekeeping
'peekcode $1FF, tempvar 'OSCCAL calibration value
'POKE $05, tempvar      'OSCCAL register location


'**************************************************************
'     begin program


GPIO.0=0


loophere:
GPIO.0=1
pause 500
GPIO.0=0
pause 500


goto loophere


end

But you should use PEEKCODE along with POKECODE ...

I'm not writing to CODE area though, it's writing to the OSCCAL register, location $05. Am I wrong in thinking this should do it? It didn't recognize OSCCAL and threw an error when I tried writing it to the register directly using that naming convention.

[HenrikOlsson]

As far as I know OSCCAL the thing is only for calibrating/adjusting/tweaking the actual oscillator frequency so that it's within specification. It should not be needed to get the chip running and I don't think it relates to your problem.

With that said

peekcode $1FF, tempvar
OSCCAL = tempvar

Or perhaps even

PEEKCODE $1FF, OSCCAL

Should do it. But again, I'd remove it from the code until you get a blinky running.

[picster]

As far as I know OSCCAL the thing is only for calibrating/adjusting/tweaking the actual oscillator frequency so that it's within specification. It should not be needed to get the chip running and I don't think it relates to your problem.

With that said

peekcode $1FF, tempvar
OSCCAL = tempvar

Or perhaps even

PEEKCODE $1FF, OSCCAL

Should do it. But again, I'd remove it from the code until you get a blinky running.

Thanks - it's setting OSCCON that's the issue apparently. If I don't bother, it works fine. Anything else, nope. It does NOT like OSCCAL being mentioned. The PEEKCODE $1FF, OSCCAL compiles, but has the same "he's dead, Jim" result.

However, having said that, Acetronics2 used "DEFINE OSCCAL_1K 1", which I can only assume grabs the value for OSCCON from the last code address on a 1K pic and uses it in a snippet of code to drop the value into its rightful register. In this case, it would wrap-around while reading from $3FF (the referenced 1k mark) since there's only 512bytes, but it should still result in the same thing happening.

Thanks guys, for the input - blinky is blinking and I'm away to the races. I would NOT have thought that a poke to the OSCCAL would lock things up, regardless of the value written to it, and the fact that it's not recognized as a register is a head-scratcher.