Looking at your configuration scripts, they should *not* call init once they are implemented correctly.
> This does mean that omap3.cpu has to be enabled *before* it can be used (?) > On the other hand, in previous discussion, we had learned that init has to > be called *after* target create. But from some tests, it seems that init has > to be called *before* tapenable. Do you see the deadlock? How to resolve > this? We may need to iron out a few issues in OpenOCD... -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
