Weird issue with Lab X1

[Demon]

Using PBPro, 16F877 compiles, programs and runs fine, the LED bar blinks at the proper rate. If I reset MCLR, the LEDs blink at proper speed.

But if I disconnect the X1 power and reconnect the LEDs blinks at turbo speed. I reset MCLR and it does the same thing.

Has anyone had something similar to this? It's as if it loses the oscillation.

DEFINE OSC 4 ' Set oscillator speed
TRISD = 0 ' PORTD to all output
loop: PORTD = %00000000
pause 200
PORTD = %11111111
pause 200
Goto loop ' Do it forever
END ' Terminate processing

PIC BASIC Pro v2.46a
Microcode Studio Plus v3.0.0.5
MeLabs USB Programmer v4.24 using default configurations switches
Lab X1 using all default jumpers running at 4 MHz

I've been out of the loop for a while, so please bear with me if this is something real stupid.

[mackrackit]

I have never used that board but I have heard of others using that type with the programmer software setting the fuses giving trouble.

Should be some place in the programmer software to turn that option off then set the fuses in code space or the *inc file.

Maybe....

[MOUNTAIN747]

Robert,
Are the OSC pins on the board set for 4Mz or a faster rate?

[Demon]

Robert,
Are the OSC pins on the board set for 4Mz or a faster rate?

Yup, 4, using onboard crystal.


"Lab X1 using all default jumpers running at 4 MHz"

[Demon]

I have never used that board but I have heard of others using that type with the programmer software setting the fuses giving trouble.

Should be some place in the programmer software to turn that option off then set the fuses in code space or the *inc file.

Maybe....

The part I don't get is that the program works perfectly as long as I don't disconnect power. I can program over and over, no problem.

Remove power, reconnect and boom, LEDs blink at turbo rate. I reprogram, LEDs now work fine.

I can disconnect programmer as the program runs, LEDs continue to blink properly.

[Demon]

I have never used that board but I have heard of others using that type with the programmer software setting the fuses giving trouble.

Should be some place in the programmer software to turn that option off then set the fuses in code space or the *inc file.

Maybe....

I look in the sample programs and none of them use includes. I remember that we had to use them before, but it's been long enough that I don't know if this is now the way things are done.

The programmer does identify the PIC 16F877 properly.

[mackrackit]

Depends what you want to include. Not sure what you are getting at?

[Demon]

Depends what you want to include. Not sure what you are getting at?

We used to include stuff like 18F877x, I can't find any more examples, don't have my old drive. It was long files with a ton of variables and addresses inside, I think in assembler.

And then there's this stuff:


ASM
LIST
include 'M16F62x.INC' ; PM header
device pic16F628, hs_osc, wdt_off, pwrt_on, mclr_off, lvp_off, protect_off
XALL
NOLIST
ENDASM


I can't find one I used for a 16F877, and no longer remember which of these switches we used.



EDIT: Found M16F87X.INC, that looks like what I was thinking about.

[mackrackit]

That all was either before my time or by the looks of it maybe a PM thing. What if tou used MPASM? Just curious...

Now modedefs seems about the only thing that PBP requires and only for certain command.
But you can still use includes, you are going to love some of the stuff Darrel has done.

Looking at the schematic of the LABx
http://melabs.com/downloads/labx1sch.pdf
What does U2 do? Bad chip?
I am just guessing... as usual