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

Partition Verification after OTA (AEGHB-967) #146

Open
3 tasks done
graineri opened this issue Jan 29, 2025 · 4 comments
Open
3 tasks done

Partition Verification after OTA (AEGHB-967) #146

graineri opened this issue Jan 29, 2025 · 4 comments

Comments

@graineri
Copy link

graineri commented Jan 29, 2025

Checklist

  • Checked the issue tracker for similar issues to ensure this is not a duplicate.
  • Provided a clear description of your suggestion.
  • Included any relevant context or examples.

Issue or Suggestion Description

Does ESP Mesh Lite mark the OTA partition as valid after boot?

We are doing that manually but sometimes we are failing to obtain the partition state as ESP_OTA_IMG_PENDING_VERIFY because it has already been marked as ESP_OTA_IMG_VALID. In those cases we see this warning log line:

W (2597) ESP_Mesh_Lite_OTA: SHA-256 for current firmware: ...

Anything you can share about this process?

Thank you very much!

@github-actions github-actions bot changed the title Partition Verification after OTA Partition Verification after OTA (AEGHB-967) Jan 29, 2025
@tswen
Copy link
Contributor

tswen commented Feb 7, 2025

Yes, Mesh Lite sets the OTA partition to valid during initialization.

W (2597) ESP_Mesh_Lite_OTA: SHA-256 for current firmware: ...

This is merely a print of the SHA-256 for the current firmware and is not an error message. It will be logged as INFO level in future versions.

@mrjohannchang
Copy link

Is there a way to disable the automatic 'set pending activation partition valid' feature? If esp-mesh-lite enforces this, we won't be able to perform customized checks.

@tswen
Copy link
Contributor

tswen commented Feb 8, 2025

OK, thank you for your suggestion, we will optimize it later.

@tswen
Copy link
Contributor

tswen commented Feb 21, 2025

This issue was updated in this commit: 56d5ad2

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

3 participants