Hiya All! I read in the readme file of MPASM 1.4 that it supports the 24C range of EEPROMs with macro's or something. It looks promising, but I can't figure out what the heck they are talking about. To save you time, I'll quote from readme.asm ..The selections EEPROM8 and EEPROM16 are provided for generic ..memory product support. Read below for a description of how ..to use MPASM to generate files for programming Microchip Serial ..EEPROM devices. .. ..The standard header files have been updated to reflect these ..devices. No header files are provided for generic memory produc ..support. .. ..2. MPASM can now be used to create files for programming ..Microchip Serial EEPROM devices. .. ..Two "processor" selections are provided to generate byte data - ..EEPROM8 and EEPROM16. Both generate data in terms of bytes, ..but EEPROM8 considers a "word" to be 8 bits wide, while ..EEPROM16 considers a "word" to be 16 bits wide. The "program ..counter" is always incremented in terms of bytes. .. ..The default size for memory products is 128 bytes. This can ..be overridden by using the LIST M= directive. ..Note that is always evaluated as a decimal number. ..The header file MEMORY.INC is provided to define the maximum ..address for available memory devices. The format of the ..defined symbols is _; for example, to set the maximum ..memory size for a 24LCS21, use the directive LIST M=_24LCS21. .. ..The following data generation directives are supported for ..memory products: .. .. DW FILL ORG .. ..The behavior of other data generation directives is not ..guaranteed. All other directives are unchanged. Has anyone had the fortune of figuring out how it works? -- Friendly Regards Tjaart van der Walt ______________________________________________________________ | Another sun-deprived R&D Engineer slaving away in a dungeon | |WASP International GSM vehicle tracking and datacomm solutions| |+27-(0)11-622-8686 | http://wasp.co.za | tjaart@wasp.co.za | |______________________________________________________________|