Select the version of your OS from the tabs below. If you don't know the version you are using, run the command
cat /etc/os-release or
cat /etc/issue on the board.
Remember that you can always refer to the Torizon Documentation, there you can find a lot of relevant articles that might help you in the application development.
During the development process with TorizonCore, usually it is required to capture configuration changes on the
/etc directory that needs to be committed to the TorizonCore image.
Here are some examples of articles describing procedures that require changes in the configuration of the system.
This article shows how to capture these system configurations.
This article complies to the Typographic Conventions for Torizon Documentation.
The pre-requisite to complete these instructions are:
To use TorizonCore Builder, you need to create an alias. Follow the installation instructions on the TorizonCore Builder article. Make sure to:
If the user has made any configuration changes, e.g., the
/etc directory, the
isolate command will get all those changes (modifications, addition, and deletion). It requires an ssh connection for the communication between the host PC and the target board.
Get configuration changes from the target board
$ torizoncore-builder isolate --remote-ip 192.168.1.146 --remote-username torizon --remote-password 1234 isolation command completed
Merge changes to base Toradex Easy Installer image of Torizon. Use any "--union-branch" name you want; as example we use
$ torizoncore-builder union --union-branch=changes_committed Commit d77ed9d5ddec41b7b61f9a571e810de2447133391ee19fe5f34d1a81009967d1 has been generated for changes and ready to be deployed.
Set the branch
changes_committed created in the previous command to deploy at boot. The output image can be deployed on the target board:
$ torizoncore-builder deploy --output-directory deployed_image d77ed9d5ddec41b7b61f9a571e810de2447133391ee19fe5f34d1a81009967d1
Note: Optionally, you can deploy the previously created
changes_committed branch directly on the target board:
$ torizoncore-builder deploy d36d7f8b393e9226af780d16c0813eaa087fd35ff1251c86b5dc0d61a9ca29b3 --remote-host 192.168.1.111 --remote-username torizon --remote-password 1234