Add bootloader configuration parameters for MAX32625PICO

[khariya]

Description

Tested with MAX32625PICO in bootloader mode (default).
Tested override using mbed_app.json for non-bootloader mode.

Pull request type

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

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : FAILURE

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

[mbed-ci]

Test : SUCCESS

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

[0xc0170]

@khariya Can you review exporters failure? It's related to device packs.

I believe it is related to this change "device_name": "MAX32625" . Is this valid device name?

[khariya]

I found same error when Maxim pack was not installed, keil_without_pack.txt

No error after installing the Maxim pack: keil_with_pack.txt

I believe the device name is valid. Would you mind checking if the pack is installed correctly?

[cmonr]

Will get the pack installed in our CI, and rerun once it's good to go.

[cmonr]

IOTTESTINF-3041

[cmonr]

/morph export-build

[cmonr]

/morph export-build

[cmonr]

/morph export-build

[cmonr]

/morph mbed2-build

[studavekar]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

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

[0xc0170]

The failure in the last exporter looks like the device pack still not present, we will investigate

[cmonr]

Going to re-run, just in case: /morph export-build

[cmonr]

/morph export-build

[cmonr]

/morph export-build

[adbridge]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

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

[khariya]

We're reviewing the pack files to see if something is broken.

[cmonr]

@khariya Thanks for looking into the issue. We're also looking to reproduce the issue locally on our side as well.

Could you confirm that http://www.mxim.net/microcontroller/pack/Maxim.MAX32650.1.1.0-a.pack is the correct pack that we should be installing?

[khariya]

@cmonr Here's the pack for MAX32625: http://www.mxim.net/microcontroller/pack/Maxim.MAX32625.1.0.0.pack

Your link is for the MAX32650 target.

[cmonr]

Needs work on our end. Still waiting on the CI update.

[khariya]

An update for MAX32625 pack has been released:
http://www.mxim.net/microcontroller/pack/Maxim.MAX32625.1.1.0-a.pack

It fixed the problem on my local machine.

Keil version 5.25.2.0
Compiler version 5.06 update 6

[cmonr]

Pack should now be installed.

Restarting with build since last build is older than a week.
/morph build

[cmonr]

Sorry, absolutely no idea what happened there.

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : SUCCESS

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

[adbridge]

Looks like some of the files in this commit have been renamed and then edited in the same commit. This causes problems for 'git am' and makes it extremely difficult to patch. @khariya please try not to do this in the future. Moving this to 5.10

[cmonr]

@ARMmbed/mbed-os-maintainers
Is this documented somwhere? I recall seeing this kind of mistake made every once in a while, but unless it's documented publically somewhere, I tend to not hold it against the PR owner.

[khariya]

@adbridge is there a way to check this locally before creating the PR?

[adbridge]

@khariya I'm not sure how you could check it. It looks like the recommended way of doing things is 'git mv' for renaming files, you could try this in the future ?

[cmonr]

@khariya It helps if file move commits are seperate from file changes.

If they are together, then the patch application process becomes incredibly sensitive to the order of operations (file change then move, vs file move then changed) and I don't know what the process defaults to.