Release Notes for MPLAB® PM3
Device (Production) Programmer

MPLAB® IDE v8.91

DLL and Firmware versions:

 MPPm3.dll   v2.40.1.56  
 PM3 Suite (OS, FW)   v2.12.00  (pm3021200.mjc)

 

April 30, 2013

 

IMPORTANT: Do not allow Windows® OS to pick a USB driver; MPLAB PM3 will not work with this driver. You must follow the procedure specified at MPLAB IDE software installation for USB driver set-up. If you did not set up the port during installation, see the section in this readme file on USB Port Setup.

Table of Contents

1       Device Support

2       Operating System Support

3       HCS Support and Programming Information

4       Reference Documents

5       What's New in v8.91

6       Repairs and Enhancements in v8.91

7       Autorun

8       Known Problems

9       Important Notes

10          Socket Support

11          Tested SD/MMC Cards

12          Definitions

13          Declaration of Conformity

1      Device Support

Click the link below to see device support for the programmer (PM3).

·         Device Support List

2      Operating System Support

This tool has been tested using the following operating systems:

32-Bit: Windows® 2000 SP4, Windows XP SP2, Windows Vista™ and Windows 7 OSs

64-Bit*: Windows XP 64, Windows Vista 64 and Windows 7 64 OSs

NOTE: Windows NT® and Windows 98/ME OSs are NOT supported.

*MPLAB PM3 P/N 10-00359 does not support 64-bit drivers.
*MPLAB PM3 P/N 10-00398 supports 64-bit drivers.

IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and MPLAB PM3 will no longer be tested on Windows 98 or Windows ME OSs. MPLAB IDE and MPLAB PM3 may continue to work under these operating systems, but their operation will no longer be verified through testing.

3      HCS Support and Programming Information

As of MPLAB IDE 7.41, MPLAB 5.xx is no longer required to create SQTP files for the programming of HCS devices. SQTP file creation for HCS devices is now available by using the KeeLoq Plug-in. This component is offered during the MPLAB IDE Installation. When installed, the KeeLoq Plug-in becomes available under the Tools menu in the MPLAB IDE. Encoder, Decoder and Transponder options are offered on the KeeLoq dialog for the SQTP file creation.

4      Reference Documents

The following documents may be found on our website or MPLAB IDE CD-ROM:

·         MPLAB PM3 User's Guide                                       DS51464

·         Setting Up the MPLAB PM3 Poster                          DS51405

·         Programming Specifications for devices                  various DS numbers

·         Development Tools Selector

On-line help (Help>Topics) is also available for this tool:

·         Programmers>MPLAB PM3                                     hlpMPLABPM3.chm

5      What's New in v8.91

None.

6      Repairs and Enhancements in v8.91

None.

7      Autorun

To automatically load an environment into the PM3 at power-up, Autorun can be used on a memory card (PM3Card).  Create a file called autorun.run at the root directory level of the memory card and include these commands in the file:

 

LOAD <Environment Path>\<Environment Name>

END

 

For example, if an environment has been saved on the memory card (PM3 Card) called PIC18F4321 in directory PIC18F4321, the following lines should be placed in the autorun.run file:

 

LOAD PIC18F4321\PIC18F4321.pm3

END

 

Note: Make sure there are no leading or trailing spaces on the command line or the command will not be recognized.

8      Known Problems

The following is a list of known problems. For information on common problems, error messages and limitations please see “Troubleshooting” in the online help file for MPLAB PM3 (hlpMPLABPM3.chm).

8.1       Loss of Communication

·         The MPLAB PM3 does not timeout if a communication error is received. If this occurs, turn the power to the MPLAB PM3 off then on. Disable and then Enable the MPLAB PM3 within MPLAB IDE.

8.2       MPLAB IDE

·         Once address ranges are set in the Programmer Settings dialog, Program tab, the settings will stay set and not revert to default values after an operation.

8.3       GENERAL

·         IMPORTANT: In ICSP mode, MPLAB PM3 will default to program in low voltage mode on the PIC12(L)F1xxx/16(L)F1xxx enhanced mid-range devices.

Note: In MPLAB IDE versions prior to 8.66, the default was to program in high voltage mode. In MPLAB IDE version 8.66 the default was changed to low voltage.

In order to program the LVP (low-voltage programming) fuse on the device, you must be in high voltage mode. To set the high voltage mode using MPLAB IDE, access the ICSP settings dialog located under PM3 Programmer Settings, Voltages Tab and check the “Use high voltage on MCLR” checkbox. OR, you can set the high voltage programming setting on the MPLAB PM3 in Standalone Mode. To set this in Standalone Mode, select the enhanced mid-range device family and device, then select All Functions>Settings>ICSP Settings>ICSP Programming Mode>High Voltage on MCLR. This setting can be saved in environments created in MPLAB IDE v 8.73 or later.

Please refer to the device’s programming specification for more information on changing the LVP fuse.

·         Memory Areas, Program Memory Range, Preserve EEProm and Erase All Before Program options set on the MPLAB PM3 hardware for Stand Alone use cannot be controlled by the MPLAB IDE, Visual PROCMD or PM3CMD, nor are they saved with Environments.

·         With PIC18F8xxx devices set in boot block processor mode, memory past the boot block range is not accessible. Therefore, verifying after the boot block range will fail in this mode. In microprocessor mode, all of program memory will fail a verify. In some devices, configure and ID memory will also fail.

·         For ICSP of PIC18Fxx20 and dsPIC30F devices, you must connect the AVDD and AVSS pins for the devices to program.

·         ICSP is not currently supported for Serial EEProm devices.

·         ICSP programming of dsPIC devices may require a short cable and/or impedance matching resistors for optimal speed. On some of the smaller pin count devices, crosstalk between the PGD and PGC does not allow the device to get into ICSP mode. Keep the cable length under 6 inches and/or place 100ohm resistors in-line with the PGD and PGC signals to minimize the crosstalk.

·         The OS Suite that has been released with the MPLAB IDE version installed on the workstation must be used for programming. If not, conflicts can occur between the MPLAB IDE and the MPLAB PM3 firmware detected on the programmer.

·         If you encounter a problem with downloading an MPLAB PM3 BIOS using a USB connection, under certain conditions, an MPLAB PM3 may lose communication with the PC during the BIOS download. If this occurs, the MPLAB PM3 screen will appear blank upon restart. At this point, the new BIOS may be downloaded using MPLAB IDE through a Serial Port connection.

·         Programming issue on the PIC16C5X – The PM3 may have difficulty programming the 16C5X device. To work around this issue, place 0.1uf cap on both Vdd to ground and Vpp to ground. In addition, connect the device ground pin to the system ground located on the socket module. Turn the socket module over and find connector P1. The bottom pin on the inside edge of the connector is ground. Make sure to ground the associated ground pin of the device to system ground.

·         There are some cases in which PIC16C5X devices failed to program due to excessive current sink at Vpp/MCLR pin. Please refer to ETN 28 found on www.microchip.com for further information.

·         For the PIC18F14K22 family, MPLAB IDE debug/programming tools will not work below 1.9v. The work-around is to run the device above 1.9v.

·         PIC18F2520 MCUs: Table Read Protect (EBTRx) will not work unless Code Protect (CPx) is enabled. Also, once Table Read Protect is enabled, you cannot perform a Verify on the protected block.

·         Although support has been added to Preserve Program Memory Space for the MPLAB PM3/MPLAB IDE, it has not yet been implemented for Visual PROCMD, PM3 Stand-alone mode, or PM3CMD.

8.4       dsPIC33FJxxGSxxx Devices

Programming issue on dsPIC33FJxxGSxxx devices (dsPIC33FJ16GS502, dsPIC33FJ16GS402, dsPIC33FJ16GS504, dsPIC33FJ16GS404, dsPIC33FJ06GS101, dsPIC33FJ06GS202, dsPIC33FJ06GS102) – MPLAB PM3 may experience difficulty programming dsPIC33FJxxGSxxx devices using PM3 socket modules. This is due to the high current required by these devices during the initial power-up and the current limit from the PM3 socket module pin drivers.  A work-around for this limitation is to program these devices in-circuit (ICSP), using the PM3 14-Pin ICSP connector. For more information on the ICSP connector/configuration, please consult the MPLAB Online Help.


8.5       SSRs (System Service Requests)

Key

Summary

Device Affected

PM3-499

PM3 does not support Low Voltage programming for PIC18F devices.

PIC18F devices with Low Voltage mode

PM3-489

There is no Verify function for SST devices.

SST25VF020B, SST25VF040B, and other SST devices

PM3-485

SST devices are currently not able to be programmed on older MPLAB PM3s, P/N 10-00359.

SST25VF020B, SST25VF040B

PM3-475

Hex file that may not contain all addresses imported into PM3CMD may differ from what is imported into the MPLAB IDE.
Workaround - Import the file into MPLAB IDE and perform a File Export of the hex file from MPLAB IDE to obtain a formatted, linear hex file.

PIC18F4520

PM3-457

For the PIC32 devices, several options are not saved in the PM3 environment, such as 'Preserve Flash on Program', and the Boot flash. After loading the environment, please enable the appropriate selections on the PM3 stand-alone until this issue can be repaired.

 

PM3-443

Preserve Flash on Program' and Preserve EEPROM on Program' selection in the MPLAB 8 IDE PM3 Settings box does not transfer to the MPLAB PM3 in standalone mode.

PIC16F1783, but possibly others

PM3-410

After performing a READ of the device, CODE PROTECT ALL message is always displayed on the PM3 stand-alone screen, even though the device is not code protected

PIC18F45K80, PIC16F877A and possibly others

PM3-370

A warning message appears"PM3 is unable to read device - Current operation is aborted", after creating an environment if the device is not connected when the environment is loaded.

any devices

PM3-362

PM3CMD does not save the '/w' setting to an Environment

 

PM3-352

PM3CMD -Exporting a Serial EE memory hex file results in a hex file that is separated by 0x00

All SEE memory devices

PM3-348

When performing LVP programming, programming fails when using power from target

PIC18F2520

PM3-329

PIC16F877A can't range program Program Memory when "erase all before programming" is unselected.

PIC16F877A

PM3-324

PIC17C756 and PM2 socket module AC174007 (with adapter) does not work with this device. It reads back wrong values.

PIC17C756

PM3-308

dsPIC33FJ256GP710 fails to program from MPLAB IDE. Returns "Serial Receive Error" when using USB.

33FJ256GP710

PM3-293

PIC16F88 does not erase/blankcheck when voltage settings are set below 4.5V.

PIC16F88

PM3-275

There is an increase in time required to load an environment from PM3 CARD from 3 seconds to 13 seconds.

 

PM3-274

When loading environment from MPLAB PM3 card settings such as Memory Regions, Memory Range do not get loaded properly into MPLAB IDE.

All

PM3-264

AC164322 Rev 1 socket is missing resistors R2 adn R6 on bottom of socket.
This only applies to 10-00367-22 rev 2 if there are no 0-ohm resistors at R2 and R6.
Workaround:
1. Locate the Reference designators R2 and R6 at the bottom of the socket.
2. Solder 2 0-ohm (0805 size) resistors across the R2 and R6 pads.
3. Clean excess solder.

PIC16F886

PM3-208

PIC18C252 programmed hex file differs from read hex file due to unimplemented bits being read as 1's instead of 0's. This should not cause any problem since these bits are ignored during programming.

PIC18C252

PM3-174

Verification bar doesn't fill during verification

25LC256

PM3-164

Programming Memory is getting erased regardless of the state of the 'Erase before Programming' checkbox.

PIC18F87J50 family

PM3-162

The PIC16F88 is not erasing below 4.5V.

PIC16F88

PM3-158

SIGN' configuration bit reported after an Erase of a code protected device and attempting to verify that it was blank

PIC18F86J15

PM3-151

Load Environment: No error message displayed if the environment selected does not match the device selected in the MPLAB IDE

Any

ICD2-81

ICSP mode fails to program/verify the PIC24FJ128GA010 device when user code does runtime flash erase /write operation. It appears the device is executing code before the full programming cycle is complete.

For PIC24F devices during a programming/verify operation (or subsequent verification operation) of user code that performs self-writes and/or self-erases to program space, a verify sequence may fail if the code execution occurs within the first execution cycles following reset.

Workaround: Place a delay in your code before the code section that performs the self-write and/or self-erase.

The specific delay value may need to be adjusted, but 100 ms would be a conservative value to start out with. Here is a C language example that illustrates the workaround:

 

int main (void)

{

 

    // Place 100 ms delay here before any self-write/self-erase code

 

        .       .       .

        .       .       .

        .       .       .

 

}

PIC24

28427

PIC18F24J10:  Fails to Erase/Program (Revision 2 motherboard issue). If you experience this Revision 2 Motherboard problem, please contact Microchip for hardware replacement.

PIC18

28011

The PIC17Cxxx devices cannot be programmed under ICSP with all MPLAB PM3 ICSP Monitor cards or FPGA versions found in the MPLAB PM3. For example, if either the ICSP Monitor card or FPGA versions are improper, attempting to enable the MPLAB PM3 with a PIC17C756A will yield the following error messages:

MPLAB IDE

The current hardware configuration does not support ICSP for PIC17C devices. Please contact Microchip support for the latest MPLAB PM3 hardware revision. The following sockets are supported:

AC164301

AC164308

AC164319

Stand Alone Mode - MPLAB PM3 Display

Your MPLAB PM3 does not support PIC17CICSP. Please contact Microchip for a hardware upgrade.

PIC17

26990

 The PIC10Fxxx, PIC12F510 and PIC16F506 support programming down to 2.25 volts. Programming below this voltage may cause the program memory and calibration data to be improperly programmed.

PIC10/12/16

25254

 Some devices require that a .1uF bypass capacitor be placed from the VDD pin to the VSS pin of the device to successfully program the device. If programming failures still arise, try increasing this value incrementally to a maximum of 10uF. The parts affected are:

PIC16F737      PIC16F747     PIC16F767       PIC16F777

PIC16F818      PIC16F819     PIC18F1220     PIC18F1320

PIC18F2220    PIC18F2320   PIC18F2331     PIC18F2431

PIC18F2410    PIC18F2420   PIC18F2455     PIC18F2480

PIC18F2510    PIC18F2515   PIC18F2520     PIC18F2525

PIC18F2550    PIC18F2580   PIC18F2585     PIC18F2610

PIC18F2620    PIC18F2680   PIC18F4220     PIC18F4320

PIC18F4331    PIC18F4431   PIC18F4410     PIC18F4420

PIC18F4455    PIC18F4480   PIC18F4510     PIC18F4515

PIC18F4520    PIC18F4525   PIC18F4550     PIC18F4580

PIC18F4585    PIC18F4610   PIC18F4620     PIC18F4680

PIC18F4682

PIC16/18

9      Important Notes

9.1       Checksums

Please see the MPLAB IDE readme for any important updates on checksums.

9.2       MCP Devices

MCP devices are now supported. Hex files for MCP CAN extenders can be created in two ways using the .ASM and .INC files available from Microchip FAEs, CAEs or applications engineers:

1)     Select the appropriate values for each parameter in the .ASM file and assemble it using MPASM or MPASMWIN. The potential values for each parameter are listed in the .INC file. Import the resulting hex file and program the device.

OR

2)     Choose values for each parameter in the GUI (graphical user interface) and generate the hex file. Import the resulting hex file and program the device.

9.3       PIC17CXXXX ICSP Support

For support of PIC17CXXXX ICSP, the following is required in your MPLAB PM3:

·         Minimum ICSP Monitor card version 2.83

·         Minimum FPGA version 1.11.00

Contact Microchip for the procedure to update the FPGA version and the required file.

9.4       USB Port Setup

Installation and setup instructions are dependent on your operating system. Open the appropriate file for your OS in a web browser and follow the instructions to install the driver(s).

Note: If you have accidentally installed the Windows OS default driver, these instructions will direct you to how to "clean" your system first before installing the correct driver(s).

Notes:

Win 2000/Win XP/Win Vista/Win 7

Find detailed instructions at:
C:\Program Files\Microchip\MPLAB IDE\MPLAB PM3\Drivers\ddpm3.htm

Basic instructions are as follows:

  1. Install MPLAB IDE v8.40 or higher.
  2. Insert a communication board (standard or high-speed) into the MPLAB PM3.
  3. Connect the MPLAB PM3 to a PC USB port using a USB cable.

4.     Follow the “Found New Hardware Wizard” to install the drivers (software):

a.     automatically for Win 2000/XP.

b.    manually for Win Vista. The drivers are located in:
C:\Program Files\Microchip\MPLAB IDE\ MPLAB PM3\Drivers

 

Win XP 64/Win Vista 64/Win 7 64

Find detailed instructions for Win XP 64 at:
C:\Program Files (x86)\Microchip\MPLAB IDE\Drivers64\XP64\ddxp64.htm

For Win Vista 64:
C:\Program Files (x86)\Microchip\MPLAB IDE\Drivers64\Vista64\
ddvista64.htm

For Win 7 64:
C:\Program Files (x86)\Microchip\MPLAB IDE\Drivers64\Win7_64\
ddwin764.htm

Basic instructions are as follows:

1.     Install MPLAB IDE v 8.14 or higher (for Win XP/Vista 64) or v8.43 or higher (for Win 7 64).

  1. Insert a communication board (standard or high-speed) into the MPLAB PM3.
  2. Connect the MPLAB PM3 to a PC USB port using a USB cable.

4.     Follow the “Found New Hardware Wizard” to install the drivers (software) manually.
C:\Program Files (x86)\Microchip\MPLAB IDE\ Drivers64

 

IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and MPLAB PM3 will no longer be tested on Windows 98 or Windows ME OSs. MPLAB IDE and MPLAB PM3 may continue to work under these operating systems, but their operation will no longer be verified through testing.

Win 98
C:\Program Files\Microchip\MPLAB IDE\MPLAB PM3\Drivers\ddpm398.htm

Win ME
C:\Program Files\Microchip\MPLAB IDE\MPLAB PM3\Drivers\ddpm3me.htm

10   Socket Support

Refer to the Development Tools Selector (DTS) located on the Microchip web site (www.microchip.com). Select "Development Tools" under "Design", and then select "Development Tool Selector" under "Resources" from the MPLAB IDE CD-ROM you used to install MPLAB

11   Tested SD/MMC Cards

Microchip is continuing to test MMC and SDMMC cards from various manufacturers. At the time of this release, we suggest using cards greater than 16 MB.

The following SDMMC and MMC cards have been tested with the MPLAB PM3:

Manufacturer

Type

Size

ATP

SD

1 GB

Generic

SD

128 MB

Integral

SDMMC

64 MB

Kingston

SDMMC

32 MB & 128 MB

Kingston

MMC

64 MB

Lexar

MMC

32 MB

Lexar

SD

512 MB

PQI

SD

128 MB

PNY

SD

128 MB

PNY

SD

256 MB

PNY

SDMMC

256 MB

SanDisc

SD

128 MB

SanDisk

Ultra II SD

256 MB

SanDisk

SD

2 GB

 

Microchip does not support FAT32 and FAT12 formatted cards. MPLAB PM3 will reformat non-supported formats to FAT16.

12   Definitions

Image

An image encompasses all the information needed to program a device. MPLAB IDE first transfers an "image" to the MPLAB PM3 before it verifies or programs a device. In addition, when you read a device you are creating an image on MPLAB PM3 which later will get transferred to MPLAB IDE.

MPLAB PM3 Operating System (OS)

The MPLAB PM3 OS (aka Firmware) is the suite of machine code that allows the programmer to operate much like Windows is to your PC. MPLAB IDE will automatically alert the user when a new upgrade is available.

Environment

The MPLAB PM3 Device Programmer uses a new concept called an MPLAB PM3 Environment. An Environment is a snapshot of the current programming settings for a specific device. It contains all the necessary information to recreate the current programming state, including a binary image of the device’s memory data, links to an optional SQTP file, and specific part information. When an Environment is saved, a folder is created on the selected drive on a PC or on the removable MPLAB PM3 Card.

See the MPLAB PM3 User's Guide for more information.

13   Declaration of Conformity

We

Microchip Technology Inc.

2355 W. Chandler Blvd.

Chandler, Arizona 85224-6199

USA

hereby declare that the product:

MPLAB PM3

 

complies with the following standards, provided that the restrictions stated in the operating manual are observed:

Standards: IEC 61010-1 Safety requirements for electrical equipment for measurements, control and laboratory use.

Standards: IEC 61326-1  Electrical equipment for measurement, control and laboratory use - EMC requirements

Microchip Technology, Inc.

12 November 2003

 

Important Information Concerning the Use of the MPLAB PM3

 

Due to the special nature of the MPLAB PM3 programmer system, the user is advised that it can generate higher than normal levels of electromagnetic radiation which can interfere with the operation of all kinds of radio and other equipment.

To comply with the European Approval Regulations therefore, the following restrictions must be observed:

  1. The system must be used only in an industrial (or comparable) area.
  2. The system must not be operated within 20 meters of any equipment which may be affected by such emissions (radio receivers, TV´s etc.).