Hi, the flyswatter.cfg says to report test with real interface here. I have Flyswatter rev B connected to Stellaris Launchpad (ARM Cortex M4F) as a test device (see output below).
It seems the processor is detected correctly (0x4ba00477), but afterwards it fails with "invalid ACK" message. Config used for target is here: http://pastie.org/9432092 (a bit modified stellaris script from older openocd) I tried searching for the meaning of the "invalid ACK" message, but couldn't decipher what is wrong. % openocd --file interface/ftdi/flyswatter.cfg --file target/stellaris.cfg Open On-Chip Debugger 0.8.0 (2014-07-30-14:23) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html WARNING! This file was not tested with real interface, it is based on schematics and code in ft2232.c. Please report your experience with this file to openocd-devel mailing list, so it could be marked as working or fixed. Info : only one transport option; autoselect 'jtag' adapter speed: 500 kHz Info : clock speed 500 kHz Info : JTAG tap: lm3s.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) Warn : Invalid ACK 0x6 in JTAG-DP transaction Info : accepting 'gdb' connection from 3333 undefined debug reason 7 - target needs reset Error: Target not examined yet undefined debug reason 7 - target needs reset Info : dropped 'gdb' connection Ondrej ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
