I am attempting to make a factory .bin image using

make factory_bin

I get the following error:
IOError: [Errno 2] No such file or directory: 'D:/msys32/home/Jeff/esp-at/build/download.config'

Where do I get the download.config file?

I have tried every which way I can think of but still cannot get the esp-at to compile. I've followed the readme file to the letter but something always breaks. This is my latest output. Makefile:36: There is no module_config/module_wroom-32,Using module_config/module_esp32_default /home/Jeff/esp/es...

***** SOLVED ******

My flash programmer had SPI mode set to QIO instead of DIO

I'm sure the address are correct, I've use the same setup before. And now it has happened on a second unit. This occurred after I attempted to downgrade from V1.2.0.0 to V1.1.0.0 using the OTA function I used the command AT+CIUPDATE=0,"V1.1.0.0" and it did finish with the final response of +CIUPUDAT...

I have somehow managed to brick my ESP32. I have tried loading versions 0.10, 1.0, 1.1, 1.1.1, 1.1.2, and 1.2 of the command set be no matter the version, this is what happens at boot. ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x...

Does anyone know the proper format for the filename in the command string?

AT+CIUPDATE=<ota_mode>[,<version>]

If I want to upgrade to version 1.1.0.0, what should be in the <version> field?
I have tried "1.1.0.0" and "V1.1.0.0" and anything else I could think of.

Thank you for the reply but that really does not help answer my question.
I need to know if there is a away to connect to a server that supports only TLS1.2 using the at command set. I
If the at commands do support tls1.2, what version added that support?

We are currently using the ESP32-WROOM-32D module with AT Commands V1.1.3.0. Our customer is preparing to change their servers to TLS 1.2. Will this module work with TLS 1.2 and if so could anyone direct me to instructions? There are a few thousand installed and updating the AT Command set is not pr...

Thanks for the help.
I just needed to add the HTTP/1.1 200 OK and it is working.

That is the only thing I send and it works fine for Android and PC devices.
What information would need to be in the header?