TESTS: Reduce allocate memory size

Merge pull request #15003 from dustin-crossman/pr/add_missing_bt_support ...

Add bluetooth support files to Cypress BSPs.

Merge pull request #14982 from npal-cy/pr/swintegration-481 ...

CYW43XXX Cordio HCI driver: fixed MCU deep-sleep locking flow

Merge pull request #14976 from world-direct/feature/target_stm32f1 ...

Add more uarts for STM32F103xG

Add bluetooth support files to Cypress BSPs.

Merge pull request #14990 from ikmdani/stm32l1_usb_enable_pullups ...

Driver: USB: STM32L1: Managing internal pullups for usb enumeration

Merge pull request #14997 from Patater/update-pywin32 ...

python: Upgrade pywin32

python: Upgrade pywin32 ...

Remove pinned pywin32 version. Require an upgrade of pywin32 to a
version that includes security and bug fixes we'd like (CVE-2021-32559).

Merge pull request #14995 from saheerb/master ...

travis ci migration to github action

Merge pull request #14902 from LDong-Arm/greentea_skip ...

CMake: tests: Support skipping unsupported test with reason

Merge pull request #14972 from OpenNuvoton/nuvoton_m2354_tfm_psa_fwu ...

M2354: Support PSA Firmware Update

CMake: greentea: Port PSA Attestation test to CTest ...

The PSA Attestation test suite requires full RTOS. There is no need
to explicitly check PSA support, because when we build all greentea
tests from the top of Mbed OS, PSA tests only get included if PSA is
enabled.

CMake: greentea: Add skip reason to ticker test

CMake: tests: Support skipping a test with a reason ...

Add a new argument `TEST_SKIPPED` to `mbed_greentea_add_test()` to
indicate a test is skipped and give a reason (e.g. the Mbed target
and/or configuration does not provide what the test requires).

The skip reason of a test is printed when running tests with `ctest`,
and the test is marked as "Skipped" in the test report.

cmake: Improve indentation of mbed_greentea_add_test doc

CMake: turn mbed_greentea_add_test() into a function ...

Unlike a macro, a function is more self-contained and can return
early if necessary.

Merge pull request #14892 from rwalton-arm/greentea_ctest ...

Add CTest support for `mbed-drivers-ticker` greentea test

travis ci migration to github action

ci: Use new mbed-os-env docker image in "multiple executables" test ...

The github workflow to test building multiple executables was using the
soon to be deprecated docker image "mbedos/mbed-os-env:latest". This
commit points it at the new docker image on ghcr.io.

targets: Add "bare-metal" to supported_application_profiles ...

We weren't setting the "supported_application_profiles" correctly for
some baremetal supported targets. This didn't cause build failures with
mbed-cli 1 as it just seems to ignore this config parameter. In our CMake
build system we have added a hard dependency on the
supported_application_profiles; we fail the build if the profile we're
trying to build isn't in the list.

CMake: Use CMAKE_MODULE_PATH to locate nuvoton post build hook ...

We were previously relying on the global MBED_PATH variable to provide
the root for the include path to the post build hooks. We can't
guarantee that MBED_PATH will be set by any application building us, so
use CMAKE_MODULE_PATH (which we always set) like we do for the other
post-build hooks.

ci: Add github action to build greentea tests with cmake ...

Build for two targets, one with baremetal profile and one full profile.

CMake: greentea: Use more specific name for baremetal option ...

Make it obvious the option is used for greentea tests.

CMake: greentea: Port mbed-drivers-ticker to CTest ...

Call add_test in mbed_greentea_add_test and specify mbedhtrun as the
command to run.

An MBED_HTRUN_ARGUMENTS variable has been added, which is a semicolon
separated list of arguments to forward to htrun. The user is required to
pass in any arguments mbedhtrun needs to communicate with the device
under test at CMake configuration time.

We automate passing some of the htrun arguments in CMake using data
provided by mbed_config.cmake or gathered from the CMake environment.
The following arguments are passed to htrun from CMake:

* -f/--image-path
* -e/--enum-host-tests
* -m/--micro
* -R/--reset-timeout

--baud-rate is also passed if the MBED_CONF_PLATFORM_STDIO_BAUD_RATE
config parameter is defined.

Temporary checks have been added to mbed_greentea_add_test to keep the
old flow working until we port all of the greentea tests to CTest. These
checks should be removed after we make all greentea tests runnable by
CTest.

CMake: greentea: Set variables usually defined by external apps ...

We rely on external applications to set MBED_CONFIG_PATH and include
app.cmake. Mbed OS can't build for a target without those parameters
set. When building greentea tests there is no external application. So,
we define the appropriate settings in our root CMakeLists.txt for
greentea tests.

CMake: Add option to enable greentea tests ...

Add an option to enable the greentea tests independently from the unit
tests.

We can't just use the typical BUILD_TESTING option to enable greentea
tests. BUILD_TESTING enables unit tests and fetches googletest, which
are compiled for the host. Greentea tests are cross compiled and require
a toolchain file. For this reason we add a new option just to enable
greentea tests, preventing build failures triggered by the unit tests
and googletest.

Driver: USB: STM32L1: Managing internal pullups for usb enumeration ...

This commit adds internal pullup on DP line for usb enumeration
in nucleo_l152re platform. This platform as such does not have
usb connector (device).

This has been tested with example in https://github.com/ARMmbed/
mbed-os/blob/master/drivers/usb/include/usb/USBMouse.h#L58-L76

and mbed_app.json file

"target_overrides": {
        "*": {
            "platform.stdio-baud-rate": 115200,
            "platform.all-stats-enabled": true,
            "mbed-trace.enable": "0"
        },
        "NUCLEO_L152RE": {
            "target.device_has_add": ["USBDEVICE"]
        }
    }
}

Signed-off-by: Krishna Mohan Dani <krishnamohan.d@hcl.com>

Merge pull request #14983 from LDong-Arm/sfdp_sector_map ...

SFDP: Add unit tests for Sector Map Parameter Table parsing

SFDP: Add unit tests for Sector Map Parameter Table parsing ...

Add tests for `sfdp_parse_sector_map_table()` which currently (at the
time of this commit) supports flash devices with
* no Sector Map Parameter Table (i.e. the whole flash is uniform and
non-configurable)
* a single descriptor in the Sector Map Parameter Table (i.e. the
flash layout is non-configurable and has multiple regions)

Support and unit tests for flashes with multiple configurable layouts
will be added in the future.

Note: The implementation of `sfdp_parse_sector_map_table()` assumes
the table to be valid if read succeeds, so the SFDP reader callback
needs to ensure it reads data correctly or return an error.

Fixed MCU deep-sleep locking flow in CYW43XXX Cordio HCI driver. The CYW43XXX Cordio HCI driver incorrect handles lock/unlock deep-sleep entry, as results it allows to put PSoC6 in to deep-sleep when CYW43xx does not expect this (the host_wake_up pin in ACTIVE_LOW state, which means hat host must be in ACTIVE mode ). ...

Now, CYW43XXX Cordio HCI driver has the following MCU deep-sleep locking scenarios/flows:
a) A BT device or MCU does not support Low Power mode (MBED configuration does not include MBED_TICKLESS, DEVICE_SLEEP, DEVICE_LPTICKER or CYCFG_BT_LP_ENABLED features). In this case, CyH4TransportDriver locks deep-sleep in the initialize() function and unlocks the terminate() function.

b) A BT device and MCU support Low Power mode. In this case, the control of the unlock/lock of the deep-sleep functionality will be done in bt_host_wake_rise_irq_handler and bt_host_wake_fall_irq_handler handlers. Finally, CyH4TransportDriver unlocks the deep-sleep in terminate() function (if it was locked before) by checking the bt_host_wake_active flag.

Fixes #13076, #13700, #13295.