Not sure but according to [datasheet, section 3.3] the 2232 comes up by default in rs232 mode (unless configured otherwise in the eeprom) and [section 8.0 table 8.1] in rs232 mode pin 13 isn't pulled up.But why doesn't it do that at bootup already then? I'm missing something here, I guess.
I added the following code before sending the "bit-bang mode MPSSE" command, and the XC-1 seemed to behave well.Let me know if you get any further,
Code: Select all
# if defined( _XC1 )&&( 1 == _XC1 )
{
/* PROBLEM on XC-1:
Unlike XC-1A, the XC-1.FT2232D.ACBUS1 gates transistor Q12, enabling RESET_ to flow;
this resets the XS1 chip. This is obvious when LED17 (PLL_LOCK) extinguishes on setting
MPSSE mode. So pre-program upper byte output value (ACBUS0:3).
cmd=0x82 : set ACBUS0:7 dir and initial states - see FTDI 2232D datasheet 3.3, AN135 p:18 and AN108 table 2-1
0x82 = Configure data bits high-byte of MPSSE port
0x00 is initial state (GPIOH0:2=0, GPIOH3=x)
0x03 is direction (TRST_=out, RESET_=out, DEBUG=in, GPIOL3=in)
*/
jtag_system_reset_clear( );
}
# endif
Unfortunately I still read back 0xffffffff from the target registers, but this is probably something I've clobbered in the Win32 port...