Hi, On Wed, Aug 20, 2014 at 9:26 AM, Paul Fertser <fercer...@gmail.com> wrote:
> > In fact running openocd is much easier: > > openocd -f board/sheevaplug.cfg > > thanks for that hint. I've been using the longer commandline since this was verbatim how The Internet told me it should work when my plug was bricked. And since it did in fact work that way with 0.7 and I was more in panic mode (the plug is my internet gateway and general purpose home server) and not exactly ready for learning new things I've never bothered to investigate what part of the commandline was actually needed to get openocd running. > (no need for full path and -s). You should be able to get it running > with > openocd -f board/sheevaplug.cfg -c "adapter_khz 100" > > If you have a reasonable explanation of what the default adapter freq > should be, I can add it to the config. > > 0.7 tells that: " [...] sheevaplug_load_uboot Info : clock speed 2000 kHz Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2) Info : Embedded ICE version 0 Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit ^C " so 2000 kHz is probably what should go into the config. > HTH > Yes, it did. Many thanks for your support! Andreas
