Intel® oneAPI IoT Toolkit Release Notes

Published: 08/05/2019  

Last Updated: 09/14/2021

By Juhi Batra

Intel® oneAPI IoT Toolkit includes the following components:

Refer to this article to get more information about semantic versioning followed by Intel® oneAPI Toolkits.

New in This Release

 

  • Intel® processor optimizations in compilers and performance libraries and continued CPU performance enhancements. The Intel® compilers provide additional OpenMP 5.0 and 5.1 capabilities, and they enhanced their SYCL* 2020 feature set and conformance to improve programming productivity on various hardware accelerators.
  • Intel® Inspector improved C++ stack frames visualization and increased accuracy of libc and OpenCL* libraries reporting.
  • IoT Plugins for Eclipse 
    • The Yocto meta-intel-iss layer has been deprecated and is expected to EOL as part of the 2022.1 general release. Developers should switch to using the meta-intel-oneapi layer.
    • The Yocto meta-intel-oneapi layer, which adds support for dpc++ compiler runtimes, will move to the open embedded layer index in a future release. Precise timing and details of that move will be provided as part of the 2022.1 general release.

 

 

Changes to Existing Features

  • Removal of Eclipse* IDE - Starting with the 2021.3 release of the Intel® oneAPI IoT Toolkit, the Eclipse IDE for C/C++ Developers (Eclipse CDT) package will no longer be bundled with the Intel® oneAPI IoT Toolkit. Plug-ins to support Intel® oneAPI development in Eclipse will continue to be provided for integration into a user-provided copy of the Eclipse IDE for C/C++ Developers either during or after installation of the Intel® oneAPI IoT Toolkit.
  • Starting with the oneAPI 2021.4 release, SLES 12 and SLES 15 SP1 will no longer be supported.
  • Starting with the oneAPI 2022.1 release, Fedora 32 and Fedora 33 will no longer be supported.
  • Starting with the oneAPI 2022.1 software release, CentOS 8.x will no longer be supported.
  • The Linux* kernel build tools and IoT connection tools have been deprecated and will be removed from the Intel® oneAPI IoT Toolkit with the 2022.1 release. This means that the “com.intel.yocto.tools” Eclipse plugin and the “org.eclipse.upm.sensorbrowser" Eclipse plugin will no longer be supported or distributed with the Intel® oneAPI IoT ToolkitThe “meta-intel-oneapi” Yocto layer (aka recipe) will continue to be supported for adding oneAPI libraries and tools via command-line development of Yocto projects.

Installation Instructions

Please refer to System Requirements to check the prerequisites for installing the Intel® oneAPI IoT Toolkit. 

The Intel® oneAPI IoT Toolkit can be installed from the download page. For more detailed instructions, see Installation Guide for Intel® oneAPI Toolkits.

For more information on using the toolkit, see: Linux* | Windows* | Containers

If you run into issues installing the tools, and would like to see the install logs (helpful for reporting issues) you can find them in %temp%\intel_oneapi_installer and %temp%\dd_VSIXInstaller_.log for Windows* Host and /tmp//intel_oneapi_installer/ for Linux* Host.

Product Versions

The following table outlines which version of the individual components are present in the latest version of Intel® oneAPI IoT Toolkit.

Component Version
Intel® DPC/C++ Compiler 2021.4.0
Intel® C++ Compiler Classic 2021.4.0
Intel® Inspector 2021.4.0
Linux* kernel build tools 2021.4
IoT connection tools 2021.4

Known Issues and Workarounds

  1. Missing Symbolic link in component "Yocto* compatible Linux* Platform Project Development" may cause build failure in /YoctoProject/meta-intel-iss/recipes-socwatch/socawatch/intel-iss-socwatch-target.bb
    Implication: Users will be unable to integrate SoC Watch into Yocto* Project images
    WorkAround:
    • Remove the /lib64 -> /lib symlink if the build failure persists,
    • Create /lib64 folder if it does not exist
    • Create symlink /lib/ld-linux-x86-64.so.2 -> /lib/ld-linux-x86-64.so.2 if it does not exist.
  2. The file third-party-programs.txt has an incorrect path to additional information.
    On Linux for a default installation, the file is /opt/intel/oneapi/licensing/2021.1-beta09/third-party-programs.txt. The path name in that file should be /opt/intel/oneapi.
    On Windows for a default installation the file is: C:\Program Files (x86)\Intel\oneAPI\licensing\2021.1-beta09\third-party-programs.txt. The path name in that file should be C:\Program Files (x86)\Intel\oneAPI.
  3. If you have chosen to download the Get Started Guide to use offline, viewing it in Chrome, may cause the text to disappear when the browser window is resized. To fix this problem, resize your browser window again, or use a different browser.
  4. Yocto Project* 3.1 Toaster Startup bug
    Implication: In Yocto 3.1, Toaster has a startup bug (a proposed fix is listed which may allow some users to use Yocto 3.1) which is affecting multiple components. Users will need to use other supported versions of OS till a fix is issued
    1. Linux* Kernel Build Tools does not support Yocto 3.1 as it depends on the Toaster component of Yocto.
      1. Workaround: We recommend use of Yocto 3.0 in conjunction with Linux* Kernel Build Tools until a fix is released for this issue. Linux* Kernel Build Tools does not support Ubuntu* 20.04
    2. Linux* Kernel Build Tools does not yet support SLES 15/15.1 because it depends on the Toaster component of Yocto, which is not working as expected on SLES 15/15.1. This issue has been reported to Toaster maintainers and is expect to be fixed soon.
  5. Linux* Kernel Build Tools Beta does not support Ubuntu 20.04 because it depends on Yocto 3.1, which does not yet support Ubuntu 20.04.
    We expect the next version of Yocto to support Ubuntu 20.04 which will enable Linux* Kernel Build Tools to support Ubuntu 20.04 in oneAPI Gold release.
  6. The Problems view in Eclipse* may list error results for some oneAPI sample projects.
    Workaround: These errors are false positives and can be ignored. The samples will build and run in Eclipse* when the environment is correctly configured as described in the oneAPI Getting Started documents.
  7. When creating and building sample projects using the Eclipse* samples provider, the Eclipse Intellisense indexer does not work.
    Workaround:
    To resolve the issue, the project toolchain must match the compiler from Intel (usually the Intel® oneAPI DPC++ Compiler) that builds your sample project.

See the Intel® oneAPI Base Toolkit Release Notes for additional details and issues common to multiple toolkits.

Notices and Disclaimers

Intel technologies may require enabled hardware, software or service activation.

No product or component can be absolutely secure.

Your costs and results may vary.

© Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.

No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.

The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.