PIC only works connected to debugger...

[LabRat]

Hey gang...

Trying to get a basic "bit whacker" up and running. I've grabbed the source for the bootloader, and updated it for the 20Mhz resonator that I have connected. At this time I've kept things very bare-board. I've got a couple of diagnostic LED's attached (different pins from the original fw, so I have updated for the new locations). I also moved the "debug" switch to a (now obviously stupid) different location (pin 28, thus conflicting with the ICSP).

Most of this is redundant information as the question is.. what could lead to having a software image that will load and run just fine, when under control of the debugger (JuneBug), but won't run on it's own?

My "hello world" is - led init, led light, loop forever. Works flawlessly under debugger control, but nothing appears to happen when I disconnect the JuneBug.

Thoughts?

[Edit: 18F2550 is connected to USB for power. So it's not a case of losing power when I disconnect the debugger. ]
Thanks
Andrew

 

[Pommie]

It's because it has the debug executive loaded as well as your code. Select your PicKit2 as a programmer instead of a debugger and it will work fine.

Mike.

 

[LabRat]

Oh mah gawd...

I've spent hours chasing this... when you describe the solution it's so obvious.


Thank you.. burned the hex with PK2 directly.. disconnected.. and presto.. led's are lit.

Brilliant

Thx again.. I'm packing it in for the night. (2:14 am it plenty late)

 

[Sceadwian]

LabRat been there.. done that =\ AVR's for me though not PIC.

 

[smanches]

Well, now I know what has been much frustration to me. Thought I was handling MCLR wrong somehow, but it was "intermittent". Now I know...