On Tue, Jul 12, 2011 at 7:04 PM, Steve Bennett <ste...@workware.net.au> wrote:
> Although this problem is fixed in the latest libftd2xx1.0.5,
> that version is not yet publically available.
> Without this fix, the ftd2xx aborts with a fatal error and
> is thus unusable.
>
> Signed-off-by: Steve Bennett <ste...@workware.net.au>
> ---
> src/jtag/drivers/ft2232.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/src/jtag/drivers/ft2232.c b/src/jtag/drivers/ft2232.c
> index 38ead56..2e0495d 100644
> --- a/src/jtag/drivers/ft2232.c
> +++ b/src/jtag/drivers/ft2232.c
> @@ -2260,8 +2260,7 @@ static int ft2232_init_ftd2xx(uint16_t vid, uint16_t
> pid, int more, int* try_mor
>
> if ((status = FT_GetLatencyTimer(ftdih, &latency_timer)) != FT_OK)
> {
> - LOG_ERROR("unable to get latency timer: %lu", status);
> - return ERROR_JTAG_INIT_FAILED;
> + LOG_WARNING("unable to get latency timer: %lu", status);
BTW, this will produce a warning for 64bit Linux.
src/jtag/drivers/ft2232.c: In function 'ft2232_init_ftd2xx':
src/jtag/drivers/ft2232.c:2263: warning: format '%lu' expects type
'long unsigned int', but argument 6 has type 'FT_STATUS'
mv -f .deps/ft2232.Tpo .deps/ft2232.Plo
> }
> else
> {
> --
> 1.7.5.1
--
Xiaofan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
