Enable tickless mode in MAX32630FTHR

[gpsimenos]

Description

This PR is part of IOTCLOUDPR-3223. The requirement is to enable tickless mode in targets that CI can run tests on. In this first PR, tickless mode is enabled in MAX32630FTHR, which successfully passed all greentea tests with tickless mode.

An additional PR may follow with more targets that currently show minor greentea regressions, after it is confirmed tickless mode is not the cause.

Pull request type

[ ] Fix
[ ] Refactor
[X] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@evedon @hugueskamba

[ciarmcom]

@gpsimenos, thank you for your changes.
@hugueskamba @evedon @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

commit this separately please - removing dead space

[gpsimenos]

Done

[gpsimenos]

Hey @0xc0170 did you want the removal of dead space in a separate PR or just a separate commit in this PR?

[0xc0170]

separate commit would work but as there are multiple commits, separate PR is easier.

[hugueskamba]

Please edit the first commit message to clearly list the targets for which tickless has been enabled.

[hugueskamba]

LGTM

[evedon]

Changing release to 5.15 as this is a target change

[evedon]

Fine for the code change to enable tickless.
One comment left by Martin for the dead spaces.

[0xc0170]

Ci started

[mbed-ci]

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_build-ARM
• jenkins-ci/mbed-os-ci_build-IAR
• jenkins-ci/mbed-os-ci_build-GCC_ARM

[gpsimenos]

Last force push removes failing target.

[0xc0170]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts

[idea--list]

Hi there,
Opened issue ticket #12493 earlier this night.
After some hours of investigation i found in the release notes for 5.15.0 that tickless mode has been enabled in MAX32630FTHR. As it sounded suspicious i opened up targets.json, looked up the definitions for the MAX32630FTHR board and deleted the changes introduced by this merge.

Made a clean build and the problem described in #12493 is solved. If i undo the change in targets.json and clean build the code then the issue is back again.

It seems this merge has not been tested properly, please either undo this merge or solve the bug it introduces in crucial functions like wait(), wait_ms(), ThisThread::sleep_for(), etc.