Converting to MPASM

[btaylor]

Hi Melanie,

Thank you for the prompt assistance. I had in fact read your post on configuration fuses in the FAQ prior to my message. I should have mentioned that. Sadly it did not cut it for me.

For example I took the line in PBP
@ Device pic16F876A, HS_OSC, BOD_OFF, PWRT_ON, WDT_ON, PROTECT_OFF

and re-wrote it to suit MPASM as
@_config_HS_OSC &_BOD_OFF &_PWRT_ON &_WDT_ON &_PROTECT_OFF

The error count on compiling under MPASM jumped from 3444 errors to 6259 errors - hardly a leap forwards.

Must I cover EVERY fuse in the chosen controller? Can some be left as don't cares or whatever the default is?

Can I explicitly declare the processor type in the @_config_ line in MPASM? A project at the moment has three separate interacting parts with three different processors and jumping between them occasionally calls up the wrong controller. PM lets me know - can MPASM do that?

Is there some magic at the start of the @_config line? Is it @__config or @ __config. Must it start in the first or second column or what?

Cheers
Brian