Am 05/26/2011 09:12 PM, schrieb Paul Claessen: > In April (2011) I built openocd version 0.5.0-dev-00858 and used it > successfully with an Olimex OpenOCD JTAG Tiny. > I recently built version 0.5.0-dev-00882 and I now get the following > error: > > Error: An adapter speed is not selected in the init script. Insert a > call to adapter_khz or jtag_rclk to proceed.in procedure 'init'
> I would argue that if you remove a concept of default values and > thereby BREAK working systems and turn them form working systems into > failing systems, then, IMHO, no matter how elegant and architecturally > correct your 'concept removal' was, you violated the extremely > important idea of backward compatibility and you have, for all > practical purposes, introduced a bug. > > We're now having a system, that used to work fine, that no longer > works and gives me (just a simple user) some very vague hint about > adding a call somehow somewhere without further details as to > parameters etc. > I hope someone can reverse all this. > > In the mean time, can someone provide me with some more detailed > instructions on where and how exactly to add this call? The adapter_khz and jtag_rclk commands are described in chapter 8.4 of the manual (openocd.pdf). If you are using one of the config files provided with OpenOCD, then these need to be fixed - however, you don't tell which config file and which target you are using, so I can only guess. If you use your own config file, you have to expect some breakage both on development versions and new major releases. Backward compatibility is a nice goal, but it can hamper progress and produce layers of cruft in the code, so there are situations where it is best to enforce some change and keep the code clean. cu Michael
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
