EdKeyes

Members
  • Content Count

    5
  • Joined

  • Last visited

Everything posted by EdKeyes

  1. Thanks again, @jpeyron! Everything makes sense now versus my logic probe. Again, for anyone running across this thread in the future, the appropriate OpenOCD configuration for the above info is: ftdi_layout_init 0x20e0 0x3feb This assumes an nSRST signal on GPIO2 which is initialized to inactive high, same as the existing default.
  2. Thanks, @jpeyron! I'm getting some confusing results when trying to apply these settings to drive the reset signal on GPIO2, though. Is there any chance that the OEn signals for this bank are actually active low (0 = output, 1 = input)? The ADBUS ones seem to be active high, but the GPIO lines aren't acting the same for some reason.
  3. Great, thanks! That indeed works just fine... the default config didn't turn on some of the needed OE signals. For anyone running across this problem in the future, the OpenOCD config corresponding to the above information is: ftdi_layout_init 0x00e0 0x00eb @jpeyron, would you happen to also know how the GPIO pins are mapped on ACBUS, particularly GPIO2 which usually controls the processor reset line?
  4. Yep, that's what I tried first. The configuration built into OpenOCD only gives me TCK output, with no other JTAG signals. I've been able to get at least TMS to show up by randomly tweaking some of those bits, so it seems to be an error in the FTDI driver config rather than a hardware problem with my board. The SMT2 support in OpenOCD apparently was written on the basis of a single post in a Russian forum, so it's not exactly authoritative. I'm hoping that Digilent can provide some definitive info for how things should be set up.
  5. I'm trying to get a board using the JTAG-SMT2-NC working with OpenOCD. There's supposedly existing support for it, but at the moment I'm only getting a TCK signal and no others out, so I suspect that the existing pin mappings for the FTDI driver are incorrect. Ideally I'd love to just get a copy of the SMT2 schematic to verify everything, but it doesn't seem to be publicly available. Short of that, would it be possible to know how the FTDI 232H signals are mapped onto the various outputs, i.e. ADBUS0 drives X, ACBUS5 tristates Y when high, etc.?