Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] No rollback when migrating from [202210.01-LTS] #126

Open
Fienberber opened this issue Jan 30, 2025 · 1 comment
Open

[BUG] No rollback when migrating from [202210.01-LTS] #126

Fienberber opened this issue Jan 30, 2025 · 1 comment

Comments

@Fienberber
Copy link

Fienberber commented Jan 30, 2025

Hello,

I'm migrating from to the esp-aws-iot [202406.01-LTS] from [202210.01-LTS].
The previous integration was working properly so I know this is not an AWS issue.

We are using an ESP32C3 on our board.

Using the example works great. But I have issues while transitioning the devices from the old method.
I think there is an issue with the NVS. After the first boot on the firmware using esp-aws-iot [202406.01-LTS], the OTA flags are at ESP_OTA_IMG_NEW.

This prevent proper response to AWS and retry the OTA. The device loop OTAs indefinitely.
To fix this, I added custom flags to set the flag as ESP_OTA_IMG_PENDING_VERIFY if needed.

My issue now is with the rollback feature. If I OTA a bad firmware (crashing before partition validation) the board restart on the same partition.

During my tests, flashed using esp-aws-iot [202406.01-LTS] and transitioning to the same version, the rollback function works great.

Somewhere the version migration does something to the NVS but I can't find where.

Thanks in advance for you help.

@ig15
Copy link
Member

ig15 commented Jan 31, 2025

Thanks @Fienberber for bringing up the issue, we will look into it and get back to you shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants