Alan B. Pearce wrote:

> No do it just like a code space. Here is a sample from a project I did using
> Olins environment. You should find that there is already a "deeprom" section
> in the linker file.

Called "eeprom" in the 12F629 linker file, as far as I can se, but
it worked anyway :-)

> ;***********************************************************************
> ;
> ;   EEPROM variables.
> ;
>
> pwm1_default equ .1023/2
> pwm2_default equ .1023/2
> pwm3_default equ .1023/2
>
> deeprom code


That was my problem, tried with *anything* but "code" there :-)


> pwm1_high   de high pwm1_default
> pwm1_low    de low  pwm1_default
>
>
> pwm2_high   de high pwm2_default
> pwm2_low    de low  pwm2_default
> pwm3_high de high pwm3_default ; dummy pwm default values
> pwm3_low de low  pwm3_default
>
>
>  global pwm1_high
>  global pwm1_low
>  global pwm2_high
>  global pwm2_low
>  global pwm3_high
>  global pwm3_low

How do you "use" the pwm* symbols ? Like this ? :

   movlw  pwm1_high
   movwf  eeadr

Or how do you create the 0-127(dec) EEPROM address ?

Another thing (yes, this is my first try with the EEPROM !),
I'v seen in the HEX file that each other byte (?) is "00".
That is, when I create the data with DE directive, they seems to
be either 16-bit values, or there is something "going on"
with the addresses in the hex file. *And* the addresses
in the HEX file are actualy h'4002' when I expected h'2001'.


Jan-Erik.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics