OTA issue after secure boot flash

[qdwang]

Device: LILYGO T-Display-S3

I flashed my device with this config sdkconfig1.defaults.txt with secure boot.

Then I build the bin file with this config sdkconfig2.defaults.txt and do the OTA update.

After the successful update, the device is unusable like this.

---

Why adding one line CONFIG_LOG_DEFAULT_LEVEL_NONE=y in config can break the OTA update? Can this issue be fixed in future release?

[j0n4th4n-1410]

I broke 3 devices similar result when enabling secure boot and encryption, Internally the device works, but the screen does not display correctly. The last one worked well and when performing a factory reset it became unusable, in the same way when applying an update via OTA.

[qdwang]

@j0n4th4n-1410 Sorry to hear that. It seems the OTA function is not stable enough. The DIY Guide page should mention this I think.

---

I managed to get everything work by OTA updating the firmware to tag 1.0.33. Using stable release branch can reduce the probability to get screen issue I guess.