Stupid question

[Meriachee]

Dave,

I have tried both assemblers. I had things working just fine on another PC, and since I've re-installed, nothing seems to work, even opening any of the other files for completed projects. When I put in lines like:
device pic12F675, intrc_osc, wdt_on, pwrt_on, mclr_on, protect_off
I get errors, "cannot overwrite" and other strange things, like it doesn't like the comma or the space. I will try your suggestion this evening and see where that leads.

Gary

[mackrackit]

Did you by chance get a new machine with Vista?

http://www.picbasic.co.uk/forum/show...ighlight=vista
is an interesting thread.

[Pic_User]

Hi Gary,

(Also, this forum changes Caps. Makes the code look like the variables are whacked....)

If it is there then this is a good reason to use the CODE brackets and post your whole code.

To use the “Code Brackets” see the “vB code” Hot button in the “Posting Rules” box at the bottom left of the screen while you are posting.

It puts the code in the special box that protects the format better that the normal forum posting does...
Hope that helps,
-Adam-

[Meriachee]

Dave,

No, it's a relatively brain-ded Dell with XP. That's enough fun for one day I am not surprised that Vista is a whole new can of worms. It probably explains why people just get fed up and go cut the lawn or something.....

Code brackets. Who knew. (Fortunately for me, I've completely accepted that information going in one side causes something equal in size to leak out the other side - I'm ok with vBulletin changing the case, although it makes it look like PBPro doesn't see the variable.)

Gary

[Meriachee]

Ok, I'm going to cut the grass. ( and maybe find an all new and interesting use for the clippings!)

So, Dave, I built EXACTLY the test code you posted. No more, no less. Using the following:
MCS 2.3.0
PBPro 2.47
MPASM 5.03
Epic Plus

DEFINE OSC 4

ANSEL=%00000000
CMCON=7

LOOP:

HIGH GPIO.2
PAUSE 100
LOW GPIO.2
PAUSE 100

GOTO LOOP

No errors, no warnings. Device programs just fine. Led blinks more or less where and when it should on the programmer. Splash returns with "fat dumb and happy". Insert the chip into the proto board socket, power it up, no run. Verified, tested each and every power feed, ground, led operation, 5v across the chip just as it should be.
As my boss would say, and with appologies to anybody, wtf.

[Archangel]

Ok, I'm going to cut the grass. ( and maybe find an all new and interesting use for the clippings!)

So, Dave, I built EXACTLY the test code you posted. No more, no less. Using the following:
MCS 2.3.0
PBPro 2.47
MPASM 5.03
Epic Plus

DEFINE OSC 4

ANSEL=%00000000
CMCON=7

LOOP:

HIGH GPIO.2
PAUSE 100
LOW GPIO.2
PAUSE 100

GOTO LOOP

No errors, no warnings. Device programs just fine. Led blinks more or less where and when it should on the programmer. Splash returns with "fat dumb and happy". Insert the chip into the proto board socket, power it up, no run. Verified, tested each and every power feed, ground, led operation, 5v across the chip just as it should be.
As my boss would say, and with appologies to anybody, wtf.

Hi Meriachee,
Go back and re read post 3, from mister_e, Unless you have set the config fuses in code or manualy at program time it will program without them but not run.
JS
oh BTW
The only question which is stupid is the one you are too timid to ask, because it goes unanswered.

[Bruce]

Before you program the PIC, try setting config manually. I.E. select intrc osc,
and mclr off. Then click the save button, and try programming it. Does it
work?

Is there a check mark next to 'Update Configuration From File' & 'Reread File
Before Programming' under the Options menu?

This forces the programmer software to reload the new .hex file before
programming and use the config settings embedded in the .hex file.

Unless you have a bad PIC, that's all I can imagine that would cause this.

[Meriachee]

The nagging possibility that there was a hardware error was never far from me during this line of questioning, and once again, the blasted hardware was at fault.

Installed the same services on another machine, watched the same routine do more or less the same things, plug the same chip into the socket and lit 'er up. Watching leds blinky blink. (just like they should)

Thank you to all who responded to my questions, appologies that there never really was anything PIC related at fault. (It's ALWAYS something stuipd)

Gary