On Sun, Jul 12, 2009 at 9:43 AM, Gary Carlson<[email protected]> wrote: >>>> I am seeing issues with the str9 using the jlink. >>>> The fix for that is to comment out: >>>> jtag_sleep(5000); >>>> jlink_end_state(TAP_RESET); >>>> jlink_state_move(); >>>> >>>> Going from the original jlink code i worked on i am not sure why these were >>>> added? >>>> >>> We appear to have the same identical experience then. >>> >>> I am wondering whether the remaining questionable code may have been a >>> temporary test for troubleshooting purposes that was not abandoned or >>> removed prior to generating a corrective patch for the real issue? That can >>> happen once in awhile. >> >> I do not know anything about svn-bisect. But I just used Google for >> 5 minutes to locate the svn commit for the above lines. >> >> 1) r1507 by Zach to fix J-Link reset >> https://lists.berlios.de/pipermail/openocd-svn/2009-April/000291.html >> + jlink_end_state(TAP_RESET); >> + jlink_state_move(); >> 2) r1616 by mlu >> + jtag_sleep(5000); > > Hmmmm!!! I wonder if this has any relationship to the first part of my V2 > patch that I recently addressed. If you recall I found that the j-link > dongle would ignore the first reset command intermittently immediately after > the USB session was started, but worked subsequently. I speculated that the > j-link dongle was doing something critical and dropped the ball on occasion > (probably a bug inside the dongle itself). The physical outcome I observed > if the reset didn't occur was that the JTAG port was messed up afterwards. > > I guess we will need to ask Zach or Oyvind about this one. Hopefully they > can shed some light on it.
Need to go back to this after the git-svn side topic. It seems to me this needs sometime to get fixed and may be not ready for 0.2 release... Still Spen could commit Gary's V3 J-Link patch to fix the problem for Windows users. https://lists.berlios.de/pipermail/openocd-development/2009-July/009438.html -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
