Signed-off-by: Anna Matczak <anna.matczak@arm.com>

Add TF-M support and enable it by default, as Total Solutions examples
aim to demonstrate all supported features.

TF-M has a predefined memory layout for each supported platform, so add
non-secure linker scripts for supported examples, platforms and
toolchains to match TF-M's requirements.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Note: Unlike Corstone-300, Corstone-310 has four ITCM blocks of 8 KB
each and the combined size of 32 KB is too small to use as an
application's main RAM. Use the 2 MB ISRAM0 as RAM instead, to match the
memory layouts of TF-M and the Open IoT SDK examples.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

At this point, support for GCC is limited to CMake and has not been
added to Keil MDK yet.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Add an option to enable automated testing with CTest and htrun. Because
the LCD display on the graphical window is not easy to verify, disable
LCD display and instead log the first two frames when in test mode.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Because the FVP or AVH is an emulation tool running on a PC, the
performance can be very low compared to an FPGA. The full Arm-2D
benchmark example runs at around 1 frame/second. To improve the user
experience, add options
* `ARM2D_EXAMPLE_TINY_MODE` (ON by default) to build a simpler version
of the example.
* `ARM2D_EXAMPLE_MVE` (OFF by default) to toggle the use of MVE which is
very slow to emulate on the FVP/AVH (which the examples run on
initially), although MVE is one of the key features of the Armv8.1-M
architecture and benefits performance on real hardware.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

This demonstrates how a user creates a CMake project that
* gets Arm-2D and its dependencies using the Open IoT SDK
* creates applications that use and link against Arm-2D
* gets platform support from an MCU-Driver-HAL implementation, in this
case mcu-driver-reference-platforms-for-arm.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Fix the memory layout defined in MPS3_CM55_DTCM.sct which is used for
Corstone-300:
* The sizes of ROM (ITCM) and RAM (DTCM) should be 0x80000 bytes each,
much less than previously declared. Any code beyond the intended ROM
size can't be loaded onto the target but nonetheless got linked into the
image previously due to incorrect size declared in the linker script.
* As a result of the ROM size fix, the ROM is not enough to fit the
example anymore. To fix this, add an additional region ROM region which
is the code SRAM and put read-only code and data in it. The use of the
two ROM regions, ITCM and code SRAM, is consistent with other projects
such as TF-M.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

The `app_cfg.h` headers in the two examples do not contain anything
useful. The only files that include `app_cfg.h` are platform support
code in `examples/common/platform`, but the headers from the two
examples only set macros that are entirely unrelated to platform
support. This is most likely to be unused legacy code that has not been
cleaned up.

Without having any impacts at all on the examples, remove the two
`app_cfg.h` files and create an empty one in the common root directory
of example code, where `main.c` is also located. With only one
configuration, we can build common code once and link both examples
against it, instead of needing two separate builds.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

The two examples have almost identical `main.c` which is mostly a
backbone. The actual applicaton bodies of the two examples are in
`examples/common/benchmark/benchmark_generic_app.c` and
`examples/common/benchmark/benchmark_watch_panel.c` respectively.
Unify `main.c` by only having a common copy of it as `examples/main.c`.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Check the macro `PKG_USING_PERF_COUNTER`, as done in
`examples/common/platform/lib/perf_os_patch_rt_thread.c`. This avoids
linking failure of every file that includes `perf_counter.h` due to
undefined `__ensure_systick_wrapper`, whose definition is only provided
for RT-Thread (in the aforementioned file) and not other RTOSes or bare
metal.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Note: The include style with relative path `..` is used, in order to
maintain consistency with existing code in the project which was
originally built with Keil MDK.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

MPS3_CM55_HEAP.sct was imported from another repository but never used.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Add missing top-level rule to trigger a pipeline when the default branch
is pushed (i.e. a merge request is merged).

Note that the templates `.gitlint-check` and `.sync-public` already
contain their own rules, ensuring they are only run under the right
conditions such as gitlint on merge requests only and syncing on default
branch only.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Whenever a merge request has been merged, the default branch will see
new commits, triggering the CI pipeline to push the latest commits to
the public mirror.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

At this point, no applications or tests have been added yet. Files from
the original Arm-2D project do not follow the style and license
requirements of the Open IoT SDK project group. For those reasons, we
only enable the gitlint check for now.

Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>