12f675_fuse_about_to_blow!

[LEDave]

Couldn't get it to compile, I had:

Symbol not previously defined Ansel (I had five of these).

And one: Overwriting previous address contents.

ANSEL is analogue select right? It's my understanding that your:

ANSEL = %00000000 code line makes all the pins read in digital, or turn any analogue input off (I think) so can't understand a problem here.

Also: CMCON = %00000111 puts out decimal 7 which turns the comparitor off? Is that right? This instruction didn't seem to cause a problem.

Could all this be because the 16F676 PIC wasn't listed when I compiled it? It wasn't in the demo version drop down list.

Plenty of head scratching going on here, great fun all though, I'll be glad to figure the basics out.

Dave

[mackrackit]

What PIC did you pick from th drop down?

[LEDave]

12F683 The nearest one to the 12F675 (probably doesn't work like that does it?).

[mackrackit]

This compiles for the 12F683. May not be the correct pins to do the expected, I did not check that.

    ANSEL = %00000000
    CMCON0 = %00000111
    
    START: 
    'D0 HIGH
    GPIO = %11001111
    GPIO = %00010000
    PAUSE 500
    'D1 HIGH
    GPIO = %11001111
    GPIO = %00100000
    PAUSE 500
    'D2 HIGH
    GPIO = %11101011
    GPIO = %00010000
    PAUSE 500
    GOTO START

ANSEL is for turning the ADC on or off. Not clear why it gave an error.
The CMCON should have though.
"Overwriting previous address contents" is because I had the fuses set in code and the fuses commented out in the *.inc.
http://www.picbasic.co.uk/forum/showthread.php?t=543

Now for some data sheet reading

[LEDave]

Is there a set of code instructions for THE PBP demo version?

I'm trying to get an understanding of GPIO and the register TRISIO. If you set a TRISIO bit low you make the corresponding GPIO pin an output (I think) Except GP3 which is always an INPUT.

I've got a very blurred picture of how this all fits together, one day the fog will lift.... I hope.

Dave

[mackrackit]

http://www.melabs.com/resources/index.htm#Manuals
http://melabs.com/products/pbpis.htm

I'm trying to get an understanding of GPIO and the register TRISIO. If you set a TRISIO bit low you make the corresponding GPIO pin an output (I think) Except GP3 which is always an INPUT.

Now I see a mess up in my last code

    GPIO = %11001111
    GPIO = %00010000

should be

    TRISIO = %11001111
    GPIO = %00010000

I think.....
Sorry about that.

[LEDave]

Hi mackrackit

Yes I ran that code and it compiled with no errors.

I loaded the HEX code (confirmed write successful) but the LED's didn't light?

I reloaded you earlier HEX file and all three LED's jogging along nicely.

[mackrackit]

Yup, different code for different PICs.
When do your 12F683s arrive?

[LEDave]

I changed the code from GPIO to TRISIO

RE-compiled, re-loaded the HEX code file and away she ran.....!

Time for me to pause here mackrackit. I need to break your program down and figure out exactly what's going on. That way I can move on.

I'll try and figure it out and if you'd be so kind you can tell me how I got on.

It's the only way for me to learn.

As ever thanks for your help.

Dave

[mackrackit]

I'll try and figure it out and if you'd be so kind you can tell me how I got on.

I like it when someone wants to learn.
I will be here....

[LEDave]

The 12F683's arrived today! I didn't order them until late last night, talk about service, I love the internet....:-)

I changed the 12F675 PIC over to a 12F683 and it ran your program a treat.

I've got a lot to learn still, a huge amount but really enjoying it.

My first project (I'm getting ahead of myself here I know) but my first project will be to make a 12F683 OUTPUT binary coded decimal four bit words and drive a seven segment display. I figure with the 12F683 having six outputs this is a viable project.

Dave