PicC 9.50 dsPIC Manual.pdf

Error and Warning Messagesduplicate romsize for * in chipinfo file at line *(Assembler)The chipinfo file has a processor section with multiple ROMSIZE values. Only one ROMSIZE valueis allowed. If you have not manually edited the chip info file, contact HI-TECH Support with details.duplicate sparebit for * in chipinfo file at line *(Assembler)The chipinfo file has a processor section with multiple SPAREBIT values. Only one SPAREBITvalue is allowed. If you have not manually edited the chip info file, contact HI-TECH Support withdetails.duplicate * for * in chipinfo file at line *(Assembler, Driver)The chipinfo file has a processor section with multiple values for a field. Only one value is allowedper chip. If you have not manually edited the chip info file, contact HI-TECH Support with details.duplicate zeroreg for * in chipinfo file at line *(Assembler)The chipinfo file has a processor section with multiple ZEROREG values. Only one ZEROREGvalue is allowed. If you have not manually edited the chip info file, contact HI-TECH Support withdetails.psect * not loaded on 0x* boundary(Linker)This psect has a relocatability requirement that is not met by the load address given in a -p option.For example if a psect must be on a 4K byte boundary, you could not start it at 100H.bit range check failed *(Linker)The assembler can place checks associated with an instruction in the output object file that willconfirm that the value ultimately assigned to a symbol used within the instruction is within somerange. This error indicates that the range check failed, i.e. the value was either too large or toosmall. This error relates to checks carried on a bit addresses. If there is no hand-written assemblercode in this program, then this may be an internal compiler error and you should contact HI-TECHsupport with details of the code that generated this error. Other causes are numerous.can’t open include file *(Assembler)The named assembler include file could not be opened. Confirm the spelling and path of the filespecified in the INCLUDE directive, e.g.:INCLUDE “misspilt.h”; is the filename correct?321