Write protect config bit on 18F258

[Guest]

Hi,

I've a problem with CPD bit and 18F258.
I assemble source file with write eeprom memory not protected.

I programm this file with ICD2 from Microchip :all is ok. My software runs and can write in eeprom memory

I programm this same file with dataman48 : Software works, but can't write in eeprom memory.

I read PIc with dataman : page 2 of configuration bits, I see : "CPD not protected" checked. OK.

But, if I read this same pic with ICD2, ICD2 tells : data eeprom write protect enabled.

What is wrong?

I use 4.65 version.

Thanks

Didier

[Dataman (Neil Parker)]

Dear Sir,

Please try to erase the chip first then load your file, make sure that you tick the CPD 'Not Protected' tick box in page 2 of the configuration menu. Then program the chip again and perform memory protection (this is sure to program the configuration), after this operation please check if the CPD has its EEPROM protection disabled.

Hope this helps,

Neil

[Guest]

Hi,
Thank you.
Excuse-me, oups, : write protected is bit WRTD in page 3, not CPD in page 2.

I've tryed your soluce : that doesn't work.

- When I read hex file, "WRTD not protected" is checked.

- I Use PIC with correct configuration inside, to be sure : programmed with ICD2, and WRTD not protected.

- I read hex file
- I go to config/page 3 : WRTD is checked
- I program PIC. All is ok
- I read pic
- I go to config / page 3 : WRTD is NOT checked
- I check WRTD myself
- I write configuration (memory protect)
- I read device again : WRTD is always NOT checked.
- I programm pic with ICD2
- I read pic with dataman : WRTD is checked.

Other test :

- I programm pic with ICD2
- I read with dataman
- I go configuration/page3 : WRTD is checked
- I write configuration (I don't change anything)
- I read pic
- I go configuration : WRTD is NOT checked

Then, I think there's a bug in 4.65 and 4.66 version with WRTD bit (and perhaps other bit, I don't have verify)

Can you rectify?
Thank you

Didier

[Dataman (Neil Parker)]

Dear Sir,

Please contact me directly on [email protected] for so that I can have your return e-mail address as my engineer would like to advise you directly.

Best regards,

Neil