>
> Ive used sdcc for a while , as far as I know they do not exist. you best =
bet
> in my mind would be to paste in whatever data you need in the eeprom into
> piklab (The only linux microcontroller IDE I know of), after reading the
> chip all data fields are editable so you could paste whatever you want in=
to
> the data EEPROM field and hit "program" and that generally will cover mos=
t
> eeprom needs. Ive got no idea how to program eeprom if your just using th=
e
> command line or running a wine emulation of mplab.
>
> anyways it sounds like a good opportunity to suggest some decent
> improvements for sdcc (though, sdcc is a c compiler, not a eeprom
> programmer)

Yes, I know that.
But when using asm, there is a directive DE, which seems to be meant
for this. I was hoping there is a way to implement something similar
using C, so I did not have to mess with separate data definitions for
eeprom. I even tried using that as an asm include, but it's not quite
clear about location where that should be included.
I tried sdcc directives for absolute adressing, but those are not
meant for this either.
When downloading PIC contents using pk2cmd, I can see those eeprom
bytes in hex file, but do not yet see a way to set them easily.
Let's leave it now as it is, since I found I had missed a parameter
for pk2cmd, -Z, which seem to help not to overwrite eeprom.
Sometimes verification still fails, but then works without complaints
again. Do not know the reason.

--=20
KPL
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.