Hmm, I didn't observe that at all. I wonder if that's specific
to the "recover" procedure, or whether other power cycle sequences
would do the same thing?
This has nothing to do with the recover procedure,
this always happens if I power cycle the target hardware.
I compiled with --enable-ft2232_libftdi, did you use ftd2xx?
Regardless, note that the action you're prompted to do is not just a
power cycle ... it's "power cycle Stellaris chip, then restart OpenOCD."
So one *could* argue the segfault is just fortune's way to make sure
you really follow the second half of those instructions... ;)
You are right, I didn't follow the second part of the instructions exactly,
but then I was forced to to so :)
It could be more fortune to stop openocd automatically at the end of the
procedure.
After the procedure the user-interface reacts very slow, to enter a shutdown command needs some
patience.
regards
Arne
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
