Add missing device_name for targets with bootloader

[amq]

Some EFM32 targets with bootloader support are missing the required device_name. This PR fixes it using an analogy to other targets.

Notes:

• I have accepted the contributor agreement.

Status

READY

Migrations

NO

[0xc0170]

@amq Please look at travis, fails because of not valid device name?

[amq]

@0xc0170 this looks like a broader issue with EFR32MG1. Probably that's also why EFR32MG1_BRD4150 is marked with public: false. Relevant PR: #3157
@stevew817

It is not possible to inherit from EFR32MG1
EFR32MG1P132F256GM48
EFR32MG1P233F256GM48
... without either removing device_name from parent or without adding public: false to child.

[0xc0170]

EFR32MG1P132F256GM48
EFR32MG1P233F256GM48

@amq Are these MCU published in the cmsis pack database? Travis fails still.

[0xc0170]

@amq bump

[adbridge]

@amq bump

[amq]

@0xc0170 sorry for not being clear enough. There is a problem beyond this PR (blocker), which makes it impossible to inherit from EFR32MG1P132F256GM48 and EFR32MG1P233F256GM48. It was most likely introduced in #3157

To my understanding this is clearly a bug and we should probably get help from Silicon Labs people.

[0xc0170]

@amq Thanks, I am still not getting the full picture, I'll talk to Steven about this.

@0xc0170 sorry for not being clear enough. There is a problem beyond this PR (blocker), which makes it impossible to inherit from EFR32MG1P132F256GM48 and EFR32MG1P233F256GM48. It was most likely introduced in #3157

@0xc0170 this looks like a broader issue with EFR32MG1. Probably that's also why EFR32MG1_BRD4150 is marked with public: false. Relevant PR: #3157

@stevew817 Can you please help ?

[stevew817]

EFR32MG1_BRD4150 is not marked as public because the board doesn't have USB MSD for programming. Also, it would make a bad mbed target since the kit costs hundreds of $.

I'm still unclear on what exactly the issue is here?

[amq]

Alright, I've removed the EFR32MG1 modification from the commit, it now fixes the missing device_name only in EFM32PG12 and EFR32MG12.

[theotherjimmy]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 510
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5253/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 125
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5253/

[0xc0170]

As already referenced, #5470 the same failure different device. There is a proposed fix in the latest comment there

[studavekar]

/morph test

[mbed-ci]

Test : SUCCESS

Build number : 334
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5253/334

[amq]

Now that CI passed on #5470, could we restart it here?

[0xc0170]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 712
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5253/

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 714
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5253/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 366
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5253/

[mbed-ci]

Test : SUCCESS

Build number : 543
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5253/543

[0xc0170]

Now that CI passed on #5470, could we restart it here?

Once this PR gets in, we will restart CI

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 408
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5253/

[cmonr]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

Build number : 417
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5253/

[cmonr]

Looking into since error is similar to #5470

[studavekar]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 435
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5253/