It seems to be a HTTP/1.1 vs HTTP/1.0 issue.

In this example file , modifying this line of code:
sprintf(http_request, "GET %s HTTP/1.1\r\nHost: %s:%s \r\n\r\n", EXAMPLE_FILENAME, EXAMPLE_SERVER_IP, EXAMPLE_SERVER_PORT);

to

sprintf(http_request, "GET %s HTTP/1.0\r\nHost: %s:%s \r\n\r\n ...

Oops! Didn't the last reply until now.

Thanks for the info. Unfortunately, LXD doesn't place nice with udev rules, but that's a minor inconvenience.

Hello there,

I'm trying to understand why the OTA process halts for roughly 60 seconds after it successfully downloads a new binary. And, if possible, can I reduce this halting time? Below is a snippet of my terminal output, and the point at which the program halts for a literal minute. Thank you ...

Ok ... it took some time, but I figured it out.

I was having problems due to three distinct issues
A) I didn't realize that OpenOCD needed the D2XX FTDI API
B) D2XX as a user-space API conflicts with the kernel-space driver that my Linux OS automatically loads upon connecting the WROVER-KIT, so I ...

Thanks for the quick reply.

I tried the same command with sudo, but the same issue persists

sameer@testWROVER:/opt/gnuarmeclipse/openocd-esp32$ sudo ./src/openocd -s ./tcl -f ./esp32.cfg

Open On-Chip Debugger 0.10.0-dev-g1bc90a1 (2017-06-08-00:39)
Licensed under GNU GPL v2
For bug reports ...

I'm having the same issue. Nothing is connected to the board besides the shorting blocks (jumpers) at
USB 5V
JP8: TMS, TDO, TDI, TCK
JP11: RX & TX
JP14: CTS & RTS

Console output:

sameer@testWROVER: /opt/gnuarmeclipse/openocd-esp32$ ./src/openocd -s ./tcl -f ./esp32.cfg

Open On-Chip Debugger 0 ...