I wonder if anyone had any success using either DirectC 2.2 or SVF files to program Actel PA3 devices. All my attempts are failing so far.
1) DirectC 2.2 compiled with VC2005 (adapted to Xilinx Cable III), had
1 time success from 100 attempts to program the part
2) playing SVF or XSVF files with Impact fail very quick, SVF doesnt even get as far as checking jtag IDCODE
3) custom SVF player also shows weird behaviour
Maybe try with the Amontec SVF Player + the Amontec JTAGkey (USB to JTAG Cable). Amontec SVF Player support Trailer Header and infinite Scan Length.
Note: if the IDCODE failed SOMETIMES this could mean you have a bad JTAG connection (between the Xilinx Cable III target board). Make sure to not route the TCK parallel to the TDI or TDO, we have the experience that this could infer to the stability of the JTAG FSM even if you run JTAG at very low speed. You could try to add a 100R resistor on TCK close to Target.
Almost sure your issue is not coming from the SVF file nor the Player, but from your JTAG signal integrity.
100% failure when trying with SVF file and impact
100% ok, when trying XSVF file and impact
100% failure when adding extra delay in RTI state (TCK IDLE NOT TOGGLING) in custom SVF player
100% ok when doing FAST playback in custom SVF player
3) DirectC a) once worked full programming cycle b) place of failure depends on the VC compile target (debug or release) the place of failure is constant, but rather soon in the file, ISP_entry command, after IDCODE check. the DirectC timing calibration value is dependant on the build target, so i assume some speed issue here
hardware currently in use
*) Amontec Chameleon with Xilinx JTAG fly-wire adapter
*) A3P250 on proto board, wire length from IC to JTAG pin < 10 mm for all connections
I cant use Amontec svfplayer it does NOT SUPPORT amontec Chameleon : ( for some time ago I purchased 3 pcs of FT2232 mainly to rebuild the jtagkey, but didnt ever bother doing it, so I dont have any jtagkey to test with :(
Please look above my observations, could you still assume it is signal integrity issue? The pass-fail depends on the time spent in RTI when TCK is not toggling, meaning there are no signal toggling at all! I am puzzled at least.
- directc 2.2 programmed 100% one time out of 150, 149 times fail very quick (first commands already)
- flashpro - FAIL (bad response for enter isp)
PCB2_a3p060
- directc 2.2 DEBUG Build, works 100% each time
- directc 2.2 RELEASE Build works maybe 1 of 10, when fails the enter_isp mode
- flashpro - works
so it does look like some problem related to the chip or wiring or powersupply, still little strange that the release-debug setting while compiling directC makes so big difference
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.