When OpenOCD starts up slowly or abnormally, the IDE will report an error.

[laomaolaile]

When OpenOCD starts up slowly or abnormally, the IDE will report an error.

Is it possible to consider allowing the OpenOCD startup timeout period to be configurable by the user?

[ilg-ul]

This might be a possibility, but I'd be also interested to know the reason why openocd takes so long to start.

[TommyMurphyTM1234]

Similar issue here?

• Is it possible to set the timeout when gdb server (such as openocd) starts? #585

[djanovy]

Just a guess, but would adding the set remotetimeout work?

[ilg-ul]

I'm not an openocd user and I don't have any experience with these timeouts, so I don't know if this configurable timeout is helpful or not.

If you do, please suggest a PR and I'll consider it.

[TommyMurphyTM1234]

Just a guess, but would adding the set remotetimeout work?

I don't think so. That helps when OpenOCD is up and running but, for some reason, slow to respond to GDB Remote Serial Protocol commands and needs more time before timeouts much in.

What this issue is referring to is where Embedded CDT is trying to launch OpenOCD in the first place but, for some reason, it takes "too long" to launch, and Embedded CDT times out, gives up and reports an error.

I have no idea what the timeout used here is, if it's some general timeout in Eclipse/CDT or specific to the Embedded CDT OpenOCD launch support, and if it's configurable via eclipse.ini or some other configuration file even if not via the GUI.

[laomaolaile]

My scenario is Eclipse installed on a workstation, and there may be some software interception in between, such as antivirus software. In this case, there may be a timeout situation. Or openocd could have been directly killed