Remove TB_SENSE_1 target

Remove efm32zg_stk3200 target

Remove efm32hg_stk3400 targets

Remove efm32wg_stk3800 target

Remove efm32lg_stk3600 target

Remove efm32pg_stk3401 target

Merge pull request #12547 from amq/update-emlib ...

EFM32: update emlib to 5.9.1

EFM32: move __Vectors from header to source

Merge pull request #12692 from petroborys/master ...

EFM32G11: Add RGB LEDs to PinNames.h

Added RGB LEDs to PinNames.h

EFM32: fix minor emlib changelog typos

EFM32: update emlib for EFR32MG12

EFM32: update emlib for EFR32MG1

EFM32: update emlib for EFM32ZG

EFM32: update emlib for EFM32WG

EFM32: update emlib for EFM32PG

EFM32: update emlib for EFM32LG

EFM32: update emlib for EFM32HG

EFM32: update emlib for EFM32PG12

EFM32: update emlib for EFM32GG11

EFM32: update emlib for EFM32GG

EFM32: update emlib src and inc

EFM32: update emlib changelog

Bugfix for #12374 ...

Use an RTCC retention register to keep track of user timebase for RTC API. RTC and LP Ticker implementations use the same counter, but they shouldn't share timebases.

EFM32: fix mbed_hal-pinmap test

EFM32: add UART and LEUART for EFM32GG11 ...

- adds the missing PinMap definitions for UART0, UART1, LEUART0 and LEUART1
- corrects a misplaced `#endif` for `#if DEVICE_SPI` which included `UART_TX`
- all according to https://www.silabs.com/documents/public/data-sheets/efm32gg11-datasheet.pdf

modified itm_api.c for STK3701 and add SWO location 0 to EFM32GG11_STK3701, EFM32GG_STK3700, EFM32LG_STK3600, EFM32PG_STK3401, EFM32PG12_STK3402 and EFM32WG_STK3800

Update HAL CRC API ...

* Change "is supported" check to be a macro, so it can be done at
  compile-time.
* Eliminate weird shift on 7-bit CRCs.
* Add support for 32-bit CRCs and reversals to TMPM3HQ.

Merge pull request #11203 from Tharazi97/Watchdog_lower_limit_timeout_test ...

Add watchdog lower limit timeout test

Clean up ARM toolchain heap+stack setup in targets ...

ARM Compiler 6.13 testing revealed linker errors pointing out
conflicting use of `__user_setup_stackheap` and
`__user_initial_stackheap` in some targets. Remove the unwanted
`__user_initial_stackheap` from the targets - the setup is
centralised in the common platform code.

Looking into this, a number of other issues were highlighted

* Almost all targets had `__initial_sp` hardcoded in assembler,
  rather than getting it from the scatter file. This was behind
  issue #11313. Fix this generally.
* A few targets' `__initial_sp` values did not match the scatter
  file layout, in some cases meaning they were overlapping heap
  space. They now all use the area reserved in the scatter file.
  If any problems are seen, then there is an error in the
  scatter file.
* A number of targets were reserving unneeded space for heap and
  stack in their startup assembler, on top of the space reserved in
  the scatter file, so wasting a few K. A couple were using that
  space for the stack, rather than the space in the scatter file.

To clarify expected behaviour:

* Each scatter file contains empty regions `ARM_LIB_HEAP` and
  `ARM_LIB_STACK` to reserve space. `ARM_LIB_STACK` is sized
  by the macro `MBED_BOOT_STACK_SIZE`, which is set by the tools.
  `ARM_LIB_HEAP` is generally the space left over after static
  RAM and stack.
* The address of the end of `ARM_LIB_STACK` is written into the
  vector table and on reset the CPU sets MSP to that address.
* The common platform code in Mbed OS provides `__user_setup_stackheap`
  for the ARM library. The ARM library calls this during startup, and
  it calls `__mbed_user_setup_stackheap`.
* The default weak definition of `__mbed_user_setup_stackheap` does not
  modify SP, so we remain on the boot stack, and the heap is set to
  the region described by `ARM_LIB_HEAP`. If `ARM_LIB_HEAP` doesn't
  exist, then the heap is the space from the end of the used data in
  `RW_IRAM1` to the start of `ARM_LIB_STACK`.
* Targets can override `__mbed_user_setup_stackheap` if they want.
  Currently only Renesas (ARMv7-A class) devices do.
* If microlib is in use, then it doesn't call `__user_setup_stackheap`.
  Instead it just finds and uses `ARM_LIB_STACK` and `ARM_LIB_HEAP`
  itself.