Jump to content

Brad

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Brad

  • Rank
    Newbrie
  1. Thanks for clearing this up for me Dave. Migrating my mind over from NEC microcontrollers...
  2. Hi, Compiling to PIC16F886 with SourceBoost V6.97 Beta 2 or V6.96 on a Windows XP machine. Using the following preprocessor directives: #pragma DATA _CONFIG1, _DEBUG_OFF & _LVP_ON & _FCMEN_OFF & _IESO_OFF & \ _BOR_NSLEEP & _CPD_ON & _CP_ON & _MCLRE_OFF & \ _PWRTE_ON & _WDT_OFF & _XT_OSC #pragma DATA _CONFIG2, _WRT_OFF & _BOR21V #pragma DATA _EEPROM, \ 0xCFF9, 178, 155, 138, 124, 113, 103, 95, 88, 82, 77, 73, 68, 65, \ 249, 237, 226, 216, 207, 199, 191, 184, 178, 171, 166, 160, 155, 151, \ 146, 142, 138, 134, 131, 127, 124, 121, 118, 115, 113, 110, 108, 105, \ 103, 101, 99 After successfull compile I get the following HEX output: :02400E0001327D :02401000FF3E71 :10420000F9CFB2009B008A007C00710067005F005C :10421000580052004D00490044004100F900ED00F3 :10422000E200D800CF00C700BF00B800B200AB006A :10423000A600A0009B00970092008E008A008600D6 :1042400083007F007C0079007600730071006E00AF :0A4250006C00690067006500630060 It seems to me as if the addresses are incorrect (red text) and the bytes are stored into memory at word (16-bit) offsets (blue text). I can not seem to find a work around to the incorrect address mapping, unless I am mis-reading the HEX file?
×
×
  • Create New...