On Sun, Mar 01, 2015 at 04:52:00PM +0100, Uwe Bonnes wrote: > I have some F411 nucleo board that I run battery powered. The reset line and > some other lines between the stlink and the target go to none 5 volt > tolerant lines of the STLink cpu and draw substantial battery current when > the stlink is not USB powered. A nucleo config with "reset_config none" will > work with both the modified and unmodifies nucleo board, while "reset_config > srst_only" will work only for the unmodified board.
So basically you have a custom board based on F411 nucleo, and since it's custom, it's reasonable that you might need additional configuration on top of the nucleo board config, so you can source it and then use "reset_config none". > Another situation is with using the STLink from nucleo or discovery to go > off board to another CPU. "reset_config srst_only" as given with most > configs, will require another jumper wire, while "reset_config none" as > default doesn't need that wire. srst_only can appear only in board config, so this is not relevant here, you're not using a ready-made board config when you connect stlink to another CPU. > So I don't buy the "it's usually more reliable" argument :-) You can't connect to a sleeping SoC without SRST, you can't reset other on-board devices without srst. "reset_config none" is default, just as you want it :) srst_only appears in some board configs where it should work nicely. Do you know of any counter-example? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
