On 7/11/09 5:38 PM, "Xiaofan Chen" <xiaof...@gmail.com> wrote:
> On Sun, Jul 12, 2009 at 8:13 AM, Gary Carlson<gcarl...@carlson-minot.com>
> 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 believe svn-bisect would help us narrow where this change was implemented
>> and hopefully discover its origin. Unfortunately that utility does not work
>> properly on my Mac. Would you be interested in giving it a try?
>> Admittedly, I am not an expert with SVN, so there maybe easier tricks to do
>> this also. If there is, let me know.
>>
>
> 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.
>
> Google "jlink.c jlink_end_state(TAP_RESET);
> site:https://lists.berlios.de/pipermail/openocd-svn";
>
> 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();
>
> Google "jlink.c jtag_sleep(5000);
> site:https://lists.berlios.de/pipermail/openocd-svn";
> 2) r1616 by mlu
> + jtag_sleep(5000);
Sometimes I look for the more complex solution when there is an easier one
staring at me in the face. Google works too! :)
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.
Gary
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
