• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 844 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

XDS100v1 with FT4232H

i5rovi
Prodigy 40 points

Hello,

I am making XDS100v1 with FTDI 4232H chip. I got to the D Flip Flop Q (OE) and CLK signals.

In the original version of XDS100v1 these are connected to ACBUS-2 and ACBUS-3 of the FT2232D chip. FT2232D has 12 bits on A bus (ADBUS 0-7, ACBUS 0-3), but FT4232H has only 8 bits on A bus (ADBUS 0-7).

My questions:

1. On what FT4232H ADBUS pins should I connect D Flip Flop signals Q and CLK ?

As for TRSTn, I suppose it stays on ADBUS 4.

EMU0 and EMU1 use ADBUS 5-7 but I don't need EMU signals and would gladly put Q and CLK on some of these 3 pins.

2. How to "tell" the FT4232H that Q and CLK are on those pins i.e. is the driver for XDS100v1 with FT4232H same as for XDS100v1 with FT2232D ?

3. Do PID/VID values and Device Name String stay the same?

Thanks

  • 0
    TI__Prodigy 390 points

    The XDS100 emulators use an FT2232 device, not an FT4232 device. 

    So no matter how you hook it up, the software will not work as is, since you would have to program the second port of the FT4232 differently than the way the uper half of the 16-bit port in the FT2232 is programmed.

    If you are writing your own driver code, you can just hook them up the the lower 4 bits of the B port on the FT4232, and then you would write the software to access the bits according to how you hooked them up.

    You can't use the ADBUS5-7 pins for CLK and Q for the same reason, the current software driver expects those pins to be for EMU0 & 1 and would have to be modified if they are something else.

    I don't think there is anyway to "tell" the driver you are using an FT4232, because it was never written to understand that device or any other pin configuration.

    Sorry