MPLAB Production Test Interface

I saw this from JasonK's signature. I could not find any other relevant information other than the short info from Microchip Direct. Any pointers?

MPLAB Production Test Interface
Cost: US$2500 per unit
 
The MPLAB PTI (Production and Test Interface) provides a programmatic (static DLL) and GDB-compliant command-line interface to MPLAB IDE debug tools for production or automated testing. Either code or scripts can access information from MPLAB PTI. The MPLAB PTI can also be deployed for unattended automatic batch debugging during product development.

There's currently not much documentation available for MPLAB PTI. Below is another description.

In some circumstances, it is either necessary or desirable to use an MPLAB IDE debug tool, such as an in-circuit emulator (ICE), from an application other than MPLAB IDE.  Frequently, this is in an automated test environment, where some testing application executes PIC® microcontroller code under the control of the debug tool in a prototype circuit board.  This type of environment requires streamlined, low-level programmatic access to the debug tool without the overhead and interference of the MPLAB IDE graphical user interface.  For such applications, the MPLAB IDE Debug Tool API provides the best solution.

A Microsoft® Windows® application interfaces with an MPLAB IDE debug tool through the MPLAB IDE Debug Tool API.  It accesses the API by linking with the Windows DLL that supports the required tool.  A different API, and consequently a different DLL, is provided for each MPLAB IDE debug tool, specifically MPLAB ICD 2, MPLAB ICE 2000, and MPLAB ICE 4000, MPLAB REAL ICE, and the MPLAB Simulator.  Although different, each API is essentially the same, in that they all have a set of analogous functions.

In addition to the basic debug-tool API, MPLAB PTI also includes a simple command-line interface to the debug tools.

DBTOOL command-line interface to MPLAB Debug Tools

        dbtool [drive:][path][filename] [/T:tool] [/D:device]

[drive:][path][filename]
        Specifies drive, directory, and HEX file that contains the program to
        be loaded onto the debug tool for execution.

/T
        Specifies the desired debug tool; currently, it may be either ICE2000
        or ICD2.  For example, to start the DBTool application using the ICE
        2000, type

                dbtool /T:ICE2000

        at the Window's command line.  This argument is optional, but, until a
        debug tool is specified using the TOOL command, the only commands that
        will not return an error are the DEVICE, HELP, and the QUIT commands.

/D
        Specifies the Microchip device that the debug tool will use.  The
        option must be the device name, such as PIC18f452 or dsPIC30f6014.
        For example, to use the ICD2 on a PIC18f4310, type

                dbtool /T:ICD2 /D:PIC18F4310

        Although this argument is optional, until the DEVICE command is used to
        specify the desired device, the only commands that will not return an
        error are the TOOL, HELP, and the QUIT commands.

Help is also available for the following commands:
        tool
        device
        load
        run
        step
        reset
        break
        clear
        pc
        read
        write

Type

        help [command]

 or

        [command] /?

to display the help for a particular command.

Hope this helps.

ORIGINAL: JasonK
In addition to the basic debug-tool API, MPLAB PTI also includes a simple command-line interface to the debug tools.

 
Thanks. Shouldn't the command-line interface be free? If it is free, it will help quite a lot.
 
If I were Microchip, I would give this whole thing free. Just my two cents.
 
And since this has been done, it is also easy to develop a command line programming interface to MPLAB ICD2. So many people have requested.
 
I do have a belief this stuff will be free in the future.