Hello all, I'm building a board with an FT4232 on board to support UART access of various devices and reprogramming of the onboard ARM. I'd like to use SWD instead of JTAG for the ARM if possible, but I'm having a hard time finding documentation on how to hook up the 4232 so that it will be supported by OpenOCD.
The best guess I have comes from the KT-Link manual, which shows a multiplexer connecting the TDI/TDO pins to the TMS output (which is the standard pin used to connect SWDIO in a multilingual system). If I were to assume that I'll never use JTAG (I'm trying to keep the BOM for the board down, but I guess a MUX or a DPDT switch wouldn't break the bank), would it be reasonable to just connect the TDI/TDO pins together through resistors (a la converting MOSI/MISO to a bidirectional SPI line)? Or is there a more efficient way of connecting these up? I haven't delved into the guts of the MPSSE code in the FTDI code, so I don't know if there's a more efficient "direct" connection for this. Also, since this is a small, internal project and we're not about to acquire USB VIDs: if I leave the 4232 in "generic" mode (i.e. using FTDI's VID/PID), will I be able to "claim" the JTAG/SWD port dynamically with OpenOCD? I know my Olimex pod has an entry in FTDI's OS X driver that claims the serial port but leaves the JTAG port open, and I'm wondering if I'll run into the same problem. Many thanks in advance, - Dave ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
