Platform Integration Aspects: Embedded Wizard Community License (EWCL) - Developer Guide
This article provides a non-binding convenience summary for developers. For all legal purposes, only the full Embedded Wizard Community License (EWCL) applies.
This guide explains how to use the Embedded Wizard Community Runtime and associated binary components (the "Library") under the Embedded Wizard Community License (EWCL). EWCL is a proprietary, zero-fee license that allows you to use and redistribute unmodified binary runtime components of the Embedded Wizard Platform Package Community Runtime. It is not an open-source license.
The license is primarily intended for business and professional use in connection with the evaluation and development of graphical user interfaces and related software. Nothing in EWCL is intended to limit any non-waivable rights you may have as a consumer under applicable law.
What You Can Do Under EWCL
Under EWCL you may develop, test, and distribute applications using the Library, subject to specific requirements:
Internal Development and Testing
You may develop and test your applications using the Library internally without any application source code disclosure obligation, as long as you do not distribute the resulting product (Combined Work).
Distribution of Combined Works
You may distribute products ("Combined Works") that contain the unmodified Library, provided that you:
★Comply with the Application Source Code disclosure requirements.
★Comply with the attribution and notice requirements.
★Comply with all other terms of EWCL.
Repository References
You may include build manifests, checksums, package references, or fetch scripts in your repositories that download the Library from the Licensor's official distribution point. However, you may not generally re-host the Library yourself, except in specific SDK bundling scenarios that are expressly allowed by EWCL.
Application Source Code Disclosure
If you distribute a product (firmware, software image, device, SDK, etc.) that contains the Library (a "Combined Work"), you must provide the complete corresponding Application Source Code to all recipients.
What Must Be Disclosed
You must provide the complete corresponding Application Source Code (your own application code) to all recipients of the Combined Work, excluding:
★The Embedded Wizard Library itself.
★Independent Third-Party Components under their own licenses (e.g., operating system, standard libraries, middleware).
How to Make Source Code Available
Make the Application Source Code available through one of the following methods:
★Via a publicly accessible repository without paywall or mandatory registration, in a form sufficient to build the application.
★Via a written offer provided with the Combined Work, valid for at least 3 years from distribution (and as long as you offer spares or support for that product, if longer), to give any third party who possesses a copy of the Combined Work either a copy of the complete corresponding Application Source Code on a durable physical medium for no more than your reasonable cost of performing such distribution, or access to download the complete corresponding Application Source Code from a network server at no charge.
Additional Requirements
When distributing the Combined Work, you must:
★Ensure that you do not impose additional terms on the Library that conflict with EWCL.
★Ensure that recipients understand they receive a direct license to use the Library from TARA Systems under EWCL.
IMPORTANT
If you use the Library only internally and do not distribute a Combined Work, no Application Source Code disclosure is required.
Redistributing the Library (SDK Bundling)
Normal Projects (Non-SDK)
Outside of SDK bundling, you must not mirror, copy, host, or publish the Library or any of its components (including headers) in public repositories, package registries, or CDNs. You may only reference official download locations.
SDK Bundlers
If you are a semiconductor vendor, board vendor, or tooling partner, EWCL allows you, as an "SDK Bundler", to distribute the unmodified Library as part of a developer SDK, reference design, or evaluation kit, provided that you:
★Include EWCL in the SDK and require downstream developers to accept it before using the Library.
★Do not charge a separate fee for the Library.
★Do not modify, wrap, obfuscate, or unbundle the Library.
★Include and preserve all required notices.
★Only use TARA Systems' name and trademarks for truthful attribution.
★Promptly update or remove the Library from your SDK if TARA Systems requests this (e.g., for security or license reasons).
IMPORTANT
End users get their rights in the Library directly from TARA Systems under EWCL; you do not sublicense the Library to them.
For more information about Platform Packages and Build Environments, see Platform Package and Build Environment Overview.
Key Restrictions and Anti-Avoidance
When using the Embedded Wizard Community Runtime, you must adhere to the following restrictions:
Prohibited Modifications
★Do not modify, translate, adapt, wrap, obfuscate, or create derivative works of the Library, except as expressly permitted by EWCL.
★Do not reverse engineer, decompile, or disassemble the Library, except where explicitly allowed by mandatory law (for example, for limited interoperability purposes under applicable law).
★Do not remove or circumvent any technical protection measures, runtime notices, or license keys in the Library, except where applicable law expressly allows this.
★Do not separate, copy, or redistribute the Library's components except as an unmodified bundle as provided by TARA Systems or as permitted for SDK Bundlers.
Benchmarking Restrictions
Do not benchmark or publish performance comparisons of the Library without TARA Systems' prior written consent, except to the limited extent that a prohibition of such publication is not allowed by mandatory applicable law.
Anti-Avoidance Provisions
Do not structure, split, refactor, repackage, or label your code or components with the purpose or effect of evading the Application Source Code disclosure obligations.
IMPORTANT
Helper libraries, glue code, wrappers, or modules that primarily implement application business logic or primarily exist to talk to the Library are typically considered part of the application rather than independent third-party components.
EWCL contains an "anti-avoidance" clause with objective factors (such as shared code bases, joint deployment, common development teams, and whether a module implements application business logic) to determine what counts as part of the application. When in doubt, assume such modules are part of the application and include them in your Application Source Code disclosure.
Required Attribution and Notices
Whenever you distribute a Combined Work or SDK that includes the Library, you must place the required attribution and a copy of EWCL (or a URL pointing to it) in your usual third-party notice locations.
Placement Guidelines
For devices or tools with a UI:
★Include the attribution in an About, Legal, Credits, or similar screen that is reasonably accessible to end users.
For devices without a UI:
★Include the attribution in printed or electronic documentation shipped with the device, or provide a publicly accessible URL printed on the device or packaging.
For OEM or module integrations:
★Include the attribution in the OEM's standard third-party or open-source notice files that are made available to end users.
Preserve Existing Notices
You must preserve all copyright, trademark, and legal notices included by TARA Systems in the Library.
Required Attribution Text
The following is the exact wording required by EWCL:
This product includes unmodified binary components from Embedded Wizard Platform Package Community Runtime, licensed by TARA Systems GmbH. Copyright (c) [Year] TARA Systems GmbH. All rights reserved.
No Warranty and Limitation of Liability
EWCL provides the Library on an "AS IS" basis without warranties of any kind, either express or implied. This means:
★The Library is provided without warranty of merchantability, fitness for a particular purpose, non-infringement, or any other warranty, to the maximum extent permitted by applicable law.
★To the maximum extent permitted by applicable law, TARA Systems and its licensors are not liable for indirect, incidental, special, consequential, punitive, or similar damages (including but not limited to loss of profits, business interruption, loss of data, loss of goodwill, or other commercial loss), even if they have been advised of the possibility of such damages.
★EWCL clarifies that liability is limited to the maximum extent that applicable law allows such limitation; where liability cannot be excluded, mandatory law controls.
IMPORTANT
This warranty disclaimer and limitation of liability applies to the maximum extent permitted by law. Where mandatory consumer protection laws apply, they may provide non-waivable rights that supersede these limitations.
Security Updates and Takedown
EWCL contains explicit obligations regarding critical security issues in the Library. You must have processes in place to respond to security notifications.
Response to Security Notifications
If TARA Systems notifies you that a particular version of the Library has a critical or high-severity security vulnerability, you must:
★Without unreasonable delay, cease any new distribution of Combined Works that include the specifically affected version, except where continued distribution is strictly necessary for safety, regulatory, or operational reasons.
★Use commercially reasonable efforts to make an updated Combined Work available that includes a fixed version of the Library or appropriate mitigations.
★Where reasonably feasible, inform your direct customers or channel partners about the availability of such update or mitigation if the vulnerability is likely to materially impact them.
When No Fix Is Available
If no fixed version is available yet, you must assess the vulnerability and implement reasonable compensating controls or mitigations under your own responsibility, especially in safety-critical or regulated contexts.
TIP
Watch for security notices from TARA Systems and have a process in place to stop distributing known-vulnerable Library versions and to provide updates or mitigations.
When You Need a Commercial License
You must obtain a separate commercial license from TARA Systems if any of the following applies:
★You want to ship a closed-source product and do not want to provide the complete corresponding Application Source Code as required by EWCL.
★You need extended warranties, SLAs, or long-term commercial support beyond what EWCL provides.
★You plan to use the Library in safety-critical or regulated contexts (e.g., automotive, medical, industrial safety systems) where a failure could result in death, personal injury, or severe property or environmental damage, and where specific safety standards (IEC 61508, ISO 26262, DO-178C, IEC 62304, etc.) apply.
★You need additional regulatory documentation, certifications, or safety artifacts that are not covered by EWCL.
For such use cases, contact TARA Systems to negotiate a commercial license that explicitly covers your use.
For more information about commercial licensing options, visit Embedded Wizard Platform Packages.
Suggested Developer Workflow
Follow this workflow to ensure EWCL compliance throughout your development process:
During Development
★Use the Embedded Wizard Community Runtime internally under EWCL.
★Keep your Application Source Code in a repository that can be published or otherwise made available to recipients if you distribute a Combined Work.
★Avoid "clever" module splits whose main effect is to hide application logic from disclosure; they may still be treated as part of the application.
Before Shipping a Product
★Decide whether you will use EWCL-style distribution (disclosing the complete corresponding Application Source Code) or obtain a separate commercial license from TARA Systems for closed-source distribution.
★Add the required attribution text to your About, Legal, documentation, or product notices.
★Verify that the runtime notice is present in Community builds of the Library and not suppressed.
★Implement and document your Application Source Code disclosure mechanism (e.g., public repository URL or written offer in the manual).
Ongoing Maintenance
★Monitor security and license-related notices from TARA Systems.
★Stop distributing vulnerable Library versions once notified, and provide fixed or mitigated updates as described in the security section.
Examples of Compliant and Non-Compliant Disclosure
The following examples provide non-binding guidance to complement Appendix D of EWCL. In case of doubt, always check the exact text of EWCL.
Good (Compliant) Examples
Public GitHub Repository
A public GitHub repository that contains:
★All application .c, .h, and other application source files created or modified by you.
★CMakeLists.txt, Makefile, or other build scripts.
★A README with clear build instructions, e.g., "Build with: cmake . && make".
The repository is public, does not require login, and stays available for as long as you distribute the Combined Work (and at least 3 years).
Public Product Web Page
A public product web page or documentation with a clearly visible statement, such as:
"Application source code available at: https://yourcompany.com/opensource/product-xyz"
The URL leads to a page that allows anyone who has a copy of the Combined Work to download the complete corresponding Application Source Code without paywall, mandatory registration, or additional contractual restrictions that conflict with EWCL.
Written Offer
A written offer in the product manual, for example:
"Application source code for this product is available upon request. Please contact: sourcecode@yourcompany.com"
In practice, any person who possesses a copy of the Combined Work can obtain the complete corresponding Application Source Code by sending an email, without being forced to sign an NDA or accept extra license terms that reduce their rights under EWCL.
Bad (Non-Compliant or Risky) Examples
Restricted Access
Source available upon written request, but in practice, the requester is required to:
★Create a customer account and accept additional terms that restrict their rights under EWCL.
★Sign a non-disclosure agreement (NDA) before receiving the code.
This conflicts with the requirement that recipients of the Combined Work must be able to effectively obtain the complete corresponding Application Source Code without extra restrictions that contradict EWCL.
Incomplete Disclosure
A public repository or download that only contains:
★Some application source files (e.g., only main.c), but not all code needed to build the application.
★Build scripts that are clearly incomplete.
★No README explaining how to build the application.
This is typically not sufficient to qualify as "complete corresponding Application Source Code" in a buildable form.
Paywalls or Restrictive Terms
A download page that:
★Requires payment.
★Requires mandatory registration with acceptance of additional license terms that limit use of the disclosed Application Source Code beyond what EWCL allows.
Paywalls or restrictive terms on top of EWCL are not compatible with the disclosure obligation in Section 2.2.
TIP
These examples are intended to help developers implement an EWCL-compliant disclosure strategy in practice. Where your actual setup differs, review it against Section 2.2 and Appendix D of EWCL, and adjust as needed.
Full License Text
For all legal details, definitions, and binding obligations, please refer to the full Embedded Wizard Community License (EWCL) shipped with your package (typically named Embedded_Wizard_Community_License_EWCL.txt or similar), or visit the official license page referenced by the Library's runtime notice or by TARA Systems on their website.