Am 06/10/2011 09:33 AM, schrieb Laurent Gauch:
>/
/>>/ >/ Do you have any other ideas on what should be done on ft2232_quit()
/>>/ />/ except rtck, hi-z, div5..? I can prepare a patch, or Peter will as I
/>>/ />/ can see he is already working out the subject :-)
/>>/ /
/>>/
/>>/ What problem is setting pins to a default state on exit supposed to
/>>/ solve? Are we sure this is what we want? If I make openocd pull the
/>>/ reset
/>>/ line and then quit openocd, I'd expect the target to remain in reset.
/>>/ If I
/>>/ quit openocd while the target is running, I'd expect it to keep on
/>>/ running.
/>>/ How would that work if we make this change?
/>/ What do you mean by PULL?
/>/ If you close the openocd, we have to put both SRST and TRST in High-Z
/>/ . That's the normal case, any other case are specific to a custom
/>/ debug procedure.
/Why *do* we have to do that?
If I quit OpenOCD, I expect the target to stay in the same state as before.
If it was in reset, I expect it to stay in reset and not start some code
uncontrolled.
Yes you're right Michael regarding the state of the TARGET.
Did you already have needed to have SRST to be assert low at the end of
the openocd to force the SYSTEM RESET on the target board ?
If yes, putting systematically all signal to High-Z at the output of the
dongle could be a trouble.
But I am not sure it is the 95% of debugging/programming case.
Regards,
Laurent
cu
Michael
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
