The Synchronous Data Stream (SDS) Framework implements a data stream management, provides methods and helper tools for developing and optimizing embedded applications that integrate DSP and ML algorithms. This framework may be used stand-alone, but also in combination with CMSIS-Stream that allows to combine algorithms using a compute graph.
Refer to Overview for more details.
| Directory | Description |
|---|---|
| documentation | User documentation of the SDS Framework. |
| overview | Top-level overview of SDS Framework. |
| schema | Schema for SDS YAML metadata format that describes the content of SDS files. |
| sds | SDS-Framework source files and implementation of various SDSIO interfaces. |
| template | SDS template application - a test framework for DSP and ML algorithms. |
| layer/sdsio | Configured SDS interface layers for SDS file I/O via Network, USB, or File System interface. |
| utilities | Python scripts for processing of SDS binary data files. |
- SDS Pack available on keil.arm.com/packs.
- SDS Examples a repository with SDS template applications that are configured for evaluation boards and use cases.
- ML Developers Guide for Cortex-M Processors and Ethos-U NPU.
- Arm Virtual Hardware - FVP repository with documentation.
The SDS Framework is licensed under 
The documentation is generated using Doxygen and MKDocs with the following additional plugins:
Use mkdocs serve to generate the documentation on a local computer.
Contributions are accepted under 
Please feel free to raise an issue on GitHub to report misbehavior (i.e. bugs) or start discussions about enhancements. This is your best way to interact directly with the maintenance team and the community. We encourage you to append implementation suggestions as this helps to decrease the workload of the very limited maintenance team.
We will be monitoring and responding to issues as best we can. Please attempt to avoid filing duplicates of open or closed items when possible. In the spirit of openness we will be tagging issues with the following:
- bug – We consider this issue to be a bug that will be investigated.
- wontfix - We appreciate this issue but decided not to change the current behavior.
- enhancement – Denotes something that will be implemented soon.
- future - Denotes something not yet schedule for implementation.
- out-of-scope - We consider this issue loosely related to CMSIS. It might by implemented outside of CMSIS. Let us know about your work.
- question – We have further questions to this issue. Please review and provide feedback.
- documentation - This issue is a documentation flaw that will be improved in future.
- review - This issue is under review. Please be patient.
- DONE - We consider this issue as resolved - please review and close it. In case of no further activity this issues will be closed after a week.
- duplicate - This issue is already addressed elsewhere, see comment with provided references.
- Important Information - We provide essential information regarding planned or resolved major enhancements.