On 7/11/09 2:46 AM, "Spencer Oliver" <[email protected]> wrote:
>
>> Based on some initial testing it looks like the what the code
>> thinks the state of the JTAG state machine is verses what it
>> is inside the processor are two different things following reset.
>>
>> There are some other relevant details about this board worthy to note.
>> First this particular board only utilizes the system reset
>> (SRST) signal.
>> The test reset for the jtag port (TRST) is not physically
>> connected to the emulator port on the PCB. Without pulling
>> up the datasheet, I am going to assume therefore that
>> actuation of SRST is also yanking the TRST signal internally.
>>
>> In the process of debugging I temporarily commented out the
>> following steps in jlink_reset:
>>
>> // if (trst == 0)
>> // {
>> // jlink_simple_command(EMU_CMD_HW_TRST1);
>> // jtag_sleep(5000);
>> // jlink_end_state(TAP_RESET);
>> // jlink_state_move();
>> // }
>>
>
> 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?
>
> Cheers
> Spen
Apparently when I was composing the prior email I was a little too
aggressive with the double slashes and indicated that I commented out more
then I did in my testing. In reality I had the same three lines commented
out that you did since the first command is valid and needed. 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.
Gary
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
