However, hvepromcmd (in it's step one) has different values for pins 25, 26 and 7:
#define DESC_TEST_MCS48_PON \
"Connect your multimeter negative (black) probe to pin 20 on the MCU socket.\r\n" \
"\r\n" \
"Check the following pins on the MCU socket are within 5% of the specified values: \r\n" \
"\r\n" \
"40: VCC = +5V\r\n" \
" 7: EA = +5V\r\n" \
"25: PROG = +5V\r\n" \
"26: VDD = +5V\r\n"
Measuring quite liberally built MCS-48 prommer, actual voltages are much closer to UI (4.2V).
If this is error in hvepromcmd then using it can lead user to determine that board is faulty.
Step one of MCS-48 test sequence has following entries in closed source UI version:
40: VCC = +5V 26: VDD = +4.2V 25: PROG = +4.2V 7: EA = +4.2V
However, hvepromcmd (in it's step one) has different values for pins 25, 26 and 7:
Measuring quite liberally built MCS-48 prommer, actual voltages are much closer to UI (4.2V).
If this is error in hvepromcmd then using it can lead user to determine that board is faulty.