- Mar 24, 2024
-
-
Devaraj Ranganna authored
With all documentation files added under `docs` folder, finding a relevant document was a time consuming process. Restructure the docs folder to replicate the FRI source structure for easy navigation and better user experience. Signed-off-by:Devaraj Ranganna <devaraj.ranganna@arm.com>
-
Devaraj Ranganna authored
Add VS Code tasks and launch configuration files to enable building and debugging FRI using VS Code. Signed-off-by: -
Devaraj Ranganna authored
Create `devcontainer.json` and the `Dockerfile` to bootstrap the devcontainer when FRI project is cloned using VS Code command palette. Signed-off-by: -
Devaraj Ranganna authored
In order to support VS Code build and debug support, add debug option `-d` to run script. In addition, use `realpath` to get absolute path for build folder. Signed-off-by:
-
- Mar 18, 2024
-
-
When building ML apps, the MLEK downloads model resources for the model specified by a given application. The FRI integration of the MLEK prevents these resources from being re-donwloaded if they already exist to speed up build time. However, in the case of a different application being build, model resources have to be re-downloaded as different ML applications use different models. To allow the re-download of model resources, the generated ML model resources subdirectory is now generated in the CMake build directory. Building a different application requires triggering a clean build which will also delete the resources specific to a model used by another application. Signed-off-by:
Hugues Kamba Mpiana <hugues.kambampiana@arm.com>
-
- Mar 17, 2024
-
-
Hugues Kamba-Mpiana authored
The `freertos-iot-libraries-tests` application was mistakenly relying on another app's TF-M configuration file. The other app (`aws-iot-example`) was removed along with its configuration files. The `freertos-iot-libraries-tests` application now uses its own TF-M configuration file. Signed-off-by:Hugues Kamba-Mpiana <hugues.kambampiana@arm.com>
-
- Mar 14, 2024
-
-
Corstone-315 added to the blinky and to the ML/OTA tests too. Signed-off-by:Dávid Házi <david.hazi@arm.com>
-
Object detection example is an ML vision example on the Cortex-M systems. Currently running only on Corstone-315 to demonstrate the usage of ISP, NPU, HDLCD together. Signed-off-by:Gabor Abonyi <gabor.abonyi@arm.com>
-
Starting bootloader printed by BL2. Corstone-300 and 310 starting the BL2 first, than do the provisioning part. Corstone-315 do the provisioning first, because of the BL1 ROM bootloader, therefore the log messages comes swapped from this platform. We have deleted the Starting bootloader line to unify the pass output file. Signed-off-by: -
The HDLCD helper adds 3 predefined display formats to the project, RGB565, RGB32 and A2R10G10B10. Signed-off-by: -
The tools has been added to convert images to .FRM format, which can be fed into the Corstone-315 FVP's "camera" input. Signed-off-by: -
Generates `You Only Look Once` (YOLO) fastest object detection model for the object detection application Signed-off-by: -
Arm-2D is used by the object detection example to draw frames around detected faces. Signed-off-by: -
Using the latest platform, the Corstone-315 as default. Signed-off-by: -
Arm Mali-C55 image signal processor (ISP) driver The Corstone-315 has an ISP IP, which can be used to create downscaled image for ML vision applications. ISP also can handle camera lens, sensors. The driver comes with a 3A algorithm (proprietary) Signed-off-by: -
* Add Corstone-315 platform to FreeRTOS Plus TCP Corstone-315 has got a different memory map than the previous Corstone platforms. * Turn on BL1 logging for Corstone-315 * Don't define PLATFORM_DEFAULT_CRYPTO_KEYS for Corstone-315, this platform using its own keys, because of the new security IPs Signed-off-by: -
Added Corstone-315 support. Because of the different provisioning method, the 315 should be handled separately. The function is using the cmake variables instead of the function parameter list. Signed-off-by: -
* 0001-corstone300-Modify-ISRAM0-to-be-non-secure-partition.patch have been removed, because DTCM was not large enough in some cases. S DATA RAM moved to the beginning of ISRAM0, size increased to 128kB. * Updated to the latest commit which supports Corstone-315 platform * patch: Corstone-315 has got a new provisioning method. To match the new method to the older platforms, we were changed the last provisioning step's log messages, in this case the CI pass conditions can be unified. Signed-off-by: -
The latest version of the Arm Corstone Platform BSP repository provides support for the Corstone-315 platform. Signed-off-by: -
For the Corstone-300, 310 and 315 platforms, TF-M allocates S DATA RAM on the first 128kB of the ISRAM0 memory region. NS DATA RAM can be placed after this region. Signed-off-by:Ahmed Ismail <Ahmed.Ismail@arm.com>
-
- Mar 11, 2024
-
-
Add real clock time synchronisation to keyword-detection application by using `coresntp` and `helpers-time-sync` libraries This would require using MbedTLS time functions alternatives to query the correct synchronised real clock time. This addition would fix AWS TLS Expired Server Cert test as previously, wrong clock time was fetched which result in using expired server certificate. Now, correct clock time would be fetched which results in target rejecting the server's expired certificate which in turn fixes the test. Signed-off-by: -
This helper library shall be used with any FRI application to add real clock time synchronisation for the target. This addition is needed to fix AWS TLS Expired Server Cert test which is part of AWS Device Advisor Validation tests as this test requires the device under test to have synchronised real time clock to be able to detect that the server's certificate is expired and reject it. Signed-off-by: -
Add latest LTS release of coreSNTP FreeRTOS library to the FRI to be used for synchronisng embedded targets clock time. Signed-off-by: -
Fix `descrived` typo. Signed-off-by: -
We shouldn't be allocating heap using C and FreeRTOS heap management APIs as we might end up with both FreeRTOS heap and C heap. This can lead to several unexpected issues. C standard heap functions are used to unify heap allocations as we can't use FreeRTOS heap management APIs because this would require patching lots of file as part of ml-embedded-evaluation-kit library which use C standard heap functions for heap allocations. Heap space is increased by `0x10000` as C standard heap management APIs requires more heap space for the existing FRI applications because it is less optimised than FreeRTOS heap management APIS (heap_4). Signed-off-by: -
It was noticed that sometimes speech-recognition application fails on the CI because the OTA update is not completed by the time `timeout-seconds` is reached. Hence, increasing the timeout for test applications job to 45 minutes instead of 30 minutes. Signed-off-by:
-
- Mar 06, 2024
-
-
Hugues Kamba-Mpiana authored
Patch the library to provide a reduced set of metadata to download and optimize when building applications. The only models specified in the use case resources files (depending on the application) are asr and kws. Those are the only models required by the FRI applications. The build time for the ML applications have been reduced by 40%. Signed-off-by:Hugues Kamba-Mpiana <hugues.kambampiana@arm.com>
-
- Mar 01, 2024
-
-
Signed-off-by: -
The CMSIS6 has an IRQ driven CMSIS compliant UART driver. USART0 is set to non-secure. TX/RX are now also turned ON at initialization of the USART. Because the driver is IRQ driven, the send function only initiates the transaction. To maintain the CMSIS5 operation model, a busy wait for the completion of the send operation is required. Signed-off-by: -
* As CMSIS6 provides VSI IRQ handlers and IRQ definitions, the BSP patches related to VSI IRQs are removed. * BSP patch files that reference the `CMSIS_Driver/Include` path have been amended, as the path no longer exists and the files patched have moved. * Changed VSI IRQ handlername to the offical ARM_VSI0_Handler * Added RTE_Components.h which enables USART and MPS3 IO CMSIS components. Signed-off-by:
-
- Feb 28, 2024
-
-
This addition is used to validate that the applications's software conforms with TLS, MQTT, Device Shadow, and IoT Jobs best practices. Signed-off-by: -
Add AWS IoT Core Device Advisor service helper library which can be used for validating IoT devices during software development. AWS IoT Core Device Advisor's pre-built tests help to validate the software against best practices for usage of TLS, MQTT, Device Shadow, and IoT Jobs. Signed-off-by: -
The current plan is to support AWS Device Advisor validation on keyword-detection application only. Hence, removing all unused AWS Device Advisor Validation references. Signed-off-by: -
`aws-iot-example` is deprecated as `keyword-detection` and `speech-recognition` applications do all the functionalities that `aws-iot-example` does. Hence, there is no need to maintain it anymore. GitHub CI is modified to build `keyword-detection` and `speech-recognition` applications instead of `aws-iot-example`. Building the Ml Embedded Evaluation Kit requires Python 3.10 and the `libsndfile1-dev` library. Signed-off-by:
-
- Feb 27, 2024
-
-
Devaraj Ranganna authored
* Move supported toolchain information from application docs to README.md to avoid duplicatiing it on all supported examples. * Move supported platforms description from docs/prerequisites.md to README.md to list and describe the supported platforms in one place. * Add supported versions information to supported targets. Signed-off-by: -
Devaraj Ranganna authored
The default target for FRI is Corstone-310. Update the `docs/prerequisites.md` instructions to download Corstone-310 FVP. Signed-off-by: -
Devaraj Ranganna authored
In the initial days of FRI, vht running in ami was the only supported platform since it supported virtual socket interface. However, latest ecosystem FVPs do support virtual socket interface. In addition, FRI now supports FreeRTOS TCP/IP stack. Therefore, remove vht support. Signed-off-by:
-
- Feb 25, 2024
-
-
Add missing PARENT_SCOPE to root folder CMakeLists.txt. It is needed as the entry point is the application/<example>. Signed-off-by:
-
- Feb 21, 2024
-
-
Ahmed Ismail authored
All the components across the project should use the `iot_reference_arm_corstone3xx_apply_patches` function to apply patches which in turn improves consistency. For more information, please refer to the commit with SHA: fa76f068 Signed-off-by:
-
Gabor Abonyi authored
Move common settings and values from the applications to the bsp and root CMakeLists.txt files. These values are common across all apps. Signed-off-by:
-
