GPUTILS Frequently Asked Questions

The latest version of this document is always available at

This FAQ tries to answer specific questions concerning GPUTILS. For general information regarding Microchip microcontrollers please check the Microchip homepage.


  1. What is the history of GPUTILS?

  2. Why can't gpasm find "P16F84.INC" on my Linux system?

What is the history of GPUTILS?

In 1997, James Bowman started gpasm. The objective was to create an open source replacement for Microchip's MPASM. During this time many people contributed to gpasm.

At the end of 2000, Craig Franklin became the primary gpasm developer. Through most of 2001 the focus was compatiblity with MPASM. This was made much easiler by a contribution of MPASM test files to the project by Microchip. Also during this time, work started on relocatable object tools for gpasm.

In 2002, A new package, gputils, containing gpasm and the new relocatable object tools was created.

Why can't gpasm find "P16F84.INC" on my Linux system?

GPASM includes a complete set of processor header files. These files are identical to the files that Microchip distributes. Often, with source code developed on win32 systems, the INCLUDE directives are written without regard to case. Linux is case sensitive. To be consistent, the header file names were all converted to lower case. Accordingly, all include directives calling out processor header files should be lower case.

This Site Hosted by:



Last updated: April 13, 2005