Total lack of results. JTAG timing or voltage level issues????

[HattonLe]

Having great difficulty in trying to get this CH341 adapter to work.
I have ISE 14.7 Xilinx Impact communicating with my Spartan3 FPGA board, so I know the hardware is reliable. I can read ChipID, download to the FPGA etc...I've measured the static voltages on the JTAG and they are either 0v or ~+3.2v magnitude sourced from a parallel port interface cable.
With the USB CH341 adapter connected its JTAG low voltages are 0.4v. All I get for the openocd output is at best the following (mostly I don't even see the lines with "JTAG tap:" in them.
Info : This adapter doesn't support configurable speed
Info : JTAG tap: xc9572.bs tap/device found: 0x11428093 (mfg: 0x049 (Xilinx), part: 0x1428, ver: 0x1)
Warn : JTAG tap: xc9572.bs UNEXPECTED: 0x11428093 (mfg: 0x049 (Xilinx), part: 0x1428, ver: 0x1)
Error: JTAG tap: xc9572.bs expected 1 of 2: 0x29504093 (mfg: 0x049 (Xilinx), part: 0x9504, ver: 0x2)
Error: JTAG tap: xc9572.bs expected 2 of 2: 0x09604093 (mfg: 0x049 (Xilinx), part: 0x9604, ver: 0x0)
Info : JTAG tap: xc3s1000.bs tap/device found: 0xffffffff (mfg: 0x7ff (), part: 0xffff, ver: 0xf)
Warn : JTAG tap: xc3s1000.bs UNEXPECTED: 0xffffffff (mfg: 0x7ff (), part: 0xffff, ver: 0xf)
Error: JTAG tap: xc3s1000.bs expected 1 of 1: 0x11428093 (mfg: 0x049 (Xilinx), part: 0x1428, ver: 0x1)
Error: Trying to use configured scan chain anyway...
Error: xc3s1000.bs: IR capture error; saw 0xffffffff not 0x1
Warn : Bypassing JTAG setup events due to errors

If I dab ground wire noise onto TDO the openocd reports random 0's and 1's, so its obviously can receive serial data.
A scope shows JTAG pin waggling from the CH341 so its trying to do something.
I'm about to look at the CH341 schematic \ datasheet to see what it says about voltage levels.
I've done lots of attempts with various different pin voltage combinations on the JTAG pins prior to running openocd and can find no pattern or combination that causes it to work (many initial combinations but none that works LOL), so perhaps its a timing issue as well?
Any ideas?