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=20 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=20 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=3DSQ6UJ9A0004DV > > Cheers, > -Neil. > > > > Quoting "David Duffy (AVD)" : > >> I found the functions for EEPROM access in XC8 no problem. One thing I >> can't seem to find is how to pre-load values in specific locations at >> compile time. I do not want to associate the values with C variables. >> >> There is a macro __EEPROM_DATA(...) but that seems to only be for a >> block of 8 bytes at the start of the EE address space. You can put >> multiples of the macro in of course, but I often need to set just a >> value here and there. >> >> Is there an XC8 equivalent of the old asm way: >> >> org 0xF000 ;eeprom data space 0x00 .. 0xff (256 bytes) >> de 0x20 ;network address (serialised) >> >> org 0xF007 ; >> de 0x02 ;transmit response delay (10ms increments) >> >> --=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 .