Skip to content

OTA update stretegy following rev4 design #47

@tcsullivan

Description

@tcsullivan

The latest rev4 design is significantly different from previous hardware revisions: a new PDM microphone is being used, and changing from the ESP32-C3 module to the ESP32-S3 means a different pinout and toolchain. Firmware updates for rev4 are not compatible with the previous revisions.

It would make the most sense I believe to call rev4 our "stable" hardware version, and prioritize serving OTA updates for rev4 only.

  • How many previous-revision boards are still active?
  • Is it worthwhile to still provide updates for these older boards?
  • We may need to push out a final OTA for rev3 to disable future updates (or reorganize our OTA serving to take hardware revision into account, which could be nice for future design upgrades too).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions