On 08/03/2011 11:45 AM, Dimitar Dimitrov wrote:
Simon,
Additionally, the device expects the speed in Hz, not kHz. I figured
this out be sniffing the USB traffic generated by IAR EWARM (using
Olimex' JLINK emulation driver). Since the default speed in the target
configuration file is 1000 kHz, this resulted in an effective speed of
1 kHz. This was probably the reason for the additional errors (JTAG
chain timeout (?), as in private email from Dimitar Dimitrov, the
original author of the driver and a former Olimex employee).
Good catch! JTAG chain timeout is expected in such circumstances.
Clocking the (presumably full) 4k buffer with 1kHz TCK frequency
easily exceeds the static timeout of 2 seconds, as currently defined
in the driver. Maybe timeout should be set dynamically based on JTAG
frequency?
Having the timeout dynamic sounds reasonable - operating at 1kHz JTAG
clock is not completely unthinkable (think about a device running on a
32.768kHz clock).
cu
Michael
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
