What exactly are you using for a clock? Is it running?
What is the speed?
Do you have DEFINE OSC xx in your code?
|
What exactly are you using for a clock? Is it running?
What is the speed?
Do you have DEFINE OSC xx in your code?
Dave
Always wear safety glasses while programming.
|
Once it finally starts does it run correctly?
Dave
Always wear safety glasses while programming.
|
Yes, it does. Regarding the EC settings, I tried using "_OSC_EC_1H", and did verify that I was getting 5 MHz (1/4 freq), out on A6. I'll be glad when this "CONFIG WIZARD" is working.
|
I didn't see your other questions... I'm using an external 20 MHz oscillator., and "DEFINE OSC 20" is in my code. I didn't have any trouble setting EITHER HS or EC settings (wierd), but it's the power-up delay that's confusing. Don't see a reason for it.
|
HS should be it. OSC input on both OSC pins.
What about MCLR?
Is it pulled high?
Since the time-outs occur from the POR pulse, if MCLR
is kept low long enough, all time-outs will expire. Bringing
MCLR high will begin execution immediately
(Figure 4-5). This is useful for testing purposes or to
synchronize more than one PIC18FXXXX device
operating in parallel.
Dave
Always wear safety glasses while programming.
|
I don't know why HS should be it. EC should be it. I'm using an External OSC. Input is only on pin A7. MCLR is pulled high w/ 4.7K, and snaps high immediately on power up.
|
When you said you were not using a crystal I got to thinking resonator.
You can use HS mode, OSC2 will just be an open pin.
As for your problem I am at a loss.
Maybe there is something at the beginning of your code messing things up?
Dave
Always wear safety glasses while programming.
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks