BPWin includes a variety of error messages to help debug problems with the software and hardware, the following table lists these error message to aid in fault finding.
Programming Errors
Error 3: Cannot reset hardware.
The software cannot establish communications with the programmer. Here are some suggestions:
Be sure the programmer has proper power and that the green PASS LED is on. Since the programmer will do an automatic Power On Self Test (POST) upon start-up, it could be that the programmer failed the test and has
signalled
the software into the default DEMO mode. If this should happen, please contact
Support .
The programmer may be damaged. Try another computer and/or USB port and see if it works there. See Calling for Technical
Support .
Error 5: Hardware time-out.
This error message is generated when the software is waiting on a response from the programmer while executing a command and the programmer does not respond within the expected amount of time. This error may result from several causes. You may be experiencing communication errors (see Error 3: Cannot reset hardware above). There may be a bug in the software for this particular algorithm (see Error 10: Error in programming algorithm below). See also the Self-Test section.
Error 6: Wrong model number.
See Error 3: Cannot reset hardware above for possible causes.
Error 9: Programmer execution error.
The programmer failed an internal consistency check. See Error 3: Cannot reset hardware and Error 5: Hardware time-out for possible causes.
Error 10: Error in programming algorithm. Please call technical support.
The software has detected an internal error. You should contact BPM Microsystems to report the error. You may need to obtain a software update. See the Calling for Technical Support section.
Error 11: There is no data in the buffer. You must load a file or read a chip.
A command tried to read data from the buffer to program or verify a chip, but nothing has been loaded into the buffer yet or the buffer was recently cleared.
Error 14: There is no chip in the programmer site.
Be certain that your chip is inserted correctly. If the chip was inserted correctly, remove it and run the hardware self-test to be sure your programmer is functioning correctly (Programmer Diagnostics). A defective chip may cause this error. When using an auto handler, the socket may not have closed or a connection between the programmer and the socket may be disconnected.
Error 15: The chip is not inserted in the programmer site correctly.
The continuity test determined that the chip in the programmer site does not have continuity on all the proper pins. You should examine these pins carefully. Possible causes are:
A bent pin.
The chip is not in the proper position in the programmer site.
The chip has a different number of pins than the chip selected.
The algorithm selected has an * (asterisk), indicating it requires an adapter, but you did not use the adapter, or vice-versa.
The socket is dirty and not making a connection.
The wrong socket module or adapter is being used for this part.
The device may be a very low power device that is not properly detected by our continuity methodology. If so, please let us know.
Note:
It is not easy to get continuity on an LCC device in a PLCC socket. If you are trying to do that, then you may need to add a spacer between the chip and the lid in order to apply the proper force to the device pins. The best solution is to purchase an LCC socket module that does not require any such
jury rigging
.
LCC devices will not work in the auto-eject sockets designed strictly for PLCC devices.
Error 16: The chip is inserted
backwards
The chip has passed the continuity
tests,
but appears to have the GND and Vcc pins improperly placed in the socket. If the DIP, SOIC, or TSOP device is not actually inserted
backwards
and the LCC, PLCC, or QFP is not accidentally rotated, then the device is probably defective. Try a known good device.
Error 18: Temporary file error.
Our software’s virtual memory manager is trying to store data that is currently not needed in RAM to the disk. The program was unable to create a temporary file or the disk is full. You should make sure you have plenty of disk space (the larger the data files, the larger the requirement for temporary disk space). The program does take advantage of EMS memory if you have an expanded memory manager installed. This is much faster than using the disk for temporary swap space.
Error 21: Cannot program.
Not able to program the device in the programmer site. See the Errors While Programming tab.
Error 22: Cannot erase.
Not able to erase the device in the programmer site. See the Errors While Programming tab.
Error 23: Invalid electronic signature in chip (device ID).
The chip may be damaged or the chip manufacturer may have changed the programming algorithm without notifying us. See Error 25: Invalid electronic signature in
chip
(manufacturer ID) below.
Error 24: Invalid electronic signature in
chip
(algorithm ID).
The chip may be damaged or the chip manufacturer may have changed the programming algorithm without notifying us. See Error 25: Invalid electronic signature in
chip
(manufacturer ID) below.
Error 25: Invalid electronic signature in
chip
(manufacturer ID).
Many of the new EEPROM based PLDs (such as all the GALs) have electronic identifiers that specify the manufacturer, the device code, and the proper programming parameters. The most common cause of this error is if you have selected the wrong manufacturer for the particular part you are using (for example, you may have a National Semiconductor part in the programmer site and a Lattice part selected). It is also possible that your chip has a newer ID than your software revision supports.
Error 26: Device is not blank.
A blank check may have been performed via the Blank or Program command. The device in the programmer site is determined to have programmed data. Possible causes are:
The part needs to be erased longer.
The device was previously programmed and cannot be erased (OTP EPROMs and fuse-link PLDs).
The wrong algorithm was used.
Error 27: Device is not secured.
An attempt to secure a device was made, but it failed. See Errors while Programming section.
Error 28: Data in
chip
does not match buffer.
A verify operation was performed to see if the chip and the buffer have the same data, but there is a difference in the two patterns. The verify may have been performed via the Verify or Program command. The verify will not show where the difference occurred but the Compare command will show you all the discrepancies. Here are some reasons why a device may fail to verify:
The part was secured.
The part was programmed with a different pattern.
The part has not yet been programmed.
The device was incorrectly programmed by a different system.
The wrong algorithm is selected.
The chip was not properly erased before programming (this would be caught by the blank check if it was enabled).
The wrong adapter is being used.
The device is not inserted correctly and you have the continuity test turned off or you ignored its error messages.
The device is defective.
Error 31: Database file is invalid. The .EXE file is corrupted.
The .EXE file you are executing has been corrupted. You should get a new copy from BPM Microsystems.
Error 32: Sorry, algorithm not found. Please call technical support.
The .EXE file you are executing has been corrupted. You should get a new copy from BPM Microsystems.
Error 33: You must re-select the chip you want to program.
The device was selected before establishing communications with the programmers, perhaps prior to turning on the programmer or before switching to a different programmer. Simply re-select the chip and the error should not reoccur.
Error 36: You must properly install the correct socket module.
The software interrogates the socket module before each operation to determine the correct mapping for the algorithm selected. You will get this error if:
There is no socket module installed.
The socket module installed does not support the device you have selected (for example, you have selected a 20 pin device and you have a 28 pin PLCC socket module attached).
The socket module installed is not supported by the version of the software you are using.
Use the latest version.
The pinout has not yet been defined for this package type.
Error 39: Device already secured.
The device cannot be legitimately programmed, read, etc., because it has been secured. If it is a PLD it may still be functionally tested using the Test command.
Error 40: No test vectors present.
The file you loaded did not contain any test vectors. Therefore, the Test command will not be executed.
Error 44: Internal error. Please call technical support.
The software detected an internal inconsistency. This may be caused by the computer not performing correctly.
Error 46: AFS software required to execute this function.
This is a function that is available to users that have purchased the Advanced Feature Software only. In order to use the chosen
function
you must buy the AFS upgrade.
Error 47: Self-test failed. This unit may need service. Please call technical support.
The self-test (Programmer Diagnostics) has detected a hardware problem. If this should happen, double-check the fidelity of the cable connections and try again. If you are still having trouble, please contact Support.
This error can occur when performing Programmer Diagnostics during the calibration verification procedure and
answering
NO to the question "Is the socket module installed?" regarding the requirement of having
a SM48D
/SM48DB installed before continuing.
Error 48: Cannot Unprotect.
An attempt was made to unprotect a sector and failed. See Errors while Programming.
Error 49: Cannot Protect.
An attempt was made to protect a sector and failed. See Errors while Programming.
Error 57: You must purchase support for this device to use it.
The device that you selected is not supported in the default device set for this programmer.
Error 70: The buffer data cannot be used to program this device.
You loaded a file type that is not a valid option for the currently selected device. Re-select the device and load the buffer again.
Result Code Table
-1
| Internal BPWin error (firewalled unhandled exception). Send contents of blackbox.html to BPM Microsystems technical support.
|
0
| Success
|
1
| Undefined
|
2
| Unknown result code.
|
3
| Cannot reset hardware.
|
4
| Excessive current detected. The protection circuit has shut off the power.
|
5
| Hardware timeout.
|
6
| Wrong model number.
|
7
| Program break.
|
8
| This function requires a programmer to be attached therefore the DEMO does not support it.
|
9
| Programmer execution error.
|
10
| Error in programming algorithm. Please call technical support.
|
11
| There is no data in the buffer. You must load a file or read a chip.
|
12
| Cannot create buffer.
|
13
| This software is incompatible with your hardware (revision level).
|
14
| There is no chip in the socket.
|
15
| The chip is not inserted in the socket correctly.
|
16
| The chip is inserted backwards.
|
17
| Out of memory.
|
18
| Temporary file error. Use SET TMP=c:\ or similar command to specify correct directory.
|
19
| You cannot load a file this large.
|
20
| Command failed.
|
21
| Cannot program.
|
22
| Cannot erase.
|
23
| Invalid electronic signature in chip (device ID).
|
24
| Invalid electronic signature in chip (algorithm ID).
|
25
| Invalid electronic signature in chip (manufacturer ID).
|
26
| Device is not blank.
|
27
| Device is not secured.
|
28
| Data in chip does not match buffer.
|
29
| Secured successfully.
|
30
| Command aborted.
|
31
| Database file is invalid. The .EXE file is corrupted
|
32
| Sorry, algorithm not found. Please call technical support.
|
33
| You must reselect the chip you want to program.
|
34
| A failed device in a "Sets and Banks" job session is being retried.
|
35
| A failed device in a "Sets and Banks" job session will not be retried.
|
36
| You must properly install the correct socket module or daughter-card.
|
37
| Illegal bit detected.
|
38
| Functional test failed.
|
39
| Device already secured.
|
40
| No test vectors present
|
41
| Error reading file
|
42
| Error in writing file
|
43
| Error in macro file
|
44
| Internal error. Please call technical support.
|
45
| Hardware requires calibration. Please call technical support.
|
46
| AFS software required to execute this function.
|
47
| Self test failed. This unit may need service. Please call technical support.
|
48
| Cannot Unprotect.
|
49
| Cannot Protect.
|
50
| Device's sum does not match sum specified in AFS/Options.
|
51
| The maximum failures specified for this session has been reached.
|
52
| DynCall stack underflow.
|
53
| DynCall stack overflow.
|
54
| Device is not blank. (Interchangeable with failure code 26)
|
55
| Invalid single byte identifier in chip.
|
56
| Some device pins are shorted together.
|
57
| You must purchase support for this device to use it.
|
58
| The device outputs were not tristated.
|
59
| Excessive leakage current detected.
|
60
| The demo period for this programmer has expired. Please call technical support.
|
61
| Concurrent programmer did not initialize properly.
|
62
| Device operation in a socket is "Active".
|
63
| A socket is "Idle" during a job session.
|
64
| This code is currently not in use.
|
65
| Concurrent unit has the wrong socket module.
|
66
| Concurrent unit has the wrong technology adapter.
|
67
| Concurrent unit has the wrong BIOS.
|
68
| Concurrent unit has the wrong number of pin drivers.
|
69
| Concurrent unit is not available.
|
70
| The buffer data cannot be used to program this device. Please load the correct file.
|
71
| The recorded macro was too long for the macro buffer. Please call technical support.
|
72
| Concurrent site has finished programming all of it's devices
|
73
| This code is currently not in use.
|
74
| The automated socket module is open.
|
75
| The device has been inserted into the socket.
|
76
| The device has been removed from the socket.
|
77
| Concurrent unit has the wrong amount of extended memory.
|
78
| This code is currently not in use.
|
79
| The socket is not empty.
|
80
| Excessive current detected. The protection circuit has shut off the power. (Interchangeable with failure code 4).
|
81
| We have exceeded the last serial number. We must end the session.
|
82
| This code is currently not in use.
|
83
| Internal error: One or more of the call back functions pointers are NULL.
|
84
| Internal error: The initialization of the engine failed.
|
85
| Error reading file.
|
86
| Error writing file.
|
87
| The file type is wrong. The file cannot be read/written correctly.
|
88
| This code is currently not in use.
|
89
| This code is currently not in use.
|
90
| Internal error: The specified site is out of range.
|
91
| Attempted to use a non-concurrent programmer as a concurrent programmer.
|
92
| There is no status available for the specified site.
|
93
| This code is currently not in use.
|
94
| The address in a buffer is out of range.
|
95
| This code is currently not in use.
|
96
| This code is currently not in use.
|
97
| This code is currently not in use.
|
98
| This code is not in use.
|
99
| This code is not in use.
|
100
| This code is not in use.
|
101
| This code is not in use.
|
102
| Ganged Socket Failed
|
103
| Ganged Socket Passed
|
104
| This code is not in use.
|
105
| This code is not in use.
|
106
| This code is not in use.
|
107
| This code is not in use.
|
108
| This code is not in use.
|
109
| This code is not in use.
|
110
| This code is currently not in use.
|
111
| This code is currently not in use.
|
112
| This code is currently not in use.
|
113
| This code is currently not in use.
|
114
| Use Select to reselect the device prior to using this command.
|
115
| This code is currently not in use.
|
116
| This code is currently not in use.
|
117
| Can't open a file on the disk.
|
118
| This code is currently not in use.
|
119
| This code is currently not in use.
|
120
| This code is currently not in use.
|
121
| This code is currently not in use.
|
122
| This code is currently not in use.
|
123
| This code is currently not in use.
|
124
| This code is currently not in use.
|
125
| This code is currently not in use.
|
126
| This code is currently not in use.
|
127
| This code is currently not in use.
|
128
| This code is currently not in use.
|
129
| This code is currently not in use.
|
130
| The mem file stream name should not be empty.
|
131
| The device must be selected from the device list.
|
132
| This code is currently not in use.
|
133
| This code is currently not in use.
|
134
| Device is not encrypted.
|
135
| Failed to use entire data pattern to verify device.
|
136
| This programmer model does not support multi-site configurations.
|
137
| This device does not support empty socket test.
|
138
| The socket module does not support insertion counters.
|
139
| Gang Pass/Fail Mask Mismatch
|
140
| The programming site is ready.
|
141
| Software License Expired
|
142
| This code is currently not in use.
|
143
| This code is currently not in use.
|
144
| The serialization program is missing or invalid.
|
145
| Devices should not be present in the slave sockets.
|
146
| Cannot read device.
|
147
| This code is currently not in use.
|
148
| Memory Integrity Check Failed.
|
149
| A device was detected in a socket.
|
150
| Could not load BP file.
|
151
| Software feature not licensed on all sites.
|
152
| Software feature not licensed on some sites, registration expired on other sites.
|
153
| The initial operation in the job failed; retrying.
|
154
| The quantity number should be between 1 and 2,147,483,647.
|
156
| Site overheated and will be disabled.
|
157
| The External Serialization Process indicated to fail the device.
|
158
| Programmer site does not have enough concurrent mode memory for this operation.
|
159
| The device failed to initialize properly.
|
160
| The device failed to respond properly to the algorithm exit sequence.
|
161
| This code is not in use.
|
162
| Ground transistor failure detected. One or more ground transistors is not connected to ground. This could be due to a reverse-inserted device or a failure of a ground transistor on ANY of the connected socket cards. Note that even if a single ground transistor on a single socket card does not read back correctly, power will be shut off on all sockets to protect the devices, socket cards, and programmer from damage. Please ensure that all devices are properly inserted and try the operation again. If failures persist, stop the device operation, remove all devices from the sockets, and run programmer diagnostics to verify that all ground transistors on the socket cards are functioning properly.
|
Error Whilst Programming
Specific warning messages will appear wherever applicable when choosing a device. These messages, pertaining to the type of chip being chosen, are designed to assist you with helpful information such as if the chip needs a third party adapter or requires the use of a special head, when the chip needs to be placed a certain way in the socket module, etc.
The warnings listed below are generalized warning messages to alert you of a problem that should be resolved before continuing.
Warning: Device code is not correct
When using the ID Check or ID electronic identifier option. The programmer automatically checks the electronic identifier of your memory chip. If your chip does not read out the identifier expected by the software, there are four possible actions that can be taken:
- The Select option will try to select the appropriate device/algorithm. Use it if you feel the wrong device may have been selected.
- You can replace the chip and use Retry.
- The command can be aborted.
- You can ignore the identifier and proceed.
Occasionally, a semiconductor manufacturer will change the die on a chip to add the identifier. If this happens, the software may expect the identifier to be present in your chip. If you are using an old chip made before the identifier was added, you will get an error message. It is safe in this case to ignore the warning message. Under the device command, you can un-check the box next to the ID Check or ID operation to disable the electronic identifier option.
Warning: Device is not blank
This warning message will only appear when using the Program command with the Blank Check before programming operation, if running on a non-concurrent programmer or on a concurrent programmer and Quantity set to 1. You are given the option to Abort, Retry, or Ignore message, which allows you to try another chip before proceeding or to go ahead and program data on top of the data that may already be in the chip.
Warning: Device has been secured
You will get this message only on devices that have the ability to read the security bit prior to performing any other operation. Thus, you may get this when trying to read some PLDs and some microcontrollers. You are given the option to Abort, Retry, or Ignore, which allows you to try another chip before proceeding or to go ahead and read the erroneous data from the chip.
Warning: X fuses in buffer and Y fuses in chip
You will get this message when you try to program a PLD that has a different number of fuses than the number of fuses loaded in the buffer. This is a precautionary measure designed to help you keep from accidentally programming the wrong JEDEC file into a chip.
This message may not always be the best advice. For example, if you have a GAL22V10 (5892 fuses) selected and a PAL22V10 (5828 fuses) JEDEC file loaded. It is okay to program this JEDEC file into the GAL22V10 because they are 100% architecturally compatible; however, the GAL22V10 has 64 additional fuses allocated as the UES (see Devices/UES command for more details). If you ignore this message on the first operation, you will not receive any more warnings on the subsequent programming operations.