Boot Segment Program Write Prot bit 30F5011

[jventerprises]

Hi,

Is there something I am missing about codeGuard and the DSPIC30F5011?

I want to just unsecure the entire memory range, ie General Segment with no protection.

My fuses look correct, but my Boot segment protection bit (FBS:0) always comes back as protection set even though I have requested it shouldn't.

I am running at 5v

here are my fuses

[jventerprises]

problem still exists in 4.114
_________________
Jon

[FvM]

CCS managed to introduce several faults with 30F5011 configuration fuses. The most important point is to refer
to MPLAB to get a second opinion about correct fuse coding. It may be wrong in some cases, but most likely not
for months or even years. MPLAB reveals, that WRTB/NOWRTB operation has been inversed.

The second point is, you can avoid the problems easily by specifying no boot sector related fuses at all. You get F80006 = 310F,
which is decoded by MPLAB as all boot sector features and protection disabled.

As often told in the CCS forum, you can always set all configuration bits directly by a #ROM statement, geting rid of the
compilers erroneous beliefs. Ìf you want correct operation of all configuration fuse commands in PCD, file a bug
report and patiently wait for CCS to fix the issue, or start the IDE device editor tool and fill in the correct fuse codes yourself.

[jventerprises]

Thanks for the suggestions, I had discovered the inversion of the WRTB but in order to clear it I had to change my operating voltage from 3.3 to 5. It was extremely annoying.

I have followed your suggestion and just set the config bits directly, not relying on the #FUSE directive.

Currently I have one giant general segment with no protection. I have tried to enable standard security on that section but the PIC refuses to accept it. No matter what I program I get no protection. I assumed it was because I only had one segment defined, so I have enabled the boot and secure segments but to no avail.

Thanks
_________________
Jon

[FvM]

There are possibly more bugs in the present PCD implementation of 30F5011 fuses. I don't use the chip, so I can't check if certain settings can be programmed. As said, I would check the fuse settings with MPLAB.