Just wanted to clear a few things up: Jtagulator basically is a "jtag finder". It doesn't do jtag. After you've found JTAG on a target, you need a JTAG dongle. It also supports variable voltage by some sort of command. I was saying my own dongle has this capability, but supports JTAG. Technically, I can perform a JTAG finding operation as well, but as it turns out, the push-pull drivers have issues at anything above 3.3v with current, so the design is probably going to change. At any rate, this was the similarity to JTagulator, it's variable voltage by command, eliminating the need to locate VREF.
2nd, technically, the design currently allows for 2 jtags instead of only one, but one modification only allows for port B to have JTAG, but has all of the variable voltage capabilities using SPI over port A and C as I've described (you enable control using a bit bang on C, then send a handful of SPI commands to select the voltage using port A.). Once the voltage is selected, then port A in the original variation could be reopened as a JTAG, but in the heartier driver variation, only port B is a JTAG. So I was hoping the example Andreas pointed me to would let me script, and bit-bang, the selected voltage with openocd. I may try the intermediate adapter approach if necessary, but just scripting that feature would eliminate quite a few headaches. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
