[MAX32625PICO] Add new platform

[khariya]

Depends on PR #6778

Description

MAX32625PICO is available with and without Bootloader.
Use target name MAX32625PICO_NO_BOOT to compile without the bootloader.
Use target name MAX32625PICO to compile with the bootloader.

Test results:
mbed_test_max32625pico-no-boot_arm.txt
mbed_test_max32625pico-no-boot_gcc-arm.txt
mbed_test_max32625pico-no-boot_iar.txt

Tested all supported toolchains with MAX32625PICO

Pull request type

[ ] Fix
[ ] Refactor
[X] New target
[ ] Feature
[ ] Breaking change

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : FAILURE

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

[0xc0170]

/morph mbed2-build
/morph test

[0xc0170]

/morph test

[0xc0170]

@khariya Please resolve the conflict

[khariya]

Conflict resolved. Rebased with the master branch.

[mbed-ci]

Test : FAILURE

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

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[ashok-rao]

@khariya , for the target with the bootloader, are there any post build steps required to "combine" the bootloader with the generated binary?

[ashok-rao]

@khariya : Since there are multiple peripherals of each type, it would be recommended to define a "default" for each one.. for ex: SPI_MOSI = SPI1_MOSI , I2C_SDA = I2C1_SDA & so on.. so that application code doesn't need to explicitly specify the peripheral number to use..

[khariya]

@ashok-rao Added the default defines. Thanks.

[khariya]

@ashok-rao No additional post-build steps are required for the target with the bootloader, the generated binary is sufficient.
Please note that the bootloader must be programmed separately before dropping the application binary. Compiling the target with bootloader does not combine the bootloader with the application.

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[0xc0170]

Restarting CI. The last commit looks fine.

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[ashok-rao]

Thanks @khariya for adding the defaults. Regarding bootloader, curious to know how this will be made available to end users? Will there be a link somewhere on the platform page?

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[cmonr]

/morph mbed2-build

[cmonr]

/morph mbed2-build

[khariya]

@ashok-rao The MAX32625PICO board(as a target, not as a programmer) comes with the bootloader installed on it by default.
Thanks.

[cmonr]

/morph mbed2-build

[cmonr]

@ashok-rao Does this link answer your question? https://os.mbed.com/platforms/MAX32625PICO/#default-daplink-image

@khariya Is it expected that this link will be updated when updates are needed/available?

[ashok-rao]

Thanks for the link @cmonr . All other changes good to go from my side.
@khariya : can we have the default bootloader binary provided to users from that link as well? or steps/ link to update it when there are updates to it in the future.. along with DAPlink as already provided.. thanks.

[ashok-rao]

LGTM! Thanks @khariya

[cmonr]

@khariya I'm ready to give the ok and get this merged in once we get the last couple of questions answered.

[khariya]

@cmonr @ashok-rao The platform page will be updated when needed.
We can provide the default bootloader binary on the platform page along with instructions. Additional hardware will be required to update the bootloader.

[ashok-rao]

thanks @khariya . Please update the instructions on the platform page along with any specific HW / SW requirements. Thanks.

[khariya]

Yes, I will update the platform page. Thanks!

[adbridge]

There is something very strange in the commit history for this PR. Trying to cherry pick across to 5.8 we get the following:

error: patch failed: targets/TARGET_Maxim/TARGET_MAX32625/device/TOOLCHAIN_IAR/TARGET_MAX32625MBED/MAX32625.icf:1
error: targets/TARGET_Maxim/TARGET_MAX32625/device/TOOLCHAIN_IAR/TARGET_MAX32625MBED/MAX32625.icf: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.

As I can't see an easy way of fixing this I'm going to push it out to 5.9.