write_program_memory and 18F27J53

[Ttelmah]

Key thing is though, that I know if there was a problem, and/or while first trying the chip, you would look at the actual fuses at the end of the .lst file, and verify each one against the data sheet.

I tend to use a 'half way house'. Like PCM_programmer, I'd set the minimum to work, add any that I explicitly think are likely to cause problems, verify this is producing what I want, then later if a problem appears with a compiler version, one of the very early things I'd check is that the fuses match what the previous compiler was doing. If it doesn't, then I'd 'go explicit', and set the fuses to match the working version.

I use the 47J53 in a project at the moment, I actually explicitly have NOWPDIS set, and WPBEG, which says the protection starts at the bottom of memory and then the WPFP bits set to just protect my bootloader (config4 = 0x1). Since I was using a bootloader, and wanted this protected, I had to explicitly set this up.