> Any suggestions? The problem has to do with end state.
In 2046 there was a global variable that subtly tracked what the end state should be. The end state is now decided by the code that invokes jtag_add_xxx_scan(). 2047 improved the API by removing this global variable in the JTAG layer. The evidence that the previous implementation is obtuse is of course that it is not easily evident what broke. The fix is to go through all the arm11_dbgtap.c and figure out what the end state should be for each queued command. There are two approaches to doing that, by code inspection or by reverting the change and running the app. You *would* believe that it should be possible to tell by code inspection in 2046 what the end state for each queued jtag command, but because the API was so obtuse, this is actually quite hard... -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
