-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/11/2010 09:53 PM, Spencer Oliver wrote: > On 11/05/2010 18:22, Øyvind Harboe wrote: >> So should we just apply this patch you think?
Possibly limiting the revision to <= B1. I don't have access to a later revision chip, and I will most likely never get that since we've decided to switch to the STM32 because of the inferior ethernet peripheral in the LM3S. The STM32 has other shortcomings, of course. Let me know if you want me to provide another patch. > Do not have any tempest silicon to test, but it sounds as if they forgot > to fix this old bug. > > Tobias, > Can you confirm that the srst pin is actually getting asserted/released? Yes. Verified using oscilloscope. > Another test is to hold the reset button down then run openocd, after a > couple of seconds release the reset button. I don't understand what I should look for. If I press reset before starting openocd and release it 2 seconds after openocd is started, openocd start up normally. If I release it 3 seconds after starting openocd, I get this: srst_only separate srst_gates_jtag srst_open_drain Info : clock speed 500 kHz Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Command handler execution failed Warn : jtag initialization failed; try 'jtag init' again. /Tobias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkvqlwAACgkQoVlA9AKQ7+xt6wCfa0w5tjSzhUW1X43TlfaUQaDM xDcAn1k4BPVYp+FnISSaj3TGIAdruYnQ =doNd -----END PGP SIGNATURE----- _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development