Create VSCode development environment for Open IoT SDK
descirption and guidelines for setup and usage.
Add Gitlab wkrflow extension descirption and setup guide.
Add note about VSCode development environment in main README.

Signed-off-by: Artur Tynecki <artur.tynecki@arm.com>

Signed-off-by: Andy Powers <andy.powers@arm.com>
Signed-off-by: Lingkai Dong <lingkai.dong@arm.com>

There are multiple documentation pages in docs/, so we should take the
user to the whole directory instead of just one page.

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

Rewording description for the Greentea tests dependencies
and removing obsolete colon and rewording description
of the additional resources for CMake parameters.

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

Correcting grammar and fixing previously
missed uses of not proper name of the repo.

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

Remove the information about the features which are
currently in progress: NimBLE and TinyUSB.

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

Add directory structure to the README.
Update the description of folders in the directory
structure table to make it more informative.

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

Fix typos in Prerequisites and root README files.

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

Tables of contents have been added to Prerequisites
and root README files.

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

Signed-off-by: Jack Styles <jack.styles@arm.com>

We want each example and test to work on all supported reference
platforms (currently Corstone-300) as well as RTOSes that are compatible
with any given example. Also, we would like each example to work like a
typical user project which targets one particular platforms and one
particular RTOS (or none, if the app runs on bare metal). This creates a
large matrix of examples x platforms x RTOSes (or baremetal).

To avoid having to maintain all possible combinations, we introduce a
mechanism for generating examples (similarly for tests). See updated
documentation for how to use this mechanism.

When the main branch is updated (i.e. an MR is merged), publish newly
generated examples to the repository that hosts full, ready-to-use
examples for users' convenience.

In CI runs, all flavors (RTOSes) of the same example are grouped into
the same pipeline to minimize the number of required runners, while
different platforms and toolchains are put into their own pipelines
as before because each of our Docker images contains only one toolchain
or FVP.

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

Add a link to our docs to help make them easier to find for folks new to
browsing this repo.

Signed-off-by: Jaeden Amero <jaeden.amero@arm.com>

Evelyne Donnaes authored Mar 21, 2022 and Rob Walton committed Mar 22, 2022

Signed-off-by: Evelyne Donnaes <evelyne.donnaes@arm.com>

Martin Kojtal authored Mar 08, 2022 and Rob Walton committed Mar 21, 2022

Using Arm Developer report security vulnerabilities

Signed-off-by: Martin Kojtal <martin.kojtal@arm.com>

Evelyne Donnaes authored Dec 20, 2021 and Rob Walton committed Mar 21, 2022

Signed-off-by: Evelyne Donnaes <evelyne.donnaes@arm.com>

Vincent Coubard authored Dec 14, 2021 and Jaeden Amero committed Feb 07, 2022

The stack is not integrated with the rest of the SDK at this stage. It
is only fetched.

Signed-off-by: Vincent Coubard <vincent.coubard@arm.com>

Provide an overview of the components included in the SDK.

Signed-off-by: Jaeden Amero <jaeden.amero@arm.com>

Martin Kojtal authored Nov 05, 2021 and Jaeden Amero committed Jan 20, 2022

Signed-off-by: Martin Kojtal <martin.kojtal@arm.com>

Martin Kojtal authored Oct 25, 2021 and Jaeden Amero committed Jan 19, 2022

Signed-off-by: Martin Kojtal <martin.kojtal@arm.com>

Signed-off-by: Martin Kojtal <martin.kojtal@arm.com>