Update speexdsp to 1d99e79f604aa23fd3c9db2a727f24287519999b.

Signed-off-by: autobot <autobot-noreply@arm.com>

Signed-off-by: autobot <autobot-noreply@arm.com>

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Update iotsdk-toolchains to c82c133e270e5631e3ba355fa0baa626123def0f.

Signed-off-by: autobot <autobot-noreply@arm.com>

autobot expects files formatted in certain way for working well.

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

autobot will update components to the latest version periodically,
offloading developers from keep up this repository of dependency
changes.

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Saheer Babu authored Dec 21, 2022 and Vincent Coubard committed Jan 12, 2023

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Evelyne Donnaes authored Jan 09, 2023 and Saheer Babu committed Jan 11, 2023

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

Martin Kojtal authored Nov 21, 2022 and Vincent Coubard committed Jan 04, 2023

Our commit messages should follow the Open IOT SDK guidelines

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

The table provides sufficient information about all components
within a project. This will be updated with autobot or when a new
update comes manually, it should be updated as well to reflect
changes to every component.

Using Gitlab feature: json table formatter - much cleaner than
using Markdown tables.

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

Lingkai Dong authored Nov 25, 2022 and Hugues Kamba Mpiana committed Dec 20, 2022

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

The keyword and speech apps can now use the NetX Duo Azure IoT
Middleware for Azure RTOS addon to connect to Azure using ThreadX
and the NetX Duo networking stack.

Some Azure ceritification and device connection files have been imported
from NetX Duo Azure IOT sample example. These are:
* bsp/netxduo-config/nx_azure_iot_cert.c
* bsp/netxduo-config/nx_azure_iot_cert.h
* bsp/netxduo-config/nx_azure_iot_ciphersuites.c
* bsp/netxduo-config/nx_azure_iot_ciphersuites.h
* bsp/netxduo-config/sample_azure_iot_embedded_sdk_connect.c

Signed-off-by: Hugues Kamba-Mpiana <hugues.kambampiana@arm.com>

Hugues Kamba Mpiana authored Oct 31, 2022 and Hugues Kamba Mpiana committed Dec 20, 2022

The function to be implemented by the application to send the result
of the inference was not documented.
Add signature for the expected function in the API header file.

Signed-off-by: Hugues Kamba-Mpiana <hugues.kambampiana@arm.com>

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

Fix naming, using `-` for stages

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

MLIA 0.5.0 has the following updates:
* change the way backends are installed providing a different
  CLI entry point: mlia-backend
* update the generic inference runner to be compatible with the new
  version of Corstone-310 available on AVH

Signed-off-by: Diego Russo <diego.russo@arm.com>

Lingkai Dong authored Nov 25, 2022 and Vincent Coubard committed Nov 25, 2022

The Open IoT SDK has updated ml-embedded-evaluation-kit to a newer
version that
* fetches the standalone CMSIS-DSP submodule rather than as part of
CMSIS_5
* requires each example to include `BufAttributes.hpp` which defines
attributes of the tensor activation buffer
* does not build the timing adapter library for Corstone-310 which has
no timing adapters.

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

In each of the keyword and speech examples, a blink task sets a timer to
post blink events to a queue at a regular time interval, and the blink
task itself processes the queue in a loop. A few other tasks (i.e. ML,
DSP, cloud) run at the same or higher priorities, blocking the blink
task. The queue, not getting processed promptly, gets exhausted quickly
so the timer is unable to post further events into the queue.

The user observable effects of the issue are:
* LED not blinking
* a huge number of "Failed to send blink_event message to ui_msg_queue"
messages printed to the serial terminal

To fix the issue, make the blink task the highest in priority, so it
doesn't get blocked.

Because the blink task has the highest priority, there is no need for
* the blink timer (with overhead of ISR) and blink events (with overhead
of queue) - use `osDelay()`
* time slicing (with the overhead of contantly switching between equal-
priority threads)

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

Apply format changes suggested by `black`.

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

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

The test script `test_ml.py` expects "ML interface initialised" before
"Init speex", but the actual order is not guaranteed for the following
reason:

The DSP thread has a lower priority than the ML thread, but both are
blocked waiting for start signals from message queues. In the case of
running only ML without cloud, the demo posts the DSP start signal
before the ML start signal, which is the opposite order to the thread
priorities. This sometimes causes RTX and ThreadX (but not FreeRTOS) to
unblock the DSP thread first, causing the two texts to be printed in a
different order from what `test_ml.py` expects.

Fix this by posting the start signals of ML and DSP in the same order
as their thread priorities.

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

The function `tfm_ns_interface_init()` creates a mutex to ensure only
one thread calls TF-M APIs at a time, but ThreadX mutexes are only
available when the kernel has been initialized. Fix the issue by moving
`tfm_ns_interface_init()` after kernel initialization.

The CI missed this issue, because the `test-application` pipeline which
runs examples (including blinky) without cloud credentials only covered
AWS as endpoint, and ThreadX is not enabled with AWS. Add the missing
matrix in order to cover blinky with ThreadX.

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

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

Fix the issue that cmsis-rtx accidentally gets linked when threadx-cdi-
port is the intended RTOS implementation.

Linking of RTOS implementation should not be based on the existence of
cmake targets for `freertos-kernel`, `cmsis-rtx` and `threadx-cdi-port`.
All of them depend on listing `cmsis-5` in `IOTSDK_FETCH_LIST` to get
`cmsis-core` and `cmsis-rtos-api`, but the side effect is the `cmsis-5`
repo also adds `cmsis-rtx`, causing a mixture of symbols from
`cmsis-rtx` and `threadx-cdi-port` to get linked. One visible error is
that when building `threadx-cdi-port`, `osKernelInitialize` from
`cmsis-rtx` gets picked up instead of the one from `threadx-cdi-port`,
causing ThreadX kernel initialization to be skipped. This results in,
among other problems, NULL pointer dereference of ThreadX internal
variables when trying to use the kernel timer.

Fix this by directly checking `${RTOS}` which is passed by the build
script based on the user's choice of RTOS.

The fix uncovers another issue that no allocation wrapper
(`pvPortMalloc`) has been defined for ThreadX. To fix this, rename the
existing `malloc`-based wrapper from `cmsis-rtx-freertos-alloc-wrapper`
to `heap-alloc-wrapper` and link it when using either ThreadX or RTX.
The FreeRTOS port from AWS code already has `pvPortMalloc` and thus does
not need our own wrapper.

Similarly, `lwip-cmsis-sys` from the Open IoT SDK accidentally links
`cmsis-rtx` for the same reason, so we also update the SDK to a version
that has this issue fixed.

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

While the build script does not prevent the user from using any
combinations of RTOS and cloud endpoint, it is uncommon to mix RTOSes
and cloud clients from different providers, for example Microsoft's
ThreadX kernel with Amazon's AWS client. Therefore we only need to
ensure the following combinations have been tested
* FreeRTOS with AWS
* ThreadX with Azure
* RTX, as the reference implementation of CMSIS-RTOS, with both cloud
clients.

Switch the default RTOS, when the user invokes the build script without
specifying the RTOS to use, to RTX which has been tested with both cloud
clients. Update the CI script and documentation accordingly.

Also fix the inaccurate notion that the keyword and speech examples run
on CMSIS-RTOS2, FreeRTOS and ThreadX, because CMSIS-RTOS2 is the common
API implemented by RTX, FreeRTOS and ThreadX which are the available
choices.

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

The blinky examples uses the generic CMSIS-RTOS API which is implemented
by all of RTX, FreeRTOS with wrapper and ThreadX with wrapper.

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

Add the job so that DEFAULT branch in internal GitLab will be in sync
with public GitLab.

This job will be run by a scheduled pipeline in this repository.

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

As two way mirroring needs to be established, rename current
`sync-public` to `push-public`.

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

As variable `SYNC_DESTINATION` is needed for multiple jobs, move this to
workflow.

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

developer-tools project is used by many pipelines (scripts,
configuration).

By including baseline sdk Gitlab template, we enable submodule
fetching.

If there is a pipeline that wish not to have submodule fetching
enabled, just overwrite the variable for specific pipeline and
set it to None.

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

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

For pipeline to run, there must be at least one job other than jobs in
stages `.pre` and `.post`. By default, `quality_check` jobs are skipped
in main branch. Hence, move the job to explicit stage so that GitLab CI
works on `main` branch.

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Currently `main` branch is not run which invokes the public-sync.
Also, enable pipeline for `release` branch to run them automatically
when release branch is creaed.

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

Signed-off-by: Saheer Babu <saheer.babu@arm.com>

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

This commit adds the ability to use Towncrier to
manage news (changes) files for each merge request
changeset and then create a new entry to the persistent
CHANGELOG.md file for each release.

I had to add inclusion of developer tools via a submodule.

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

Hugues Kamba Mpiana authored Oct 20, 2022 and Hugues Kamba Mpiana committed Oct 24, 2022

Components to be fetched are now selected by listing them
in a CMake variable named `IOTSDK_FETCH_LIST`.

Signed-off-by: Hugues Kamba-Mpiana <hugues.kambampiana@arm.com>