On 07/31/2014 01:35 PM, Andreas Fritiofson wrote: > Actually, it might be that TDI is not driven and is floating high. The scan > chain verification would not notice but of course the first real scan would > make > no sense to the target.
You are probably right about the TDI. I've tried three another debugger-target configurations: - Flyswatter + Proxmark3 (Atmel AT91SAM7S256) - works - Flyswatter + Tiva Launchpad (EK-TM4C123GXL) - works - J-link + STM32F2 - results in "invalid ACK" (I don't physically have TDI pin this board - it's just for SWD I guess - it's known to work with ST-Link v2, though) Great work, thanks. BTW for anyone googling proxmark3 setup in the future here is the link - https://brmlab.cz/_media/project/proxmark3-jlink.zip Ondrej ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
