> So r1817 passed but r1822 does not. r1817-r1821 do not compile. > > There are a lot of changes to jtag.c file here between r1817 - r1822. > Anybody?
I've diffed 1817 and 1822 and I find nothing that could explain arm11 burst writes failing. It's quite puzzling. The only difference I could find by reading the code is timing changes, i.e. it happens to break between 1817 and 1822 on your machine + interface, but it would break somewhere else on another setup. If this is the case, then the code was *always* broken(i.e. not robust), it just happened to work. The other hint that you have found is that removing TAP_IDLE's will make the code work, i.e. the faster the code is, the better chance it is of it running. If *timing* is the only difference when removing/adding TAP_IDLE's, then this is another hint at a race condition. These next steps come to mind: 1. Verify assumptions. Are you *sure* 1817 work and 1822 fails? 2. Try to break 1822. Try adding usleep() delays around the code, e.g. to jtag_execute_queue(). -- Ø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
