Increased wait time to allow device to sleep ...

With small wait time at the start, chances are that device does not
enter sleep and idle time is zero. Increasing wait time to make sure
device goes to sleep.

Merge pull request #6857 from deepikabhavnani/cpu_stats ...

CPU Statistics

Merge pull request #6821 from deepikabhavnani/system_stats ...

System stats - API addition

Merge pull request #6901 from kivaisan/eventqueue_time_left ...

events: Introduce API to query how much time is left for delayed event

Introduce API to query how much time is left for delayed event ...

If user has initiated a delayed event (either with call_in or call_every),
user might need to know how much time is left until the event is
due to be dispatched.

Added time_left() function can be used to get the remaining time.

Added additional read to care of lazyily initialized timer

Merge pull request #6749 from AndrzejKurek/feature-mbedtls-platform-setup ...

Add platform setup and teardown calls to mbedtls tests

Updated test to not use event queue. ...

Test was failing on limited RAM devices, because of shared event queue size.
Updated test to use thread instead of event queue.

Addressed review comments ...

1. LP ticker limiation note
2. Use read_us in mbed_uptime function
3. Doxygen recommendations
4. Use us_timestamp_t instead uint64_t
5. Astyle changes

CPU statistics addition ...

API to get CPU stats like sleep/deepsleep time, uptime and idle time.
These can be used by application to know the CPU Usage runtime.

OS version added + CPUID for cortex-M only ...

CPUID base register is available for Cortex-M processors only.
Cortex-A devices have Main ID Register, which can be used in future to
get processor info.

Added test for mbed_stats_sys_get() API

Merge pull request #6795 from deepikabhavnani/thread_stats ...

Thread stats API

Merge pull request #6864 from davidsaada/david_flashiap_unaligned_src ...

FlashIAP: Fix problem of programming source buffer not aligned to 4

Merge pull request #6711 from marcuschangarm/cleanup-nrf5x ...

Cleanup TARGET_NRF5 and TARGET_NRF5x

Cleanup ...

1. Enable watermark to get stack space information
2. Restructured code
3. Throw error if MBED_THREAD_STATS_ENABLED is not set
4. Astyle changes

Cleaup and review comments addressed ...

1. Removed prefix thread_ from all elements of mbed_stats_thread_t
2. #if conditions aligned to rest of the file

Checking difference in thread count + review comments

Thread statistics addition. ...

API to get all system threads information and states.

FlashIAP: Fix problem of programming source buffer not aligned to uint32_t

tests-mbed_drivers-rtc: Add one second tolerance in functional tests. ...

Currently test assumes that 1 sec is long enough to set RTC time and read same time which has been set.
In some cases extra time for synchronisation between clock domains is needed and after setting/reading operations the read value might be different than one which has been set (+1 sec).
Additionally in some cases when lp ticker is based on RTC, the RTC implementation may use mechanism to trace elapsed seconds without modifying RTC registers. In such case it is possible that second will change immediately after setting time.

Add 1 sec tolerance (min possible) for such checks.

Reorganize TARGET_MCU_NRF51822_UNIFIED directories ...

The unified NRF51 target and feature BLE directories have been
reorganized to follow the naming and directory structure of the
NRF52 implementation.

This reorganization does not include TARGET_MCU_NRF51822 and
derived targets.

Update logs and remove unnecessary defines for Mbed TLS tests

Moved stats test to platform folder

Re-enable flash clock test for NRF52 but with higher tolerance ...

The flash clock test is disabled for the NRF52 series. This change
re-enables the test but with a higher tolerance to accommodate the
high jitter on the current ticker implementation.

Add platform setup and teardown calls to mbedtls tests

Merge pull request #6534 from c1728p9/rtos_suspend ...

Update idle loop to reduce calls to suspend

Modifying echo test to be driven more from the device. ...

Previously, the echo test followed a flow like the following:

-STEP-	-HOST PC-                  -DEVICE-
0	send _sync
1				   echo back _sync
2				   send echo_count
3	echo back echo_count
4	send first echo packet
5				   echo back echo packet
	(repeat echo steps)

However, as noted by issue #6659, this test would somtimes fail between
steps 4 and 5. To ensure each KV pair makes to the correct destination,
we usually write the KV back. Step 4 does not wait for this to happen
and starts sending echo packets. So the device is acting as the "echo
server".

This change makes the host PC the "echo server". The idea being that the
device will be slower and the host pc should always be able to keep up
with it, not the other way around.

Renamed NRF52 targets for HAL critical section test

RTOS: SysTimer: Fix test compilation error on ARM & IAR