changing osc on the fly

[rmteo]

...Maybe not at 2 volts, but 2.5 is doable. Using the PICKIT2 for a PS, only goes down to 2.5. So I can not verify the 2 volts right now...

It is poor engineering practice to operate a device outside of the manufacturer's specs - take a look at the graph above where it shows that the minimum voltage is 4.2V for frequencies >25Mhz.

[mackrackit]

It is poor engineering practice to operate a device outside of the manufacturer's specs - take a look at the graph above where it shows that the minimum voltage is 4.2V for frequencies >25Mhz.

But I am not an engineer

I look at the graph as showing the primary frequency.
I have not built anything to run on less than 3.3 volts. I do a lot at 3.3 though. Have for some time. Makes working with SD cards and other low power things much easier. One power supply.

[rmteo]

But I am not an engineer

I look at the graph as showing the primary frequency.

Makes sense then.

[Charles Linquis]

If you need to run at 4Mhz on the internal OSC, put this in your code.

ASM
       movlw 0x62                              ; %0110 0010  = 4 Mhz, internal osc block
       movwf OSCCON
       movlw 0x80                              ; %1000 0000  = PLL disabled
       movwf OSCTUNE
ENDASM

I have a development board that runs at 40Mhz on a 10Mhz XTAL + PLL, but sometimes I need to slow things down to 4Mhz and run on the internal oscillator to see how they will run on "little" parts. This code does the trick.

[Art]

I was thinking of a routine that could detect the clock speed the pic is running at
so that then the pic program could adjust serial speed, etc accordingly.

Make a delay loop in picbasic and count the number of ticks a hardware timer
makes during the delay loop.. and then the hardware timer value will be
different for different clock speeds.

[rmteo]

Wouldn't a delay need to know clock speed to work correctly?

[Dave]

Art, What would you use as a reference in that situation?

Dave Purola,
N8NTA

[Art]

Wouldn't a delay need to know clock speed to work correctly?

No, because you use a timer based on RC clock, which is always the same,
but the delay is dependent on osc speed.

So, start timer, execute delay, read timer.

The fact that the delay varies is what I'm counting on.