Noobie Question

[paul borgmeier]

Only if you set the config fuse to disable MCLR and make GPIO.3 an input.

For clarity, I guess I should have added the bold to my original comment so that it read

"if GP3 is set as MCLR internal you have no choice since it is auto configured as an input, which is what you want."

With Steve's discussion above and before mine, I thought this was clear but after rereading my response this morning, I see that it was not - good catch.

Paul

[dhouston]

Paul,

It gets confusing because all of the various programmers use different terminology to refer to the MCLR config setting so it's hard to create a universal "how to".

[mister_e]

and more, pretty bad that PBC don't allow to set the config fuses in the code.. that would be so much convenient. Yet another real limitation of PBC.

    @ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON
         ' Internal Oscillator
         ' Enable watch dog timer
         ' Enable power up timer
         ' Disable MCLR pin
         ' Enable brown out detect

[paul borgmeier]

and more, pretty bad that PBC don't allow to set the config fuses in the code.. that would be so much convenient. Yet another real limitation of PBC.

    @ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON
         ' Internal Oscillator
         ' Enable watch dog timer
         ' Enable power up timer
         ' Disable MCLR pin
         ' Enable brown out detect

Without PBC, I cannot test or look at the "supplied" files but if the fuses are not dropped in by a .inc file like they are in PBP, I wonder if the user could include them in the following manner (at the top of their program):

ASM
device pic12F675, intrc_osc_noclkout, wdt_off, mclr_0ff, protect_off
ENDASM

I do remember that PBC supports inline ASM – shouldn't this work?.

(I use MPASM - I am not sure if the format for PM is correct above).

If it does work, I think this would be easier than having to edit the .inc file like we do in PBP. Thoughts?

Paul Borgmeier
Salt Lake City, Utah
USA

[dhouston]

ASM
device pic12F675, intrc_osc_noclkout, wdt_off, mclr_0ff, protect_off
ENDASM

I don't think it will work because the programmer does not look at the file. The fuses have to be set by the programmer. With PBP and the MEL programmer, the @device statements are read by the programmer and it, in turn, sets the fuses.

[paul borgmeier]

I don't think it will work because the programmer does not look at the file. The fuses have to be set by the programmer. With PBP and the MEL programmer, the @device statements are read by the programmer and it, in turn, sets the fuses.

I must be from Missouri because I still do not see why it will not work. When I write in pure ASM, I include the __Config in my ASM file and MPLAB takes care of my fuses. When I write in PBP, I edit the inc. file for my fuse choice and the fuses are set by MPLAB.

I have not used PM or the EPIC for years but doesn't one, when using PBP with these two, edit the .inc file for the proper device settings and then the fuse settings are automatically set when programming?

I have PBC somewhere and an old EPIC somewhere – maybe I need to see it not work to believe it. (I hope I can find them).

Paul

[dhouston]

You can refer to Melanies post for how to set config fuses with PBP depending on whether you use PM or MPLAB.

• http://www.picbasic.co.uk/forum/show...iguration+fuse

The Epic Windows software will read the file and, if you have this option enabled, set the config items.

With PBC you will get a compiler error at @.