Mbed-os: Override mbed flash behavior for Greentea

[janjongboom]

Description

Quite a lot of the Mbed OS tools require a way to flash new binaries on boards, but they all rely on using mass-storage device mode. This is fine for development boards, but when you move away from them (towards a real product) you often don't have this. E.g. many of the cheap JLINK adapters don't support MSD, or maybe you're using Atmel EDBG. Is there any way to override the flashing behavior without modifying Mbed OS itself? I've ran into this issue on three occassions in the last two weeks, with @desowin from Etteplan, with @martinichka from TWTG, and with The Things Network.

Issue request type

[X] Question
[ ] Enhancement
[ ] Bug

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-970

[desowin]

There is related issue in mbed-cli https://github.com/ARMmbed/mbed-cli/issues/475

[cmonr]

CC @ARMmbed/mbed-os-tools

[theotherjimmy]

@janjongboom My first impression is that you would have to break mbed test intombed test --compile followed by mbed test --run and specify the flashing method to mbed test --run, which should be able to take greentea arguments directly.

[loverdeg]

@janjongboom Add @loverdeg-ep, @trowbridgec, @farrenv, from Embedded Planet to your list.

We've been dealing with this for months.
Please see https://github.com/ARMmbed/DAPLink/issues/577#issuecomment-460822443

[janjongboom]

@theotherjimmy Or let me specify a flash python script in the custom_targets.json or something. That would help.

[ciarmcom]

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.