Skip to content

Missing support for explicit firmware version #26

@maclobdell

Description

@maclobdell

I am working with PSoc64 (target name: CYTFM_064B0S2_4343W).

Background:

This platform requires explicitly passing the new firmware version in 64-bit unsigned integer. The Cypress PSoC64 has it's own boot loader that also uses explicit versioning (instead of time stamp).

Updating the firmware works successfully with the following command (that includes the explicit firmware version).

manifest-dev-tool update-v1 --payload-path <payload> --fw-version <new firmware version> --device-id <device ID> --start-campaign --wait-for-completion

However, when I run the Pelion E2E tests, using the command below, there is no way to pass in the firmware version.

pytest TESTS/pelion-e2e-python-test-library/tests/dev-client-tests.py --update_bin=<path to update binary>

The device fails to start downloading the firmware payload & the service reports that the existing firmware version is at or greater than the firmware version listed in the manifest.

Could the problem be that the manifest is not getting generated with the explicit firmware version?

Is there a quick fix for this?

CC @moshe-shahar @cvasilak

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions