Troubleshooting guide for EPIC™ Programmer

• EPIC™ for Windows
• Programming Errors
• Difficulty Reading Devices
• EPIC™ for DOS
• Specific to: PIC18Fxxxx

#1 Most Encountered Problem - Power Supply

The most common cause of programming problems is low power supply voltage.  We highly recommend the use of an AC Adapter.  Batteries become depleted very quickly, causing program errors ("Code Programming Error at 0000").

The adapter that we supply for use with the EPIC outputs 16VDC at 500mA.  You may substitute an adapter if it meets the voltage and current requirements of the EPIC Programmer.  Your adapter should output at least 13VAC or 16VDC at 500mA.  The AC adapter connection on the EPIC is not polarity sensitive.

#2 Most Encountered Problem - Menu Settings

The next most common problem is incorrect option settings in the EPICWin software.  This software has a large number of configuration and option settings that can be a bit confusing.  The EPIC help file includes a complete explanation of the EPICWin Menus.

Some common symptoms and causes are:

• Configuration settings get reset every time you try to program a device. - The options "Reread file Before Programming" and "Update Configuration" are both checked.  This causes the software to automatically read configuration settings from the hex file every time you program.  The configuration menu is updated with the settings it finds in the file.
• The EPIC seems to program without errors, but the device remains blank. - The option "Program/Verify Code" is unchecked.  This option should always be checked when you want to program the code space on the device.
• The device programmed once, but subsequent attempts return a Code Programming Error. - The configuration option "Low-Voltage Programming Enable" is checked.  This leaves the device sensitive to a signal or high condition on the low-voltage programming pin (see the Microchip datasheet).  To recover from this condition, you must tie the low-voltage programming pin to ground and reprogram the device with the option unchecked.

Programming Errors:

"Code Programming Error at... "
"Device Not Blank..."

• The EPIC power supply may be low. (see above).
• This problem can be caused by a bad 25-pin cable, or parallel port settings.  Try a new cable, and set the parallel port to "standard" or "ECP" (try both) in the bios setup on your computer.
• There should be no resident drivers using the printer port.  This is especially important for Windows machines using HP printers, or devices such as scanners and Zip drives that connect to the parallel port.  Disconnecting the device is not enough, you must stop the driver.
• Printer switch boxes can cause problems.  Try it with the EPIC connected directly to the printer port.
• The device your are programming must be selected in the drop down box in the EPICWin software.  The drop down selection changes when you roll the wheel on a scrolling mouse while focus is on the EPIC window.
• The device you are trying to program may not be blank.  Read the device and view the code. If it is blank, all locations should read 0FFF, 3FFF or FFFF.  If it reads all 0000, then your device is code protected. (FLASH parts can be programmed even if not blank.)
• If you are using a UV-erasable part, and you have programmed it previously with code protect on, the device may be ruined.
• If the device is new, newly erased, or if you have previously enabled low-voltage programming, you may have to ground the low-voltage programming pin on the device while programming.  Check the Microchip data-sheet for the location of this pin on your device, if it exists.  There are modifications that you can perform on some of the ZIF adapters to take care of this.
• If you are trying to program the device in-circuit, on a board of your own design, don't use a long cable between the EPIC and your circuit.  Keep it less than 6 inches, neat and clean, without splices or extra connectors.
• The timing parameters that EPICWIN uses for the FLASH parts may not work on your computer. You can change them according to this procedure.  (Does not apply to meProg software.)
• Devices with internal RC oscillators and a programmable reset pin may fail to enter programming mode when programming in-circuit.  If you are programming one of these devices in-circuit, you may have to disable the clock oscillator if the MCLR pin is configured as an input.  Master Clear Reset should always be enabled if you are programming a PIC16F627 or 628 in-circuit on the LAB-X3.  This option is found in the EPICWIN configuration menu.  This problem does not affect programming if you use a programming adapter or the DIP socket on the EPIC board.
• Devices with internal RC oscillators come from the factory with a calibration factor stored in the last location in memory.  Because of this they will fail the blank check.  You should disable the blank check when using these devices.
• Windows NT/2000/XP ONLY:  Use the Windows Task Manager to stop the process "spoolsv.exe".  
• Problems when programming PIC18F devices can sometimes be fixed with a small modification to your EPIC Programmer board.

Windows 95/98/NT/2000/XP:

"EPIC Programmer Not Found"
"Unable to load driver..."

• This problem can be caused by a bad 25-pin cable, or parallel port settings.  Try a new cable, and set the parallel port to "standard" or "ECP" in the bios setup on your computer.
• There should be no resident drivers using the printer port.  This is especially important for Windows machines using HP printers, or devices such as scanners and Zip drives that connect to the parallel port.  Disconnecting the device is not enough, you must stop the driver.  The native Windows drivers usually allow the EPIC to function, but drivers supplied by the printer manufacturer can block the port.
• Install a printer driver for a Generic, Text Only printer on the same port as EPIC.  Set this printer to the default for the system.

Windows NT/2000/XP:

"Unable to load driver PICLPTNT.SYS"

• Usually, running the EPIC Windows programming software will automatically load the Windows NT/2000/XP driver. In some cases and with some permissions, the driver may not be properly loaded under NT/2000/XP. A program, NTINST, is included to install or remove the EPIC Windows NT/2000/XP driver. To clean up a bad install, remove the driver, then reinstall it.  Run the program in a command prompt window from the EPIC install directory.  You should be logged on as an administrator.  The ntinst executable cannot be run from a networked drive.

Open a command prompt by clicking Start>Programs>Accessories>Command Prompt.

Change to the EPIC directory by typing:  CD  C:\EPIC   (substitute you directory name if changed from the default)

To remove the NT/2000/XP driver:   ntinst  /remove
To install the NT/2000/XP driver:   ntinst  /install

Windows XP:

Intermittent Code Programming Error

• Windows XP may periodically access printer ports and interrupt the EPIC programming process.  This can be stopped with a registry entry.  Download the entry here

EPIC DOS Software:

• The code buffer in EPIC for DOS is not large enough to hold an entire 8K program. It will only hold about 6 or 7K of it. If the program is larger than this size, use EPICC or EPIC for Windows 95/98/NT/2000/XP.
• The DOS software does not support as many devices as the Windows software.  Make sure that the device you are using is supported by the DOS software.

Last Updated: 08/04/2008