WRITE data to EEPROM on PIC18F8621

[dschafer]

PicBasicPro version 2.4.6.0

[skimask]

PicBasicPro version 2.4.6.0

Show us the program that's failing you...

[dschafer]

Show us the program that's failing you...

Its a long program, but what i'm trying to do using READ and WRITE is as follows:

'at the start of the program read these values from EEPROM and place in the variables'

Read 0, trip_amount[0]
Read 1, trip_amount[1]

'so far so good, this works as per usual'

If S1 = 1 Then
Read 0, temperary[0]
Read 1, temperary[1]
If (trip_amount[0] <> temperary[0]) OR (trip_amount[1] <> temperary[1]) Then
Write 0, trip_amount[0]
Write 1, trip_amount[1]
LCDOut $FE, 1
LCDOut $FE, $C0 , " SAVING CHANGES"
Pause 1000
EndIf
Goto Menue_2_0
EndIf

'I get a SAVING CHANGES on the LCD but the eeprom values dont change'

[skimask]

well that should work fine, must be something in the rest of the program that isn't being shown, maybe a variable declaration, changing the variable itself in another part of the program, etc.etc.

[dschafer]

No, that is not the case, I have checked over the code many times.

One thing I did notice is when I program the PIC the fuse settings for 'EEPROM table write protect' and 'CONFIG table write protect' are both DISABLED, But when I read the HEX, EEPROM, and fuse data back to the PIC programer both of those setting are ENABLED.

[mister_e]

High likely it's down to your PIC programmer. Which one?

[dschafer]

High likely it's down to your PIC programmer. Which one?

I use the DIY K128 v141204

[skimask]

No, that is not the case, I have checked over the code many times.

Of course it's never the program writer's fault, is it?

One thing I did notice is when I program the PIC the fuse settings for 'EEPROM table write protect' and 'CONFIG table write protect' are both DISABLED, But when I read the HEX, EEPROM, and fuse data back to the PIC programer both of those setting are ENABLED.

So set them so that the 'protect' options are enabled, read them back, see if they're disabled, and try the program again. Maybe the software for the programmer is bass-ackwards...