It looks like you have successfully installed 6.1.0 TorizonCore operating system based on your systeminfo.
TorizonCore isn’t a Debian based image, so that is why you do not see the APT tool. Although you can start a Debian based container on the device and use/install the tools you need. But it is important to understand how containers work when you are developing inside of them (work done inside is generally considered not persistent and will discarded when the container closes. So it’s important to have an rough understanding on how to use containers.
For application development we recommend using container tools such as Docker. And we have guides on our developer website. Here is a link for Debian Containers for Torizon. Poking around on the developer site is a great way to find specific ways to achieve what you need.
Are you also using TorizonCore Builder to build your image? There are also great resources on what can be achieved with this tool. Torizon Core Builder Tool Info
so torizoncore is not “modifiable”, aka read-only exept /var, i see dependencies to os-tree, is this similar to lets say "fedora silverblue? meaning, there is no package manager at all. is there a solution similar to fedoras rpm-ostree to upgrade the OS?
I’m not familiar with Fedorda Silverblue other than it states its an immutable OS. TorizonCore doesn’t have a built in package manager but you can modify the OS based on what you need. Modifications of the OS would be OS Customizations. And how you do this is based on how you are building the image. Are you building TorizonCore with our TorizonCore Builder tool or Yocto?
There is a distinction between modifying the OS and modifying the application running on the OS. A short description of work flow: Toradex maintains the OS, you add your customization to the OS via our tools (or yocto) , and you add your application on top (via containers).
Here is a write up on how we are using OSTREE for updating. Torizon Updates
ext4load is built-in command for u-boot, which is the bootloader that is used with TorizonCore, so this specific command It would be available while in u-boot terminal and not within a container.
A.) torizoncore is not “modifiable”: ive now learned to use the “ostree” utility to upgrade/downgrade the host OS torizon. except /etc /var its not indended to be modified as a “ostree” up-/downgrade would reset all configuration anyhow. → SOLVED.
B.) Working with the MCU. Ive now learned that utilities like “ext4load” etc are accessible from the bootloader (halt the boot process by pressing space to land in the bootloader shell (uboot).
→ SOLVED as far as it goes to work through the examples in the documentation.
B.1.) Is it possible to controll the Cortex-M from within a Container running on the host? So stopping, starting, flashing the MCU while the host OS torizon is fully running?
Regarding question C, in order to do that, you will need to access the files inside /sys/class/remoteproc on the TorizonCore filesystem. You can’t simply bind mount them to the container because these files are in RO mode and need root privileges to access. So, in his case, you will need to create a container that has access to these files. It should be possible with some flags that you can pass to the docker run command, although I’ve never tested them.
I will try to run that on my side to check if there is an easy way to do that.