On 15/10/2013 8:15 AM, Matt Bennett wrote:
> On Mon, October 14, 2013 4:15 pm, David Duffy (AVD) wrote:
>> That seems to be when you have variables directly associated with the
>> data?
>>
>> In my case, some of the EE could be associated with variables, but other
>> data is used with generic read / write commands from a PC interface.
>>
>> Maybe I should look into the EE variables anyway.  Learning XC8 (and C
>> in general) has been fun so far.
>> David...
>>
>> On 15/10/2013 7:00 AM, Neil wrote:
>>> I've not really used XC8 yet.  Is there a reason the C18-type way
>>> wouldn't work?...
>>> http://support2.microchip.com/KBSearch/KB_StdProb.aspx?ID=3DSQ6UJ9A0004=
DV
> I haven't used this, so please verify first, but checking the XC8 manual,
> there are a couple options- you can use:
>
> eeprom char regNumber[10] =3D "A93213";
>
> Also, section 5.5.5.2 of the XC8 manual describes a macro:
>
> #include <xc.h>
> __EEPROM_DATA(0, 1, 2, 3, 4, 5, 6, 7);
>
> The difference being that this is just inserting the data into the .hex
> file used to program the part- it isn't associated with a variable.

I started using the __EEPROM_DATA macro which is fine for some=20
applications.  What would be nice is if there was a version of that=20
where you specified an offset from the EE start and a variable number of=20
values.

I'll have a look to see how that macro is defined.  Maybe that will give=20
me more ideas.
David...

--=20
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: www.audiovisualdevices.com.au
___________________________________________

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