MPLAB v6.2 PIC18 Code Update
Budget: $250 – $750 USD
I have a legacy code-base for a PIC18LF452 that was last maintained in a very early MPLAB release. When I load it into MPLAB v6.2 the compiler finishes cleanly, but the build stops at the link stage with “incorrect library” errors. Both the standard C runtime and a small collection of board-specific custom libraries are being pulled in from the wrong paths or with outdated archive names, so the HEX file is never produced.
Your job is to modernise the project so it builds end-to-end in MPLAB v6.2 without warnings. That means:
• Update the project and makefile settings so the correct standard C libraries for v6.2 are linked.
• Refactor or replace any obsolete #pragma, linker script, or header directives that break the new tool-chain.
• Re-organise the custom libraries (source or object) so they resolve cleanly under the current linker.
• No new code should be required
• Deliver a verified build: project files, updated C/ASM sources, linker script, and the generated .hex. I will flash and run it on hardware to confirm.
Please work directly inside MPLAB v6.2 and keep the code compatible with the PIC18LF452 data-sheet limits. Once the build is repeatable on your end, send me the updated tree along with a brief change log and any notes required for future maintenance.
Your job is to modernise the project so it builds end-to-end in MPLAB v6.2 without warnings. That means:
• Update the project and makefile settings so the correct standard C libraries for v6.2 are linked.
• Refactor or replace any obsolete #pragma, linker script, or header directives that break the new tool-chain.
• Re-organise the custom libraries (source or object) so they resolve cleanly under the current linker.
• No new code should be required
• Deliver a verified build: project files, updated C/ASM sources, linker script, and the generated .hex. I will flash and run it on hardware to confirm.
Please work directly inside MPLAB v6.2 and keep the code compatible with the PIC18LF452 data-sheet limits. Once the build is repeatable on your end, send me the updated tree along with a brief change log and any notes required for future maintenance.