Are you sure the PIC is running? Try a quick "blinky" without any serial stuff.
Are you sure the PIC is running? Try a quick "blinky" without any serial stuff.
Dave
Always wear safety glasses while programming.
Mackrackit,
Yep, it's running. Follow the rest of my reply.
Skimask,
Sorry for the delay. I wanted to try some additional things. I'll explain in a bit. I tried the new code. It produces two long flashes on the LED and one very quick one. It then does nothing. No characters are displayed on the terminal and I can't enter anything. Thinking that it might be something else, I traded out the Max232 with a Max233 (eliminated the caps and such). Same results. I then tried a new 16F690 (thinking that the other one might have been damaged), same results. Anything we're missing here?
Rob
Floating MCLR?
LVP is OFF?
Noisy PSU?
Poor contact, low battery, are some other great tests..
You could also begin your program with something like...
Code:START: HSEROUT ["1,2,1,2 TESTING....",13,10] FOR MyVAR=0 TO 250 HSEROUT ["MyVAR=",#MyVAR,13,10] NEXT GOTO START
Last edited by mister_e; - 30th October 2008 at 02:06.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Does the F690 run from the external crystal by default?
Try removing DEFINE OSC 3 and see what happens.
default config line is...
We don't see any config fuse setting here, so this would make some sense...Code:device pic16F690, intrc_osc_noclkout, wdt_on, mclr_on, protect_off
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
This is my config line
Code:__config _XT_OSC & _WDT_ON & _MCLRE_ON & _CP_OFF
Rob
Success!!
Okay, same setup. Same code. This time compiling was done with the melabs compiler (instead of mpasm) and downloaded with a pickit2 (instead of an ICD2). I'm going to investigate this more and post my findings.
Rob
Bookmarks