Can the ICP2(G3) keep the T_VDD output enabled after programming is completed? We need it to continuously supply VDD.
No, ICP2 family programmers always turn off all voltages after programming to prevent hot insertion. However, you can enable power again using specific ICP DLL functions after programming. Preset D/A of Vdd output: Icp2DaVolt(DA_VDD, ) Release RESET pin: Icp2PinState (T_VPP, PIN_Z, &dummy).Note: weak pull-down resistors are always connected (300K for I/Os, 160K for VPP) Turn T_VDD […]
PASS or FAIL 5VDC signal stays on until the next test. Is there a way to reset the device other than a 120VAC power cycle to where neither the PASS or FAIL light is on going into the next test?
You can use ICP DLL functions to turn off the LEDs after programming is completed: err=Icp2PinState(G3_GPF_OUT_PASS, PIN_LOW, &pin_state); //PASS/FAIL outputs err=Icp2PinState(G3_GPF_OUT_FAIL, PIN_LOW, &pin_state); //+err=Icp2PinState(LED_INT_PASS, PIN_LOW, &pin_state); //PASS/FAIL LEDs err=Icp2PinState(LED_INT_FAIL, PIN_LOW, &pin_state); //+err=Icp2PinState(G3_LED_PASS_EXT, PIN_LOW, &pin_state); //PASS/FAIL LEDs (ICP2GANG/COMBO) err=Icp2PinState(G3_LED_FAIL_EXT, PIN_LOW, &pin_state); //+
Why do I need to refresh the environment?
The IcpRefreshEnv() function may be invoked prior to programming to achieve maximum reliability. Note that the environment refresh or reload rate is approximately 1 MB per second.
How can I overwrite the number of boxes or channels defined in the icp01.cfg file for the ICP2-GANG(G3) or ICP2-COMBO(G3) programmer?
The following DLL functions can be used to configure and query the number of boxes and channels for ICP2-GANG(G3) and ICP2-COMBO(G3) programmers: – IcpGangNumberBoxesSet – IcpGangNumberBoxesGet – IcpGangChannelSet – IcpGangChannelGet Advanced Command Line sections in INI file: [Gang] GangNumberBoxesSet GangChannelsBox1 GangChannelsBox2 … GangChannelsBox16
We have two ICP2(G3) programmers installed in one PC and plan to program concurrently (in parallel), we would like to know any method to avoid queueing when programming concurrently?
(A) DLL use Rename icpdll.dll to icpdll1.dll, icpdll2.dll (any different name) and run each thread with its “own” DLL copy. No conflict occurs since every programmer gets its own COM number (B) Command Line use If you use ICP Command Line then you can’t rename the DLL since the EXE uses the original name, but you can […]
