Weird issue with Lab X1

[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

[Demon]

The ICS502 LOCO™ is the most cost effective
way to generate a high quality, high frequency
clock output and a reference from a low frequency
crystal or clock input. The name LOCO stands for
LOw Cost Oscillator, as it is designed to replace
crystal oscillators in most electronic systems. Using
Phase-Locked-Loop (PLL) techniques, the device
uses a standard fundamental mode, inexpensive
crystal to produce output clocks up to 160 MHz.
Stored in the chip’s ROM is the ability to generate
6 different multiplication factors, allowing one
chip to output many common frequencies...


It's used to generate the clock, the jumpers are set to 4, and it works fine, until I replug.

I would say it works fine, or else it wouldn't work at all when I program.

[Demon]

I found these:

E:\Mecanique\MCSP\MPASM\P16f877.inc

E:\Pic BASIC Pro 2.46\16F877.INC

E:\Pic BASIC Pro 2.46\M16F87X.INC <---- I would think I want to include this one.


So I tried this:


ASM
LIST
include 'M16F87x.INC' ; PM header
device pic16F877, xt_osc, wdt_on, pwrt_on, lvp_off, protect_off
XALL
NOLIST
ENDASM


And I get an error it cannot open file, include 'M16F87x.INC' not found.

In MicroCode Studio Plus, under tabs VIEW, EDITOR OPTIONS, the Default Source Folder points here:
E:\Pic BASIC Pro 2.46

I would have thought it would pick up the file that way.


EDIT: So I copied M16F87X.INC where I have my PIC program source, usually compilers look in their source folder first, but it can't find it anyways. It looks like it wants to find INCLUDE files somewhere specific, I just don't see any way to tell MCSP.