>>  global pwm3_high
>>  global pwm3_low
>
>How do you "use" the pwm* symbols ? Like this ? :
>
>   movlw  pwm1_high
>   movwf  eeadr

Correct. Just like using RAM variables. The linker keeps track of the fact
that a constant needs to be filled into the code space when linking the
file. You may also like to note that doing things this way may mean that
variables could be in different places in the eeprom in different versions
of your code, depending on how the linker allocates the space. This will
only be a problem if you have such declarations in more than one module.
However it is a potential "gotcha" if wanting to save something like a
serial number in the eeprom, and not overwriting it when loading a new
version of the software. have not actually gone around this loop myself, but
imagine it would be solved by having separate data spaces in the eeprom,
just like Olin does for the shared global variables versus the local
variables.

--
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