How to Use E-PGM+ ③
We are explaining ABOV’s Universal Programmer, E-PGM+, in a series in the order below. In this episode, we will explain ‘E-PGM+ error messages and troubleshooting’ that is the third content in the list:
① Connection Multiple E-PGM+
② E-PGM+ hardware features
③ E-PGM+ error messages and troubleshooting
The following two links lead to the first and second contents of the above list, respectively:
How to use E-PGM+ ① Connection Multiple E-PGM+
How to use E-PGM+ ② E-PGM+ hardware features
E-PGM+ error messages and troubleshooting
E-PGM+ displays how a program is progressing, on its TFT-LCD screen. By referring to this information displayed on the screen, you can process your program more easily with E-PGM+.
For the faulty device, you can solve the problem and determine the current status of the device by referring to the error message.
For the simple problems of E-PGM+, you can use the troubleshooting list.
E-PGM+ Error Message
- This section describes all error messages that can be displayed on the TFT-LCD screen of E-PGM+.
Table 1 shows the error messages and the details corresponding to each error message.
Table 1. E-PGM+ Error Messages and Details
1) No-device ID
- E-PGM+ reads the Device ID that is connected to it at the initial operation. However, if the Target B/D is not connected or it cannot communicate normally with the Device, E-PGM+ displays ‘No-device ID’.
Therefore, if you see this message on the screen, you need to make sure that E-PGM+ is properly connected to the Device and that the device is a good product.
2) No DPID
- This error message applies only to 32-bit MCUs. Each 32-bit MCU has a Device ID, and E-PGM+ displays ‘No DPID’ when it fails to read the Device ID during the initial connection to the device.
3) Power Check
- This message is about the power output of E-PGM+. E-PGM+ outputs a voltage of 3.0V or 5.0V and checks if it is output as intended. If the output voltage is different, E-PGM+ displays ‘Power Check’.
E-PGM+ can be damaged if the power source of the Target B/D and the power source of E-PGM+ collide when connecting the Target B/D and E-PGM+. This error message is displayed to warn you of this situation.
4) Trim Chk.
- Each device has its own Device ID and Trim Data. E-PGM+ first checks the Device ID of a device and then checks the Trim Data.
E-PGM+ outputs the ‘Trim Chk Fail’ message if the Trim Data of the device is different. Usually Trim Data is importantly used to determine whether the device is normal or abnormal and without it, fatal defects may occur in mass production.
When the ‘Trim Chk’ message is displayed, you cannot use the device and must report it to ABOV’s Technical Support.
5) Erase Failed
- Before programming a device using E-PGM+, all data in Flash memory of the device must be erased. Once E-PGM+ erases the Flash, it checks and determines whether the Flash is cleared.
Errors may occur if data is programmed in the Flash where data is not properly erased. In this case, the ‘Erase Failed’ message is displayed.
6) Verify Fail
- After programming the Flash, E-PGM+ reads the Flash area and compares the Flash data with the original data. If the Flash data is different to the original DATA, E-PGM+ displays ‘Verify Fail’.
In the case that incorrect values are programmed due to environmental factors or device characteristics, further analysis is required.
7) Ext Power
- During programming, E-PGM+ supplies power to the device . If power is already supplied to the device, E-PGM+ cannot progress programming. Therefore, E-PGM+ tells you whether power is supplied to the target device. If ‘Ext Power’ message is displayed, you need to check and cut off power of the device.
8) Debug Power Request
- This error message is output when the device is in Reset state, if the Reset IC is connected to the device that is on board. In this case, the voltage level of the Reset IC needs to be adjusted to release the Reset of the device.
9) CPU Reset
- This error message applies only to A31G112/123 that are 32-bit MCUs. Check the LVD level first, and then set the VDD level to be higher than the LVD level.
E-PGM+ Trouble Shooting
- E-PGM+ troubleshooting provides methods to solve various problems that may arise when installing or executing E-PGM+ on your PC.
- If you see the System Error message shown below when executing the E-PGM+.exe file, copy the WDAPI1010.dll file that comes along with the execution file and paste it in the Cwindows folder.
2) No firmware found/Device file not found
- When executing the E-PGM+.exe file, the firmware folder and E-PGM.txt file are located in the same folder. If you want to execute the E-PGM+.exe file on your desktop, you need to use ‘desktop shortcut’.
3) USB driver
- If E-PGM+ doesn’t operate with the ‘No valid license’ message displayed in the Log window, you can solve this problem by following the steps shown below
1. Close E-PGM+ S/W
2. Disconnect USB line
3. Run USB_driver_unistall.exe (Version 1.7)
4. Delete C:WindowsSystem32driverswindrvr6.sys
5. Copy windrvr6.sys which is in the driver install files
64 bit : Copy x64windrvr6.sys to C:WindowsSystem32drivers
32 bit : Copy x32windrvr6.sys to C:WindowsSystem32drivers
You can download documents and materials related to E-PGM+ at the ABOV website linked below: