Øyvind Harboe wrote: > Looking at your configuration scripts, they should *not* call init > once they are implemented correctly.
Do you like to give any hints how to implement them correctly and what do you think is wrong with them? We talk about http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/board/ti_beagleboard.cfg http://svn.berlios.de/svnroot/repos/openocd/trunk/src/target/target/omap3530.cfg >> 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... What do you propose OMAP3 people to do until this is done? Stay with an older version? E.g. 1606 which Magnus uses? Many thanks Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
