Add MTB MXChip EMW3166

[ashok-rao]

Description

Adding MXChip EMW3166 as a new target.

Status

READY

Migrations

NO

Todos

• Tests
• Documentation

Deploy notes

Needs addition of new hardware in CI.

@0xc0170 - can you please review the additions?

cc @screamerbg @chris-styles @studavekar

[0xc0170]

@ashok-rao Can you share the test results ?

[ashok-rao]

Thanks for approving @0xc0170 .. For greentea, there is no DAPLink support available yet for the STM32F412 that is used on this module. So far, I have been using KEIL to flash the axf onto the target and check the Mbed OS port. Any ideas how to proceed with tests?

cc @screamerbg @chris-styles

Edit: PR is also raised for mbedls: ARMmbed/mbed-ls#287

[0xc0170]

Thanks for approving @0xc0170 .. For greentea, there is no DAPLink support available yet for the STM32F412 that is used on this module. So far, I have been using KEIL to flash the axf onto the target and check the Mbed OS port. Any ideas how to proceed with tests?

We shall wait for daplink firmware to test this addition

[ashok-rao]

@c1728p9 .. can we please build a DAPLink for the EMW3166 with F412? It is currently built on F411. Thank you.

[c1728p9]

can we please build a DAPLink for the EMW3166 with F412? It is currently built on F411.

@ashok-rao this isn't a supported DAPLink board currently, so I can't simply rebuild it.

[ashok-rao]

Ok. So, we won't be able to run CI on this then..

[ashok-rao]

@0xc0170 .. we got a DAPLink build for it from @c1728p9 for this module .. I ran greentea locally on it and attaching the results below.. All of them seem to be commonly failing in lp_ticker / timer .. I suspect this could be because we are using internal clocks on all these MCB's ? or is there something going on with greentea ? Could you please have a look? Thanks.

GT_IAR_EMW3166.txt
GT_ARMCC_EMW3166.txt
GT_GCC_EMW3166.txt

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : FAILURE

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

[mbed-ci]

Test : SUCCESS

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

[ashok-rao]

@0xc0170 ..thanks for triggering the test.. I cannot see the reason why exporter has failed. Looks like all PASS from the logs.. ??

[0xc0170]

/morph export-build

[0xc0170]

/morph uvisor-test

[mbed-ci]

Exporter Build : FAILURE

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

[ashok-rao]

@0xc0170 Looks to me that it's failing on other different platforms while the MTB's are passing.. @studavekar @kegilbert

[cmonr]

Rerunning export test. Looks like one of the exporter machines went offline too soon.

/morph export-build

[cmonr]

@0xc0170, what's the particular reason for the Do Not Merge label?

[mbed-ci]

Exporter Build : SUCCESS

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

[ashok-rao]

Woohhoo! Thanks @cmonr .
@0xc0170 ..over to you to take this PR further.

[ashok-rao]

@0xc0170 ..bump!

[cmonr]

@ashok-rao Is it still the case that this needs hardware in CI? Or is that still not possible due to the board not having a DAPlink interface?

[ashok-rao]

@cmonr .. we have a DAPLink for this now & the tests have passed above.. It doesn't need new HW in CI.. So, should be good to go from my end. Thanks!