18F1320 ... Strange Memory

[Luciano]

Hi,

Disable interrupts when you write the internal EEPROM.
(From the datasheet).

Can you write a small PicBasic program that only
write and read the byte at location 10?

Can you write location 10 with a chip programmer and
then read the same location with PicBasic?

Can you write a small assembly program that only
write and read the byte at location 10?
(See datasheet).

Best regards,

Luciano

[Melanie]

Kinda difficult to comment without seeing the code that reads and writes to the EEPROM... really as Luciano states, create some simple code to write to EEPROM, then read it back and verify.

What I normally do, is also read the EEPROM back in my Programmer (always assumining your has that capability) and doubly confirm what I've written is actually stored there. That way you can concentrate on debugging the READ or the WRITE part of your code.

Of course you do have the latest PBP and MPLAB that has eliminated the internal EEPROM anomalies of the earlier versions?

[sougata]

Hi,

I once found on a PIC18F452 that if I codeprotect the first 512 bytes (boot) of the chip then my eeprom storage would no longer work. Leaving it out and protecting the other pages did the trick.

[Acetronics2]

Hi, Mel and Luciano

PbP is 2.46 "patched" release, and MPASM v 5.02 ... and ... no chance to use PM here !!! ( 18F1320 not supported ... it says)

If you want, I send you the code ... no secrets there !!!

There are no interrupts in this program ... I ever try not to use ... to avoid input parasitic signals difficulties ...

I've read memory w/ my picstart ... that's how I found what was happening.

The only thing I didn't try was to write into the memory not only 8 but, say, 20 values following each others...

I changed the values types ... no more luck !!!

And do not forget memory use is OK with 16F devices ...

Thanks for your Help

Alain

[Acetronics2]

Last news :

I added a value at position 9 (0 ) and copied the "writes" from location 1 to 9 to 21 to 29 ...

result : all values Written ... except value at loc.2 that has been overwritten by "FF" .... my three lonesome further values always aren't written.

may be there are overwritten too ... i'll never know.

one sure thing ... there's a writing problem !!!

Alain

Hi, SOUGATA

All writing protections have been removed ... I have to program in two times : at first config , and then program. default configs locks the programming !!!

[Luciano]

	
WRITE 2,NeutreC.lowbyte
WRITE 1,NeutreC.highbyte
WRITE 4,GaucheC.lowbyte
WRITE 3,GaucheC.highbyte
WRITE 6,DroiteC.lowbyte
WRITE 5,DroiteC.highbyte
WRITE 7,Invert   <<<<<<<<< Invert is declared as BIT
WRITE 8,Side   <<<<<<<<< Side is declared as BIT

I don't use PicBasic.

Will "WRITE" support the BIT data type?
Try to declare the variables Invert and Side as BYTE.

Best regards,

Luciano

[Acetronics2]

Hi, Luciano

Bit is well written in the EEPROM ...

Alain

[inteco]

I notice some problem with the programmer software too
in writing the EEPROM data for the memory location.
But seems melabs has corrected on their newer ver 3.31.
I can tell from running debugging while reading the EEPROM
data via rs232.