We continue to follow the Toradex release cycles, and with the August v6.3.0 quarterly release, I am also happy to announce the release of "TorizonCore Community" v6.3.0. Now with new identity and organization, with the name Common Torizon!

Below we will highlight the main news of this release.

We now have an organization to maintain projects, documentation, issues and discussions on GitHub: https://github.com/commontorizon

What I was calling before "TorizonCore Community" is now Common Torizon:

And it's always good to remember that Common Torizon is a work of the community, driven by the community. And contributions are always welcome! The name and identity change was necessary to differentiate from the official TorizonCore released by Toradex for Toradex hardware.

⚠️ Torizon™ is a registered trademark of Toradex Group AG. Common Torizon is not reviewed, affiliated with or endorsed by Toradex. I do not answer for Toradex.

Support for MACHINE beagleplay has been added. Creates Common Torizon images for BeaglePlay by BeagleBoard.org, based on the TI Sitara AM625 SoC.

Support for MACHINE raspberrypi0-2w-64 has been added. Creates Common Torizon images for the Raspberry Pi Zero 2 W, based on the Broadcom BCM2710 SoC.

In the MACHINE intel-corei7-64 images, a service has been added to register the interpreter of armv7 and armv8 architectures. Thus improving the experience while provisioning x86_64 devices on torizon.io. Previously, the user had to manually register the interpreter, and then run the provisioning command. Now the experience is the same as with an ARM device.

MACHINE raspberrypi3-64 and raspberrypi4-64 images, now support automatic rollback of OTA updates. Which means if an update breaks the system, the device will automatically roll back to the previous version. This was a feature not implemented in version v6.2.0.

⚠️ In addition to the new features listed here, the project also inherits all the fixes and new features from the official TorizonCore. Take a look at the TorizonCore v6.3.0 release notes.

For ease of use and evaluation of the Torizon ecosystem, the project already provides pre-built images of torizon-core-common-docker-dev: https://github.com/commontorizon/meta-common-torizon/releases/tag/v6.3.0-common

The available images are for the MACHINE:

• beagleplay
• beaglebone-yocto
• intel-corei7-64
• nezha-allwinner-d1
• raspberrypi4-64
• raspberrypi3-64
• raspberrypi0-2w-64

You can create Common Torizon images in two "flavors":

• torizon-core-common-docker-dev

  • Common Torizon with the Docker runtime and dependencies;
  • Debug tools integrated into the image;
  • Linux kernel with support for KGDB and debug symbols;

• torizon-core-common-docker

  • Common Torizon with the Docker runtime and dependencies;

The pre-built images are all torizon-core-common-docker-dev.

With the new organization on GitHub created, it was easier and clearer how to contribute to the project. And with that we had new contributors in this release. Thank you all!

• Drew Moseley
  • Contributed with support for Raspberry Pi Zero 2 W;
• Stefano Viola
  • Contributed with the OTA rollback for Raspberry Pi;

We are still at the beginning of the project, but we are already evolving as a community. And this is very good! Torizon is a very interesting and promising ecosystem, and I believe that Common Torizon can also bring Torizon ease of use for embedded Linux beyond Toradex hardware. And with that, help the community, both maker and professional, to create more robust, safe and reliable solutions, in an easy, fun and productive way.

There is still much to be done. In the next releases we will continue working, the focus will be on feature parity with the official TorizonCore on hardware platforms with more community usage.