Noobie Question

[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 @.

[paul borgmeier]

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

I am (at least I thought I was) fully up to speed on how to set fuses in PBP (or MPASM for that matter) - great post though for the community at large.

With PBC you will get a compiler error at @.

Why I care, I am not sure since I do not use PBC, but I am still intrigued that it does not work. I would have guessed MELABS would have built PBC and PBP around the same PM code – this is my assumption and not noted anywhere except both manuals use the term PM (and I beleive it true ).

The PBC manual (online) says you can insert ASM code and it will be inserted verbatim in the ASM file (with errors or not). The difference is PBC makes no mention of using @ before ASM code but does show ASM/ENDASM as the way to do it. If PBC is choking on the @, maybe the format I originally suggested would be inserted and hence work. If anything - the PBC PM should choke if it is not supproted, not PBC. Thoughts yet again? (I hope you can save me from having to find my old soft/hardware


Paul

[dhouston]

Using your formulation, PBC throws an error, saying "OPCODE expected instead of pic12f675".

[paul borgmeier]

Using your formulation, PBC throws an error, saying "OPCODE expected instead of pic12f675".

If you would be kind enough to test one more ...

I think "my formulation" was not 100% correct because the word "device" was in Column 1 (I did not add code formating). What happens if you use this.

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

Paul

[dhouston]

It chokes on mclr_Off as an "undefined symbol".

When I replaced that with "mclr_off", it compiles and EPICWin appears to set the config fuse settings as defined in the file.

[paul borgmeier]

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.

It looks like the PBC folks DO have an option for auto handling fuse settings. Not directly like in PBP, but with a nice workaround.

dhouston, thanks for helping to make this work. It would still be a mystery without your efforts.

The hard part for them now will be to find the proper format for the device statement.

Here are few to get them going:

12F675
device pic12F675, intrc_osc_noclkout, wdt_on, mclr_on, protect_off

16F628
device pic16F628, xt_osc, wdt_on, pwrt_on, mclr_on, lvp_off, protect_off

16F84A
device pic16F84A, xt_osc, wdt_on, protect_off

16F877
device pic16F877, xt_osc, wdt_on, pwrt_on, lvp_off, protect_off

Now, if only I used PBC I would be all set ...

Paul Borgmeier
Salt Lake City, Utah
USA

[dhouston]

dhouston, thanks for helping to make this work. It would still be a mystery without your efforts.
The hard part for them now will be to find the proper format for the device statement.

This notation also seems to work...

asm
   	device pic12f629, intrc_osc_noclkout
   	device pic12f629, wdt_off
   	device pic12f629, pwrt_on
   	device pic12f629, mclr_off
   	device pic12f629, bod_on
   	device pic12f629, protect_off
   	device pic12f629, cpd_off
endasm

It also works with upper case or even mixed case.

At first, I thought your mclr_0ff failed because it was mixed case. Now, I think you typed a zero (0) instead of the letter O.

While I haven't tested it, I expect this notation will also work with PBP.