Mbed OS example application doesn't run for MUSCA A1 target

[jainvikas8]

Description of defect

Mbed OS example application not running for target - ARM_MUSCA_A1
A simple https://github.com/ARMmbed/mbed-os-example-blinky example results in error

--- Serial output ---
[INF] Starting bootloader [ERR] Unable to find bootable image

Target(s) affected by this defect ?

ARM_MUSCA_A1

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

Arm Compiler 6.13 and GCC 9
mbed compile -t GCC_ARM -m ARM_MUSCA_A1_NS
mbed compile -t ARMC6 -m ARM_MUSCA_A1_NS

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

mbed-os-6.0.0-rc1

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

mbed cli - version - 1.10.2

How is this defect reproduced ?

Use https://github.com/ARMmbed/mbed-os/tree/mbed-os-6.0.0-rc1 version of mbed-os with https://github.com/ARMmbed/mbed-os-example-blinky. Build and flash the binary to MUSCA A1 board.

[ciarmcom]

@jainvikas8 thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. '9a8c9e2' has not been matched as a valid tag or sha.It would help if you could also specify the versions of any tools you are using?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[jainvikas8]

Effects - ARMmbed/mbed-os-example-crash-reporting#46 and ARMmbed/mbed-os-example-thread-statistics#57

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[0xc0170]

I updated the release version.

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[adbridge]

@jainvikas8 it looks like you removed the tools versions section from the issue template ('What version(s) of tools are you using. List all that apply (E.g. mbed-cli)') . This is preventing the issue from being mirrored! Please do not remove sections! Please re-instate it and fill it in. See #13106 as an example.

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@jainvikas8 it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[MarceloSalazar]

@jainvikas8
Note the Musca A1 is not considered supported in Mbed OS 6, hence we plan to remove it - #13165

[MarceloSalazar]

Closing as #13106 is merged and Musca_A1 isn't supported.