Troubleshooting; Error Codes - Microchip Technology Protouch2 User Manual

Protouch2 GUI User Manual
11 Appendix I

12.1 Troubleshooting

1. Please check if you have installed the VSM and WinUSB drivers before running
this tool using the CLI. Navigate to PT2_CLI folder and run this command as
administrator in CMD line for installing the drivers. Refer to "Protouch2 CLI User
Manual.pdf" for more details
>>pt2main.exe /i
2. If the MCHP hub is connected to a 3.0 Host controller , please check if you have
disabled power saving in the Hub using the device manager (Refer to GUI user
manual) or connect a USB device(like mouse or pen drive) to one of the
downstream ports to prevent the hub from going to sleep
3. If you are still having issues, please email the "PT2.log" file created in the same
directory as the tool to the Support contact mentioned above
Debugging failures can be done by analysing the log file generated which contains
the error codes as mentioned in Section 12.2. Please send the "PT2.log" file created in
the same directory as the application to Microchip for debugging.

12.2 Error codes

Error codes will be displayed in case of errors and the detailed description of them are
as follows
Error code
0x0000
0x0001
0x0003
0x0004
0x0005
0x0006
0x0007
0x0008
0x0009
0x0011
0x0012
0x0013
0x0014
0x0015
0x1000
0x1001
0x1002
MICROCHIP CONFIDENTIAL
Description
Success ; No Errors
The specified device was not found
Device handle passed to the API is not valid
API of the WinUSB library failed
System reboot is required
Error in installing VSM filter driver
Operation successful but requires reboot
Bin file size is invalid
Error while reading cfg/bin file
Error in installing WinUSB driver
Invalid argument
Error when VSM Filter is not available
Error when application does not have admin rights
Error if VSM command is failed due to power state of the
device
Could not load the binary file
Reading from SPI flash failed
File size did not match
Page 34