Skip to content

MAX32625PICO: cannot run Greentea tests with default configuration #14492

Open
@MarceloSalazar

Description

@MarceloSalazar

Description of defect

The MAX32625PICO target is by default configured to run a bootloader and receive binaries over USB.
However, this doesn't let us to generate Greentea tests that could be used automatically with a default configuration (e.g. tests in CI).

The workaround to let people to run tests is to manually replace the extra_labels_add from MAX32625_BOOT to MAX32625_NO_BOOT, as explained here

Target(s) affected by this defect ?

MAX32625PICO

Toolchain(s) (name and version) displaying this defect ?

Arm and GCC

What version of Mbed-os are you using (tag or sha) ?

7389671

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

1.10.4

How is this defect reproduced ?

mbed test -t <toolchain> -m MAX32625PICO -v

Possible fix with Mbed CLI 1:

  • Unify linker scripts into one and conditionally include code depending on the MBED_TEST_MODE. This works well with GCC (thanks to Update gcc.py for preprocessing in linker script #11254). However, there seems to be a bug in the legacy Mbed build system for Arm compiler, which doesn't include macros as part of link stage (.link_options.txt). The Mbed build system is frozen hence can't be fixed upstream.

Possible fix with Mbed CLI 2:

  • Update CMakeLists.txt for the MAX32625 and check MBED_TEST_MODE. Optionally unify linker scripts (assuming CLI 1 isn't used anymore). Note we can't yet verify this as CLI 2 doesn't yet fully work with Greentea (need equivalent to mbed test).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions