[bug #41637] avrdude timeout should be specifiable

[avrs-admin]

laci@monda.hu
Wed 19 Feb 2014 10:19:05 AM UTC

Currently avrdude timeouts after about 3 seconds when not being able to program the AVR.  I'd like to change this value to about 1 second (with a command line option, without recompiling avrdude).

The reason is that I'm programming an AVR through another AVR that can act like an USB to Serial bridge.  I've written a script to try to program the remote AVR with avrdude and if it doesn't succeed then kick the AVR into bootloader mode.  Being able to specify the timeout would make my script significantly faster.

This issue was migrated from https://savannah.nongnu.org/bugs/?41637

[mcuee]

This sounds like a niche use case but may still be kind of useful.

[MCUdude]

Currently avrdude timeouts after about 3 seconds when not being able to program the AVR. I'd like to change this value to about 1 second (with a command line option, without recompiling avrdude).

OP didn't specify which programmer he or she is using? My AVRISPmkII exits immedeatly if no target is detected. However, -c arduino takes several seconds before throwing avrdude: stk500_recv(): programmer is not responding. I'll assume OP is using -c arduino?

[MCUdude]

Currently, there's no way to interactively change the serial timeout delay specified in ser_posix.c and ser_win32.c.

avrdude/src/ser_posix.c

Line 53 in affe4cb

long serial_recv_timeout = 5000; /* ms */

avrdude/src/ser_win32.c

Line 39 in affe4cb

long serial_recv_timeout = 5000; /* ms */

[stefanrueger]

I'll assume OP is using -c arduino?

If that is the case, then a workaround would be to use c urclock. This programmer exits much faster than -c arduino. Seeing that the issue is from 2014, and was underspecified then with not specific PR/solution, I suggest closing it.

[mcuee]

Okay, I will close this now.