|4.0.0-devel-202008 Monthly Release|
| TOR-1202||Feature Request||Add systemd-analyze to TorizonCore||All supported modules||Open Embedded||Low||No|
Description: systemd-analyze is a tool that enables system manager analysis and debugging.
| TOR-1189||Known Issue||Bash completion is missing||All supported modules||Open Embedded||Low||No|
Description: Add bash completion support to Docker and OSTree.
| TOR-1172||Known Issue||Kiosk container not working in sht31 and grafana sample||All supported modules||Debian Base Containers, Samples||Low||No|
Description: Kiosk container is not working in sht31 and grafana sample.
Workaround: add this to the docker-compose file:
| TOR-1168||Known Issue||Prevent Aktualizer from setting bootcount and upgrade_available to zero on every boot||All supported modules||Aktualizr||Low||No|
Description: Prevent Aktualizer from setting bootcount and upgrade_available to zero on every boot to avoid wearing of flash.
| TOR-1166||Known Issue||Remove extra hyphen on demo debian container||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X||Debian Base Containers||Low||No|
Description: Error in the comment about how to accept EULA required to run imx8 vivante graphic drivers.
| TOR-1148||Feature Request||TorizonCore Builder tool||All supported modules||TorizonCore Builder||Low||No|
Description: TorizonCore Builder is a tool that helps to integrate Docker containers and user's customization in a production image.
| TOR-1147||Feature Request||Add basic OpenEmbedded metadata to OSTree metadata||All supported modules||Open Embedded||Low||No|
Description: Add basic OpenEmbedded metadata to OSTree such as distribution, machine or image name.
| TOR-1109||Feature Request||Modem support||All supported modules||Open Embedded||Low||No|
Description: Add modem support (3G, 4G, LTE, etc) in TorizonCore.
| TOR-1063||Known Issue||PKG_CONFIG_PATH is not configured in SDK containers||All supported modules||Debian SDK Containers||Low||No|
Description: pkg-config is not searching in the multi-arch folders by default and this leads to issues when a configuration script uses it to collect information about a specific library/package.
Adding the arch-specific path to PKG_CONFIG_PATH solves the issue,
Workaround: Manually set PKG_CONFIG_PATH to the folder where .pc files are stored for multi-arch packages.
| TOR-1062||Known Issue||Git not installed in cross-compilation SDK containers||All supported modules||Debian SDK Containers||Low||No|
Description: Added git to SDK cross-compilation toolchain containers
| TOR-1047||Feature Request||PIN standardization||All supported modules||Device Trees, Kernel||Low||No|
Description: Standardizing PIN access across SoM's
| TOR-1044||Feature Request||Virtual keyboard for graphical applications||All supported modules||Debian Tools Containers||Low||No|
Description: We should investigate the possibilities to have a virtual keyboard available for graphical applications.
| TOR-1028||Feature Request||OpenCV package||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X||Debian Base Containers, Debian Packages||Low||No|
Description: Provide the OpenCV package and improve the container with DLR support, a compact runtime for Machine Learning Models.
| TOR-446||Feature Request||Portainer templates support||All supported modules||Low||No|
Description: Add templates support to Portainer.
|4.0.0-devel-202007 Monthly Release|
| TOR-1149||Known Issue||Error when applying device tree overlay for 7" parallel display with capacitive touch||All supported modules||Device Tree Overlays||Low||No|
Description: Error on dtconf when trying to apply a device tree overlay for the 7" parallel display with capacitive touch.
| TOR-1144||Feature Request||Update Podman to 2.0.0||All supported modules||Open Embedded||Low||No|
Description: Podman 2.0.0 release marks the HTTP API as stable.
| TOR-1138||Feature Request||Update Docker to 19.03.11||All supported modules||Open Embedded||Low||No|
Description: Docker 19.03.11 fixed the rather severe CVE-2020-13401.
| TOR-1079||Feature Request||Disable jitterentropy in rngd||All supported modules||Open Embedded||Low||No|
Description: Research has shown that jitterentropy is causing high CPU. It seems that does threads run with regular priority, and hence really slow down the boot process. Since we install rngd mainly to fill the entropy pool from the hardware device, this change makes sure that jitterentropy is disabled by default.
| TOR-1064||Feature Request||Gumstix peripherals support||All supported modules||Kernel||Low||No|
Description: Enable drivers in the TorizonCore Linux kernel to be supported by Gumstix's AutoBSP tool.
| TOR-1048||Feature Request||Restart Portainer container if it is automatically closed||All supported modules||Debian Base Containers||Low||No|
Description: The default behavior of Portainer is to present a dialog which ask the user to change the password for 5 minutes, and shutdown itself if the user does not create a password for the admin account. To workaround this issue, we decided to set the container's restart policy to always. That way Portainer immediately restarts in the background.
| TOR-1034||Known Issue||Error installing qt5-default: trying to overwrite '/usr/lib/aarch64-linux-gnu/libGL.so.1', which is also in package libgl1:arm64 1.1.0-1||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X||Debian Base Containers||Low||No|
Description: Error when trying to install qt5-default: trying to overwrite '/usr/lib/aarch64-linux-gnu/libGL.so.1', which is also in package libgl1:arm64 1.1.0-1.
| TOR-1032||Feature Request||Touchscreen calibration support||All supported modules||Debian Base Containers||Low||No|
Description: Container to help calibrating the touchscreen in the Torizon platform.
| TOR-803||Known Issue||Chromium does not render page when Weston is started with pixman||Colibri iMX7, Colibri iMX6ULL||Debian Base Containers||Low||No|
Description: On modules without GPU support such as Colibri iMX7 or Colibri iMX6ULL the Wayland compositor Weston is started with Pixman renderer. It seems that Chromium currently does not render properly when Weston is using Pixman renderer.
Workaround: Use Weston with Mesa software OpenGL (rebuild the Debian Weston base container and drop the `--use-pixman` flag in entry.sh).
| TOR-520||Known Issue||i2c-tools does not install correctly||All supported modules||Debian Base Containers||Low||No|
Description: Fixes a bug that was preventing i2c-tools from been installed inside a Debian container.
|4.0.0-devel-202006 Monthly Release|
| TOR-1043||Known Issue||TorizonCore binary images are missing licence files||Open Embedded||Low||No|
Description: We need to provide the licence files in TorizonCore binary images.
| TOR-1039||Known Issue||Systemd is unable to stop docker-compose||All supported modules||Open Embedded||Low||No|
Description: Containers started via docker-compose can't be stopped via 'systemctl stop docker-compose.service'
| TOR-1027||Feature Request||Qt with GPU acceleration support on iMX8||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X||Debian Base Containers, Debian Packages||Low||No|
Description: Create Debian packages and a sample container to have Qt with GPU acceleration support on iMX8.
| TIE-76||Known Issue||Visual Studio Code for Linux fails attempting to add a device via serial||All supported modules||Moses (IDE Backend)||Low||No|
Description: Customer in referenced community post has an issue in the VScode extension where attempting to add a device via serial seems to fail.
| TOR-980||Known Issue||The AP network interface 'uap0' is not being created sometimes||Colibri iMX8X||Kernel||Medium||No|
Description: The AP interface 'uap0' doesn't always show up properly and only gets initialized after another reboot.
| TOR-979||Known Issue||WiFi interface in access point mode doesn't work on Colibri i.MX8X||Colibri iMX8X||Kernel||Medium||No|
Description: The mwifiex.conf file is missing in /etc/modprobe.d/, therefore it is not possible to use the WiFi interface in access point mode.
Workaround: Create the file on your own with the following content:
'options mwifiex driver_mode=0x3'
| TOR-978||Known Issue||Unable to install libopenvx-vivante1||Debian Packages||Low||No|
Description: Using `torizon/arm64v8-debian-wayland-base-vivante` one cannot install `libopenvx-vivante1`.
| TOR-977||Known Issue||Unable to install libvulkan-vivante1||Debian Packages||Low||No|
Description: Using `torizon/arm64v8-debian-wayland-base-vivante` it's not possible to install `libvulkan-vivante1` due to dependency error.
| TOR-976||Feature Request||Qt Widgets and QML support with Weston/Mesa/Pixman on i.MX7||Colibri iMX7||Low||No|
Description: Qt Widgets and QML support on devices with no HW acceleration using Weston/Mesa/Pixman
| TIE-94||Known Issue||Command to create ASP.NET application fails if the extension is not loaded||Visual Studio Code Extension||Low||No|
Description: Visual studio code activates the extensions on different event. Torizon extension is activated and loaded when an existing project is opened, when a new python or .NET application is create or when the Torizon bar is used.
ASP.NET app creation command was not considered an activation event and so it fails if you try to execute it when the extension is not already loaded.
Workaround: Open the torizon bar by clicking on the Torizon logo in the Visual Studio code Activity Bar on the left side of VS Code main window, this will activate the extension and allow you to run the ASP.NET application create command.
| TOR-952||Feature Request||Add nano to the dev-tools container||Debian Tools Containers||Low||No|
Description: The dev-tools container should have nano as text editors for a better user experience
| TOR-933||Known Issue||Docker pull fails if NTP is not synchronized||Low||No|
Description: If the system clock is not synchronized, the command "docker pull" may fail.
| TOR-918||Feature Request||Add TorizonCore to uname version||Low||No|
Description: We should add "TorizonCore" to the in the kernel version field (UTS_VERSION) compiled in.
| TIE-6||Feature Request||ASP.NET templates for Visual Studio Code Extensions||Visual Studio Code Extension||Low||No|
Description: ASP.NET provides multiple application types. Current template uses basic MVC, but this may not fit customer’s requirement.
New templates has been added for most of the ASP.NET application types supported by the “dotnet new” command.
A more flexible template definition (via YAML file) has been added and may allow definition of more templates also for other languages.
| TIE-65||Known Issue||Error adding device: this.refresh is not a function in VS Code Extension||Visual Studio Code Extension||Low||No|
Description: Error in Visual Studio Code extension when adding device from network
| TOR-797||Known Issue||Build button becomes grayed out and unavailable after first run in Visual Studio Plugin||Apalis iMX8X||Low||No|
Description: After open Visual Studio with the plugin installed, I can succesfully build and debug a new project. However, after terminate the first debug session, the "Rebuild Torizon Application" button become grayed out and I cannot build and run the application again.
| TOR-638||Known Issue||Applying overlay on Apalis iMX8X fails||Apalis iMX8X||Debian Tools Containers, Device Tree Overlays||Low||No|
Description: Activating device tree overlay fails on Apalis i.MX8
| TOR-637||Known Issue||Inconsistency in device tree overlay naming||All supported modules||Device Tree Overlays||Low||No|
Description: The devicetree overlay naming is confusing and should be improved.
| TOR-137||Feature Request||dtconf: Suggest a git pull in case the branch is missing||All supported modules||Debian Tools Containers||Low||No|
Description: In case an older dtconf container is used the branch on the local git repo is missing. Normally we should update our containers so that they already have the branch there. However, it could be that a customer has an older container locally and upated the system or similar situation. We probably should suggest to pull from the git repo in those cases.
| TOR-135||Feature Request||Missing success message when overlay has been applied||All supported modules||Debian Tools Containers||Low||No|
Description: When using dtconf activate the output mentions that the overlay has been validated, but it is not clear that it also has been enabled.
|4.0.0-devel-202005 Monthly Release|
| TOR-974||New Feature||Root filesystem with nano support||Low||No|
Description: Since vim is not “user-friendly”, let's add nano as a text editor option to the TorizonCore’s root filesystem.
| TIE-74||Fixed||SSH error on Windows when debugging a .NET application from a folder that is not under user's home||Visual Studio Code Extension||Low||No|
Description: When developing a .NET application that is stored in a folder that is not under the user home or is accessible to all users, you get an error when trying to start debugger.
On the debug console you can see an error message from SSH complaining about the fact that the permissions for the key file are too open.
Workaround: Move your project under your home folder or change it's access rights to make it accessible only from your user.
| TIE-71||Fixed||Weird behavior in the appconfig_0 folder||Visual Studio Code Extension||Low||No|
Description: An error was causing a weird behavior in the appconfig_0 folder of the VSCode plugin.
| TOR-815||New Feature||Add vim-tiny to development tools container||Low||No|
Description: It is often helpful to be able to quickly edit a device tree overlay file. It would be good to have some kind of editor in the development tools container, e.g. vim-tiny.
| TOR-813||New Feature||Support custom EULA when preprovisioning containers||Low||No|
Description: Some containers such as our base containers with Vivante binary drivers need the customer to accept an EULA. We should support adding an EULA to the Tezi image as part of the pre-provisioning process (in torizoncore-builder).
| TIE-64||Fixed||Visual Studio error: Object reference not set to an instance of an object||Moses (IDE Backend), Visual Studio Extension||Low||No|
Description: On one of the PCs where the extension has been tested, when executing "Deploy and Debug Torizon Application", a dialog pops-up with the error "Object reference not set to an instance of an object".
From this point onwards, it is impossible to deploy and debug Torizon applications, even if a new project is created or Visual Studio is restarted.
There are issues also accessing the debugging options of the project and of any project created using the Visual Studio for Linux extension.
Workaround: Uninstall and Reinstall Visual Studio.
| TOR-804||Fixed||Overlay display_EDT5.7_parallel_res_touch.dts does not work on Apalis iMX6||Apalis iMX6||Low||No|
Description: Overlay display_EDT5.7_parallel_res_touch.dts does not work on Apalis iMX6 (activating the overlay does not show anything on the screen)
| TOR-799||New Feature||Enable spidev by default on Colibri iMX8X||Colibri iMX8X||Open Embedded||Low||No|
Description: By default spidev on Colibri i.MX8X is disabled. It should be enabled by default to be consistent with other Torizon modules.
| TOR-727||New Feature||Enable support of fw_utils based on NAND flash and emmc for colibri-imx7||Low||No|
Description: Currently TorizonCore does not have support for fw_env.conf file(s) for nand and emmc. It is needed for fw_utils to read and set boot environment variables
| TOR-34||Fixed||Qt doesn't work with wayland-vivante container||Apalis iMX8||Low||No|
Description: Applications that use only widgets work when launched in a privileged container mounting /dev, those that require opengl hang.
|4.0.0-devel-202004 Monthly Release|
| TOR-806||New Feature||NXP PCF85363 RTC support||Colibri iMX7, Apalis iMX6, Colibri iMX6||Kernel||Low||No|
Description: Add support for NXP PCF85363 RTC
| TOR-791||New Feature||Development tools container on pre-provisioned images||CI / CD||Low||No|
Description: Add development tools container to pre-provisioned images
| TOR-784||Fixed||Parallel RGB support on Colibri iMX8X||Colibri iMX8X||Low||No|
Description: Enable parallel RGB on Colibri iMX8X by default. Set resolution to 640x480.
| TOR-782||Fixed||torizoncore-builder error on Windows using cmd||Low||No|
Description: torizoncore-builder does not work on Windows using cmd
| TOR-777||New Feature||SHT3x sensor support on i.MX 8 series modules||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Apalis iMX8||Kernel||Low||No|
Description: Add SHT3x sensor support on i.MX 8 series modules
| TOR-776||Fixed||CFS Quota/Period support on i.MX 8 series modules||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X, Apalis iMX8||Low||No|
Description: Enable CFS Quota/Period support on i.MX 8 series modules
| TOR-763||Fixed||U-Boot devicetree overlays support on Verdin modules||Verdin iMX8M Mini||Low||No|
Description: Enable U-Boot devicetree overlays support on Verdin modules
| TOR-738||New Feature||Journald log driver||Low||No|
Description: Enable use of journald log driver.
| TOR-697||New Feature||Toradex Easy Installer Image Server with Zeroconf in a container||Low||No|
Description: Create a container to run Toradex Easy Installer Image Server with Zeroconf
| TIE-108||Fixed||Error on 64-bit .NET Core containers||Visual Studio Code Extension||Low||No|
Description: 64-bit .NET Core container does not work
| TOR-616||Fixed||Qt5 Container on iMX8 not working||Apalis iMX8||Debian Base Containers||Low||No|
Description: Fix an issue that prevents Qt5 Containers to run on iMX8 modules
| TOR-564||New Feature||Timezones support||Open Embedded||Low||No|
Description: Add timezones support in TorizonCore image
| TOR-526||New Feature||Improve Splash Screen display time||Low||No|
Description: Show the splash screen earlier and transition to the UI later to improve splash screen display time
| TOR-515||New Feature||Portainer launch container||Samples||Low||No|
Description: Implement a container to launch Portainer
| TOR-498||New Feature||Verdin iMX8M Mini support||Verdin iMX8M Mini||Low||No|
Description: Add Verdin iMX8M Mini to TorizonCore
| TOR-497||New Feature||Apalis iMX8X support||Apalis iMX8X||Open Embedded||Low||No|
Description: Add Apalis iMX8X support to TorizonCore
| TOR-496||New Feature||Colibri iMX8X support||Colibri iMX8X||Low||No|
Description: Add Colibri iMX8X support
| TOR-469||New Feature||Goodix touchscreen support||Low||No|
Description: Add Goodix touchscreen support to TorizonCore
| TOR-410||New Feature||Tool to manage device tree overlays in the device||Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8||Low||No|
Description: Create a tool to manage device tree overlays on device
| TOR-374||New Feature||Add support to reboot module after update||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: Creating a file under /run/aktualizr-session/need_reboot will trigger automatic reboot.
| TOR-373||New Feature||Splash screen support||Low||No|
Description: Add support for splash screen
| TOR-367||Fixed||Docker Compose does not work with Balena||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: Images running Balena do not support using docker-compose
| TOR-346||New Feature||Support OSTREE for different torizon versions||Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8||Low||No|
Description: OSTREE references have been updated. Check here for the current OSTREE feeds: https://developer.toradex.com/knowledge-base/torizon-update-system#OSTree_Update_From_Toradex_Feeds
| TOR-338||New Feature||Apalis iMX8X support||Apalis iMX8X||Low||No|
Description: Support for Apalis iMX8X
| TOR-312||New Feature||Apalis iMX8 support||Apalis iMX8||Low||No|
Description: Add basic support for Apalis iMX8
| TOR-311||New Feature||Support Mainline Linux for Colibri iMX6ULL||Colibri iMX6ULL||Low||No|
Description: Colibri iMX6ULL is only supported under Toradex Labs. Images can be found on Toradex Easy Installer CI feed.
| TOR-304||New Feature||Use udev to provide Toradex standardized access to devices||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: TorizonCore provides system links to all standard Toradex interfaces (e.g. /dev/ttycolibri0-3, /dev/i2c-colibri)
| TOR-301||New Feature||Colibri iMX8X support||Colibri iMX8X||Low||No|
Description: Support for Colibri iMX8X
| TOR-300||New Feature||Kernel per-process IO accounting support||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: Enable kernel per-process IO accounting.
| TOR-266||New Feature||Real-time TorizonCore image||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: Real time images are available on Toradex Easy installer CI feed.
| TOR-224||New Feature||Colibri iMX6ULL support||Colibri iMX6ULL||Low||No|
Description: Add Colibri iMX6ULL support
| TOR-192||New Feature||Pixman renderer support on non-GPU Modules||Colibri iMX7, Colibri iMX6ULL||Low||No|
Description: Automatically use Pixman renderer on non-GPU Modules
| TOR-166||New Feature||USB-to-Serial converters support on i.MX8||Apalis iMX8||Low||No|
Description: Support USB-to-Serial converters on i.MX8 modules
| TOR-133||New Feature||Bump to latest Linux 5.4 release||Low||No|
Description: Bump the Linux kernel to 5.4 release
| TOR-56||Fixed||Docker --init does not work||Apalis iMX8X, Colibri iMX8X, Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6, Apalis iMX8||Low||No|
Description: The Docker init binary seems to be missing in the root file system
Workaround: Do not use --init, consider using an alternative like tiny-init.
| TOR-54||New Feature||Verdin iMX8M Mini support||Verdin iMX8M Mini||Low||No|
Description: Support for Verdin iMX8M Mini
| TOR-45||Fixed||LVDS Atmel Tochscreen not working||Low||No|
Description: Fix bug that was preventing LVDS Atmel Tochscreen from working properly
| TOR-15||New Feature||Docker seccomp support||Low||No|
Description: Support seccomp in Docker
|Issues in this section are not scheduled yet. Please get in touch with our support if you need to have any of these issues scheduled.
| TOR-1251||Feature Request||Torizon Web UI port usage||All supported modules||Debian Base Containers||Low||No|
Description: Standardize TCP ports used by Web UI applications in TorizonCore.
| TOR-1184||Feature Request||Syntactic Sugar in Device Tree Overlays||All supported modules||Device Tree Overlays||Low||No|
Description: Investigate the effort and make use of the syntactic sugar in device tree overlays.
| TOR-1175||Feature Request||Test automation for TorizonCore||All supported modules||Automated testing||Low||No|
Description: To improve the quality of the software and to reduce time testing nightly/monthly/production releases, we need to automate the tests in the TorizonCore operating system.
| TIE-77||Known Issue||extraparms setting not available in Visual Studio 2019 Application Properties dialog||Visual Studio Extension||No|
Description: This setting can be used to configure additional settings related to container execution.
It's available in Visual Studio Code UI, but not in Visual Studio 2019.
| TOR-1127||Feature Request||Move Debian packages to NXP 5.4 based release||Verdin iMX8M Mini, Apalis iMX8X, Colibri iMX8X||Debian Packages||Low||No|
Description: Move Debian packages to the new NXP 5.4 kernel based release
| TOR-1119||Feature Request||Stateless system support||Open Embedded||No|
Description: Add stateless system support to TorizonCore.
| TIE-98||Known Issue||VS Extension: Adding outside files/folder to the project causes compilation to fail||All supported modules||Moses (IDE Backend)||Low||No|
Description: When trying to add files/folder that are located outside of the the main VS project folder the project folder structure then gets altered. This alteration of the folder structure then causes things like compilation and debugging to fail.
| TIE-14||Known Issue||Apply environment settings to Dockerfile and ssh connection in debug builds||Visual Studio Code Extension||Low||No|
Description: Currently settings added via the "env" property are applied only when the application runs in the release container.
Debugger connects over SSH and those variables are not defined when the application runs.
| TOR-844||Feature Request||Set Custom Logo on Portainer||Low||No|
Description: It is possible to customize the Portainer logo. Toradex logo can be added as example.
Workaround: Go to the Portainer "settings", enable the option "Use custom logo" and paste the URL to your logo.
| TIE-62||Known Issue||VS Code Extension - Error Deploying to Device using WSL 2: can't find a valid IP for apalis-imx8||Visual Studio Code Extension||Low||No|
Description: On Windows 10 Home and WSL 2, when deploying to a device, the following error occurs several times: "Error (545) - Can't find a valid IP for board name". NOTE: Windows 10 Home and WSL 2 are not supported at the moment.
Workaround: Retry to deploy (press F5 for instance) until it works. It may work on 1 out of 10 tries.
| TIE-1||Feature Request||Support C/C++ development in VS Code providing cross-compiling and remote debugging||Visual Studio Code Extension||Low||No|
Description: Developing applications in C/C++ will be supported by the Visual Studio Code extension for Torizon. Cross-compilation and remote debugging will be supported.
| TOR-821||Feature Request||Optimize size of Debian base containers||Debian Base Containers||Low||No|
Description: It is possible to optimize the size of Debian base containers in various ways. This will be investigated and optimizations deployed as the study progresses.
| TIE-12||Known Issue||Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds"||Visual Studio Extension||Low||No|
Description: Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds. Disabling the extension Torizon Visual Studio Development Tools might help". It may be possible to optimize the plugin to avoid it from happening. Despite the latency caused by Visual Studio becoming non-responsive, there are no side-effects reported.
Workaround: Just click "Don't report this extension again".
| TOR-546||Known Issue||Torizon Toolbar Disabled on Torizon Project||Low||No|
Description: After a project is created and configured, if you close Visual Studio and re-open it, the Torizon Toolbar buttons become disabled and cannot be re-enabled.
Workaround: Do not close Visual Studio once you create a project. If you do and come across the error, re-create the project.
| TOR-386||Feature Request||Support ttyRPMSG||Colibri iMX7||Low||No|
Description: Add support for rpmsg
| TOR-319||Known Issue||Colibri iMX6S gets very slow with Docker||Colibri iMX6||Low||No|
Description: Limited amount of memory on iMX6S prevents system from running fast.
| TOR-165||Feature Request||Out of tree drivers support||Kernel||Low||No|
Description: Support to build out of tree Linux kernel drivers
|Issues in this section are not planned to be addressed. Please get in touch with our support if you need to have any of these issues addressed.
| TOR-1081||Known Issue||Arm-32 emulated containers may not work as expected on 64-bit PC host||All supported modules||Debian Base Containers||Low||No|
Description: Our documentation uses qemu to emulate non-native architectures when building containers, this is also what happens when docker is running on Windows.
When a 32-bit platform is emulated on a 64-bit host you may have issues with inodes, this means that functions like readdir may not return the information in a correct way.
This may prevent commands like "update-mime-database" from working when running via emulation.
A workaround is using 32-bit version of qemu to run those containers.
Workaround: On ubuntu-based machines the issue can be fixed by following those steps:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install qemu-user-static
echo -1 | sudo tee /proc/sys/fs/binfmt_misc/qemu-arm
echo -1 | sudo tee /proc/sys/fs/binfmt_misc/qemu-aarch64
echo ':qemu-arm:M:0:\x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-arm-static:CF' | sudo tee /proc/sys/fs/binfmt_misc/register
echo ':qemu-aarch64:M:0:\x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff:/usr/bin/qemu-aarch64-static:CF' | sudo tee /proc/sys/fs/binfmt_misc/register
This will install and enable 32-bit version of qemu.
Workaround has been tested on ubuntu 18.04
| TOR-1073||Feature Request||Verdin iMX8M Mini Quad 2GB IT V1.1A support||Verdin iMX8M Mini||Open Embedded||Low||No|
Description: Support for the new version of the Verdin iMX8M Mini Quad 2GB IT V1.1A.
| TIE-17||Feature Request||Provide LICENSE file for VS Code extension||Visual Studio Code Extension||Low||No|
Description: The Visual Studio marketplace allows providing license information for extensions. Visual Studio Code extension for Torizon has an empty license at the moment.
| TIE-56||Known Issue||VS Code Extension and Python: Debug instance does not start||Visual Studio Code Extension||Low||No|
Description: If a debug instance is started (press F5), stopped (press Shift + F5) and re-started (press F5) in a short time window (less than 5 seconds), the debug instance may simply not start on the second time.
Workaround: Wait a few seconds and re-start the deploy and debug (press F5).
| TIE-82||Known Issue||Error (500) When Try to Debug .NET App||Visual Studio Code Extension||Low||No|
Description: Launching debugger for a .NET app in Visual Studio code a popup reporting error 500 appears.
| TOR-572||Feature Request||Alvium Camera support||Low||No|
Description: Add support for Alvium Camera in Torizon
| TOR-290||Known Issue||Device tree overlays do not support removing property||Colibri iMX7, Colibri iMX6ULL, Apalis iMX6, Colibri iMX6||Low||No|
Description: Device tree overlays do not support removing property
| TOR-282||Known Issue||Debian container shows "No session for pid error" on startup||Colibri iMX7, Apalis iMX6, Colibri iMX6||Low||No|
Description: Debian container shows no PID error.
| TOR-55||Known Issue||Timesync fails after upgrading to latest TorizonCore||Apalis iMX6, Colibri iMX6||Low||No|
Description: After upgrading systemd-timesyncd does not start properly anymore. Starting the service fails with "code=exited, status=238/STATE_DIRECTORY".
Workaround: Delete the old timesync symlink by using: