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' (This was also reported for a J-Link build, but it seems to be a more generic issue: see: https://lists.berlios.de/pipermail/openocd-development/2011-May/018922.html ) An answer was given that stated “You have to specify the JTAG communication frequency, there no longer is any concept of a "default" frequency.” (See: https://lists.berlios.de/pipermail/openocd-development/2011-May/018923.html ) 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? Kind regards, ~ Paul Claessen
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
