I started working with s3s a couple months ago.
At work I have access to a: ESP32-S3-DevKitC-1 v1.0 (WROOM-1) N8R2
I recently bought myself a ESP32-S3-DevKitC-1 v1.1 (WROOM-2) N32R8
ota_mqqt example with esp-idf 4-4 and 202012.04-LTS did not work with my newer chip.
I didnt mind this, assumed I needed switching to esp-idf 5.0 for WROOM-2 variant since it was the latest stable release.
However now we are moving our projects to esp-idf 5.0 and with 202210.01-LTS and again older chip (WROOM-1) can successfully complete the demo but the newer chip (WROOM-2) cant finish the demo. It can download the file, but refuses to boot to it.
For some reason WROOM-2 bugs out in version checking but WROOM-1 doesnt.
Down below are the screenshots from the failure:
I switched a lot of configuration options to make it work in WROOM-2, but failed.
I do not want to disable version checking. Also it is not the root of the problem since the older chip works with default configs from the example.
It's very frustrating since I lost a 1.5 workday on this and I thought I could work remotely during my upcoming vacation with my personal chip but apparently I cant.
I started working with s3s a couple months ago. At work I have access to a: ESP32-S3-DevKitC-1 v1.0 (WROOM-1) N8R2 I recently bought myself a ESP32-S3-DevKitC-1 v1.1 (WROOM-2) N32R8
ota_mqqt example with esp-idf 4-4 and 202012.04-LTS did not work with my newer chip. I didnt mind this, assumed I needed switching to esp-idf 5.0 for WROOM-2 variant since it was the latest stable release.
However now we are moving our projects to esp-idf 5.0 and with 202210.01-LTS and again older chip (WROOM-1) can successfully complete the demo but the newer chip (WROOM-2) cant finish the demo. It can download the file, but refuses to boot to it. For some reason WROOM-2 bugs out in version checking but WROOM-1 doesnt.
Down below are the screenshots from the failure:
I switched a lot of configuration options to make it work in WROOM-2, but failed. I do not want to disable version checking. Also it is not the root of the problem since the older chip works with default configs from the example.
It's very frustrating since I lost a 1.5 workday on this and I thought I could work remotely during my upcoming vacation with my personal chip but apparently I cant.