>/ I'm not looking for something that works in all circumstances. I just
/>/ want it to be the *same* across all interfaces.
/>/
/>/ The correct long term solution would be to have *no* default speed
/>/ and just put up an error message if the script doesn't specify it.
/>/ IMHO.
/For me the correct is :
1. -init- fix the adapter jtag interface to a default frequency as 100kHz.
2a. close the JTAG interface if the scripts did not surcharge the JTAG
frequency, or set the new frequency wanted by the script.
2b. try to detect the maximum working frequency and continue the JTAG interface.
With this, we do not need to call any JTAG_ fn (upper level) from the adapter
JTAG driver (lower level). Also, this avoid tones of big spagethi and make the
all more robust.
... at the initialization of the adapters ;-)
Also, we could think to add the JTAG frequency when initializing the JTAG
interface as JTAG_interface->init(100);
>/
/>/ >/ So I think having no default and forcing the user to specify a value
/>/ />/ might be the way to go.
/>/ /
/>/ Agreed. If we could have that patch first and not go the detour of
/>/ a fixed default across all interfaces, then that would be
/>/ my choice too.
/The JTAG adapter do not need to know if the core.c is happy or not with the
JTAG frequency coming from a script or from anywhere. The JTAG adapter just
want to know what JTAG frequency to work on.
>/ Patch anyone?
/
Regards,
Laurent
http://www.amontec.com/
Amontec JTAGkey-2 : High speed USB JTAG interface
http://www.amontec.com/jtagkey.shtml
Regards,
Laurent
http://www.amontec.com/
Amontec JTAGkey-2 : High speed USB JTAG interface
http://www.amontec.com/jtagkey.shtml
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
