12f675_fuse_about_to_blow!

[LEDave]

Henrik thank you.

The program ran a treat. GPIO.0 blinking away at around a half a second period, GPIO.4 essentially 'on' all the time, very clever.

Nice little project you set up there mackrackit, thanks a lot. I've learned a lot from that namely:

1/ Read the program specification more closely! mackrackit wrote:

But if you do this using pauses to blink the LED the pauses will maybe get in the way (they did. I'm pleased they did though, I've learned from that).

2/ How a timed INTERRUPT works and some pitfalls (PAUSE)!

3/ A re-iteration about HIGH / LOW writing to the register everytime they're used. Far better to set the TRISIO register up and write directly to the PORT. I'm starting to appreciate the subtlety of these things, still lots to learn / re-learn though.

Right then, what's next?

Dave

[rmteo]

My suggestion is to learn what a "true" interrupt is and how to use it - as your next step. If it means using DT's routines because PBP does not do it, then by all means do so. It will enable you to do so much more as you advance in your adventures with microcontrollers.

[LEDave]

Thanks for that rmteo.

I'll bear that in mind. Don't forget I'm very new to this, sure I'll have to learn all about interrupts at sometime (maybe now is that time).

I'll be very interested in hearing where mackrackit, Henrik and Joe S think I should go next as they have an understanding on where my knowledge base (or lack of it) lies.

Hey I couldn't turn an LED on a Month ago!

Cheers.

Dave

[mackrackit]

Henrik,
Thanks for finishing that lesson, I got busy.

rmteo,
Good point about ASM interrupts. I am not sure if Dave can do that with the demo version. But when he gets the full version...

Dave,
We are not finished with PBP interrupts yet
As you saw things can move pretty fast with the hardware and if you want to have an event happen at a certain time no matter what an interrupt can help.

Many times it is not recommended to use PAUSEes because as you now know they block other things from happening. There are enough things that do this without adding more, but sometimes we have to use them. Every thing in its place.

Now try something like this...
Do a "MAIN_LOOP" that will TOGGLE a LED with a button press. Every time you press a button the LED changes state.

Then make a BYTE size variable and add the PBP interrupt routine for another LED. The new variable will increment a value of 1 every time the interrupt "triggers".

After a given amount of "trigger", the variable reaches 10 the second LED changes state.

This should happen whether the first LED and button has been activated or not.
By having the variable increment to change the second LED state you can now make it blink at any time frame you want.

[rmteo]

It may be worth pointing out that one does not need to use ASM to use interrupts. I have (and use) 3 different versions/dialects of BASIC for PIC's and they all handle interrupts (including vectored interrupts) without having to delve into ASM. Same situation with C.

[mackrackit]

It may be worth pointing out that one does not need to use ASM to use interrupts. I have (and use) 3 different versions/dialects of BASIC for PIC's and they all handle interrupts (including vectored interrupts) without having to delve into ASM. Same situation with C.

But this is a PBP forum... So the point is???

[LEDave]

Gulp, I'm on it.

I'm probably going to go quiet for a while trying to figure this one out. I'll give it my best shot though.

I suspect you and Henrik could code it in about five minutes!

Then again I'm not you or Henrik..... :-)

Dave