Wow!
dcbrown thanks for your answer. The "//FILES c018i.o" was the final link to success. I've gotten good builds on the "bad" code, a subdirectory copy of a good code, and even on a separate computer. I never even thought to look in 18f872.lkr, let alone think it was a text-readable file. Next step is PROGRAMMING!
I have only one possible nit to pick, in case others are following along.
Quote:
|
Verify that the "Linker-Script Path" just below the $(LIBDIR) is blank...
|
Should that be $(LKRDIR)? The picture you have is what I did.
Again, many thanks!
Roger.