SFDP: TestEraseTypeAlgorithm: Move setup into test case ...

The test data `struct mbed::sfdp_smptbl_info smptbl` is only relevant
to `TestEraseTypeAlgorithm` and not shared with other test cases.

SFDP: Set region count to 1 for no sector map ...

A flash device with no sector map table has uniform sectors, and we
treat the whole flash as one region. In this case the function
`sfdp_parse_sector_map_table()` sets the single region's size and high
boundary accordingly, but it lacks setting of region count to 1, so
users of the SFDP parser may not get the correct number of regions.
This commit fixes the issue.

SFDP: Move handling of no sector map into `if` ...

When a flash chip's SFDP table has no sector map, we treat the whole
flash as a single region. As an optimization, this should only be
done if there is indeed no sector map.

Unit tests: Remove redundant CMake target mbed-headers-base ...

Individual libraries' `target_h` stub headers have now all been moved
from `mbed-headers-base` to `mbed-headers-<library>`.

Note: Even though headers previously in `target_h` are technically
stubs/fakes too, they are used by not only unit tests but also regular
libraries when compiled for unit tests, because no target-specific HAL
implementation exists in this case. In order for regular library
sources to pick up `target_h` headers, those headers must

* have the same names as regular headers
* appear first in include paths

This is why those headers are part of `mbed-headers-<library>` and not
`mbed-stubs-<library>`. Before this refactoring, `mbed-headers-base`
was the first in unit tests' include paths.

Merge pull request #14911 from DDC-NDRS/fatfs_0.14b ...

FatFs: upgrade to R0.14b

unittests: Reduce runtime of TDBStoreModuleTest.corrupted_set_deinit_init_get ...

Instead of performing 10,000 "set, deinit, get" operations, let's just
perform 100. This reduces test time from 4.8s to 0.02s.

CMake: unittests: Show all tests in CTest report ...

Previously a test executable was recognised as a single test by CTest.
However, test executables usually contain multiple test cases, the
results of the test cases should be individually reported. With our
previous setup we could miss test case failures that didn't cause the
executable to return an error code.

This commit uses gtest_discover_test to discover all test cases in a
test executable. This enables CTest to match test passes and failures
from the googletest binary output.

CMake: unittests: Remove trailing whitespace

Merge pull request #14397 from macronix/macronix_spi_NAND ...

add SPI NAND Block device driver

FATFS: FATFileSystem.cpp migration, according to FatFs version upgrade from R0.13a to R0.14b

Merge pull request #14909 from DDC-NDRS/ndrs-pst ...

SPIF: fixed _address_size to always initialize as 3_BYTES in ::init()

SPIF: Moving _address_size = SPIF_ADDR_SIZE_3_BYTES from constructors into ::init() instead

Update FatFs from R0.13a to R0.14b by manual migration Mbed-OS modification in R0.13a to R0.14b ...

Since a lot of fixed from upstream (0.13b, 0.13c, 0.14, 0.14a and 0.14b)
@see http://elm-chan.org/fsw/ff/updates.txt

Merge pull request #14882 from LDong-Arm/storage_tests_cleanup ...

Unit tests: storage: Only use headers, sources and definitions needed by each test

Merge pull request #14884 from LDong-Arm/rm_UNITTEST_macro ...

Remove the `UNITTEST` macro from production code

Merge pull request #14849 from arduino/pr_spif_namespace ...

SPIFBlockDevice: Add mbed namespace to BD_ERROR_DEVICE_ERROR

Remove `#ifdef UNITTEST` from MbedCRC.h ...

Production code should not contain any test-specific checks. Rather
than checking `UNITTEST`, MbedCRC.h can simply include in all cases
<mstd_type_traits> whose unit test stub exists.

Also remove the `UNITTEST` macro from CMake definitions of kvstore
unit tests which depend on MbedCRC.h.

Unit tests: Clean up unused sources and definitions from storage

Unit tests: Make storage tests depend explicitly on headers it uses ...

The CMake target `mbed-headers` brings in all headers, and we are
gradually moving away from it and explicitly use only headers needed
by each unit test.

Unit tests: Create mbed-headers-kvstore ...

Create a CMake target mbed-headers-kvstore to separate KVStore headers
from the generic mbed-headers-storage. Update tests to use it.

Unit tests: Create mbed-headers-filesystem ...

Create a CMake target mbed-headers-filesystem to separate FileSystem
headers from the generic mbed-headers-storage. Update tests to use it.

Unit tests: Create mbed-headers-blockdevice ...

Create a CMake target mbed-headers-blockdevice to separate BlockDevice
headers from the generic mbed-headers-storage. Update tests to use it.

Unit tests: Limit storage stubs to link what it uses

Unit tests: Do not include mbed.h in storage stubs ...

The header `mbed.h` pulls in headers from a number of Mbed OS
components that are not necessarily used. It was intended for user
applications only, and libraries and unit tests should explicitly
include library headers it uses to limit dependencies.

This change avoids having to link unnecessary libraries in storage
unit tests' CMake definitions.

Move storage stubs into subdirectories of Mbed OS storage ...

Move storage stubs from UNITTESTS/stubs into components inside the
top-level storage directory. Specifically,
* storage/blockdevice/tests/UNITTESTS/doubles/ for BlockDevice stubs.
* storage/kvstore/filesystemstore/tests/UNITTESTS/ for a stub used by
the FileSystemStore test. The stub has been renamed from
kv_config_stub.cpp to filesystemstore_kv_config_stub.cpp, to make it
evident why it doesn't go into storage/kvstore/kv_config/.

CMake: storage: Remove trailing whitespaces

Fix missing 'mbed' namespace error in SPIFBlockDevice

CMake: Require TEST_SOURCES in greentea CMake file ...

Assumption that greentea test file is always named main.cpp is
incorrect. Updated mbed_greentea_add_test() macro to make TEST_SOURCES
parameter compulsory, which is used to specify greentea test
file(s). This allows tests to use C, or have a different name.
Therefore also updated all pre-existing greentea test CMake files to
explicity add main.cpp to TEST_SOURCES.

CMake: Only build unit tests if Mbed OS is the current project ...

Typically when adding a unit test directory to a CMake project a check
will be used to ensure the subdirectory is added only if the following
are true:

* The BUILD_TESTING option is set to ON.
* The current CMake project is the top-level project.

The reason being, if a downstream project includes our project they
generally don't want to build our unit tests.

In mbed-os, we do correctly specify the above condition before adding
the central UNITTEST subdirectory, which fetches googletest and adds the
"stub" libraries the unit tests depend on. However, we only check if
CMAKE_CROSSCOMPILING is OFF (or undefined) before actually adding the
unit tests. This mismatched logic would lead to unexpected build
failures in various scenarios. One likely case could be: a downstream
project including mbed-os happens to set CMAKE_CROSSCOMPILING to
OFF/undefined for any reason (possibly to build its own unit tests).
mbed-os would go ahead and attempt to build its tests without fetching
googletest or adding the required stub targets.

To fix the issue replace the check for CMAKE_CROSSCOMPILING in the unit
tests with the same BUILD_TESTING idiom we use for adding the central
UNITTESTS subdirectory.

Update SPINANDBlockDevice.cpp ...

Fix the spelling issue