table read Vs eeprom

These parameters are easily obtained from the datasheets. Some (size, avialability!) will vary from PIC to PIC.

Wouter van Ooijen

-- ------------------------------------

"Wouter van Ooijen

Yes, I know that. Some Pic's don't have an EEPROM and the size is different just as the size of program memory.

What I want to know is when to use what, and on what that choice is based.

I can only find that a table is more reliable than the EEPROM, and some code samples for both. But when to use what is still a puzzle to me, I think table reads are better but the (All??? the 18F) PIC's still have EEPROM's onboard.

Greetings (not from Gelderland but from Overijssel (Twente),

Alexander

(teacher mode, I never give the full answers)

Check the number of allowed writes, and what happens during a write.

Wouter van Ooijen

-- ------------------------------------

The big advantage of the EEPROM space is that you can write to it programmatically (from the PIC code, that is). It's commonly used to provide non-volatile storage for setup parameters, calibration values, and the like.

-- Mark Moulding "I prefer heaven for climate, hell for company."

That's only partially true, the 18F series can write to programspace also from Pic code.

I had a little help from Wouter, but still no real reference on when to choose what. I quess that if you have a lot to write and the time for it write to program space, else use the eeprom. Also what you said can be used but only for reading.

ThanX for the reply

"Mark Moulding" schreef in bericht news:QIa1e.15646$ snipped-for-privacy@newssvr14.news.prodigy.com...

A lot of 16F PICs can do this too. It is what makes a bootloader possible.

Wouter van Ooijen

-- ------------------------------------