PicC 9.50 dsPIC Manual.pdf

Error and Warning Messages8 bits will be rounded up to the nearest byte size, i.e. a 7 bit space in an instruction will be shown as1 byte.Generate an assembler list file for the appropriate module. Look for the address specified in theerror message.7 07FC 0E21 movlw 338 07FD 6FFC movwf _foo9 07FE 0012 returnand to confirm, look for the symbol referenced in the assembler instruction at this address in thesymbol table at the bottom of the same file.Symbol Table Fri Aug 12 13:17:37 2004_foo 01FC _main 07FFIn this example, the instruction causing the problem takes an 8-bit offset into a bank of memory, butclearly the address 0x1FC exceeds this size. Maybe the instruction should have been written as:movwf(_foo&0ffh)which masks out the top bits of the address containing the bank information.If the assembler instruction that caused this error was generated by the compiler, in the assemblerlist file look back up the file from the instruction at fault to determine which C statement hasgenerated this instruction. You will then need to examine the C code for possible errors. incorrectlyqualified pointers are an common trigger.(479) circular indirect definition of symbol * (Linker)The specified symbol has been equated to an external symbol which, in turn, has been equated to thefirst symbol.(480) signatures do not match: * (*): 0x*/0x* (Linker)The specified function has different signatures in different modules. This means it has been declareddifferently, e.g. it may have been prototyped in one module and not another. Check what declarationsfor the function are visible in the two modules specified and make sure they are compatible, e.g.:extern int get_value(int in);/* and in another module: */int get_value(int in, char type) /* this is different to the declaration */{288