CircularBuffer: volatile specifier removal ...

Volatile specifier in this case it not required as we currently have all accesses
to the buffer protected by critical section. This shall optimize accesses in
some cases to the buffer.

Fixes #7702

Merge pull request #7609 from bremoran/patch-2 ...

Make location meaningful in print_error_report

Merge pull request #7603 from OpenNuvoton/nuvoton_override_gcc_sbrk ...

Nuvoton: Replace __wrap__sbrk with overriding _sbrk

Make location meaningful in print_error_report ...

`handle_error` calls `MBED_CALLER_ADDR()`, but this is always a location from within platform/mbed_error.c. This is because `handle_error` is declared static. This does not cause the function to be inlined however. Instead, it is called by each function within mbed_error.c. For example, mbed_error yields this code:

```
000625c8 <mbed_error>:
   625c8:       b510            push    {r4, lr}
   625ca:       460c            mov     r4, r1
   625cc:       4611            mov     r1, r2
   625ce:       461a            mov     r2, r3
   625d0:       9b02            ldr     r3, [sp, #8]
   625d2:       f7ff feff       bl      623d4 <handle_error>
   625d6:       b968            cbnz    r0, 625f4 <mbed_error+0x2c>
   625d8:       4620            mov     r0, r4
   625da:       f7ff ff67       bl      624ac <print_error_report.constprop.0>
   625de:       f7ff fea8       bl      62332 <core_util_is_isr_active>
   625e2:       b910            cbnz    r0, 625ea <mbed_error+0x22>
   625e4:       f7ff fe9f       bl      62326 <core_util_are_interrupts_enabled>
   625e8:       b908            cbnz    r0, 625ee <mbed_error+0x26>
   625ea:       bf30            wfi
   625ec:       e7fd            b.n     625ea <mbed_error+0x22>
   625ee:       2001            movs    r0, #1
   625f0:       f000 f948       bl      62884 <__wrap_exit>
   625f4:       4800            ldr     r0, [pc, #0]    ; (625f8 <mbed_error+0x30>)
   625f6:       bd10            pop     {r4, pc}
   625f8:       80ff010f        .word   0x80ff010f
```

Note that at `625d2` there is a bl to handle error. That replaces the LR, which means that ALL calls to mbed_error will report a location of 0x625d6 or 0x625d7 (user vs. supervisor). I do not expect that this was the intention of the code. The simplest fix is to change line 99:

```C
static inline mbed_error_status_t handle_error(mbed_error_status_t error_status, unsigned int error_value, const char *filename, int line_number)
```

Since `handle_error()` will be inlined, the link register will be kept the same, so `MBED_CALLER_ADDR()` will yield the expected result. However, there is no guarantee that the compiler will respect the `inline` keyword in all circumstances.

The result is that each function that wishes to report its caller must extract its caller. This code cannot be centralised.

I have modified `mbed_error.c` to report the caller of each error reporting function, rather than the error reporting function itself.

[Nuvoton] Replace __wrap__sbrk with overriding _sbrk ...

With _sbrk being weak, we can override it directly rather than #if to support heap with
two-region model.

Improved logic in wait_us to avoid division operation in sub-millisec case

Update stats to fetch Mbed OS version info

Merge pull request #7434 from deepikabhavnani/version_header ...

Separate version header file in Mbed OS

Separate version header file to get version updates in Mbed OS

Remove error reporting for release builds

Don't print error reports in release builds

Fix wrong config binding

Merge pull request #7331 from TomoYamanaka/improve_bootloader ...

Improve the process for Cortex-A9 in mbed_application

platform: astyle update

Fix error history related comments

Improve the process for Cortex-A9 in mbed_application ...

I added the powerdown func by GIC in mbed_application because Cortex-A9 use GIC instead of NVIC.
This process prevent unexpected interrupt when updating software by using bootloader.

Merge pull request #7214 from SenRamakri/sen_ErrorOptimAndConfig ...

Error handling configuration updates and Optimization for exception handling

Add the process for Cortex-A in mbed_applicaion ...

I added the process for Cortex-A in mbed_application.c because this process was for only Cortex-M.
Also I enabled the macro of MBED_APPLICATION_SUPPORT for Cortex-A.

Limit error filename capture to 64 chars, wrapping tests with right configs and astyle fixes.

Updates to configuration flags used in error handling implementation. ...

The new configuration make Error history tracking switched off by default and enabled by using the config flag MBED_CONF_PLATFORM_ERROR_HIST_ENABLED.
Config flag MBED_CONF_PLATFORM_ERROR_ALL_THREADS_INFO enables printing info of all threads. This will be turned off by default.

Merge pull request #7117 from OpenNuvoton/nuvoton_fix_armc6_memtrace2 ...

Fix compile error with MBED_MEM_TRACING_ENABLED and ARMC6

Merge pull request #6949 from OpenNuvoton/nuvoton_m23_bootloader ...

Support mbed_start_application for Cortex-M23

error: fix undeclared memcpy ...

Some targets do not get string header file in, results in the warning:
implicit declaration of function 'memcpy'

Fix compile error with MBED_MEM_TRACING_ENABLED and ARMC6

Merge pull request #7050 from SenRamakri/sen_ErrorHandlingFilenameFix ...

Fix for filename capture not working

Do not capture filename for release builds

Fix for error report not printing when calling error API

Fix for filename capture not working

OS version is not available in code, need a fix for this in next patch release

Remove superfluous MOVT in mbed_start_application/start_new_application