> I am building a project in MPLab 6.10 and noticed that > some of my variable space was mis-labeled in the > "Program Memory" window. > Looking a bit deeper, the first eight bytes of register > space have been re-labeled as follows in the file registers > window: > Address Hex Decimal Binary Char Symbol Name > > 0000 00 0 00000000 . A > 0001 00 0 00000000 . AN1 > 0002 00 0 00000000 . AN2 > 0003 00 0 00000000 . ADDEN > 0004 00 0 00000000 . ABAT > 0005 00 0 00000000 . ACKDT > 0006 00 0 00000000 . ACKSTAT > 0007 00 0 00000000 . ADCS1 > > > None of these are mine. They look like bit definitions and the like from the standard include file. > I had been declaring variable space with a CBLOCK > statement as follows: > > ;***BANK0 > CBLOCK 0x00 By the way, this part of bank 0 is the access bank, which is probably not where you want to put general "bank 0" variables. > b_from_r ;Byte from robot > c_from_r ;Control from robot(4) > b_to_r ;Byte to robot > ... First, you are confusing the file register window and the program memory window. Second, the file register window is just a dumb dump. For each address it displays the first symbol name it can find that has the same value as the address. It can't tell that AN1 is intended to be a bit number, and that you think of location 1 as being called C_FROM_R. Both those symbols have the value 1, so it picks one, apparently the first one in alphabetical order. The file register window in general and symbolic display of it in particular are not that useful for looking at variables. That's what the watch windows are for. ***************************************************************** Embed Inc, embedded system specialists in Littleton Massachusetts (978) 742-9014, http://www.embedinc.com -- 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