Modifying Kernel Arguments with TorizonCore Builder
There are two main approaches to modify kernel arguments using TorizonCore Builder:
Method 1: Using the Build Command with Configuration File
You can modify kernel arguments by creating a tcbuild.yaml configuration file (1):
customization:
kernel:
arguments:
- console=ttyLP0,115200
- loglevel=3
(1)
This approach is recommended for production programming and CI/CD pipelines (2).
Method 2: Using Individual Commands
Set Custom Kernel Arguments
Use the kernel set_custom_args command to define custom arguments (3):
$ torizoncore-builder kernel set_custom_args "param1=val1" "param2=val2"
'custom-kargs_overlay.dts' compiles successfully.
Overlay custom-kargs_overlay.dtbo successfully applied.
Kernel custom arguments successfully configured with "param1=val1 param2=val2".
(3)
Important: Every time you execute the kernel set_custom_args command, the custom-kargs_overlay.dts is overwritten, so you should pass all kernel arguments in a single set_custom_args command (2).
Check Current Arguments
To see what custom kernel arguments are currently configured (3):
$ torizoncore-builder kernel get_custom_args
Currently configured custom kernel arguments: "param1=val1 param2=val2".
(3)
Clear Arguments
To remove all custom kernel arguments (3):
$ torizoncore-builder kernel clear_custom_args
Custom kernel arguments successfully cleared.
(3)
For Your Serial Console Use Case
To disable the serial console, you would want to remove or modify the console parameter. You can set custom kernel arguments that override the default console setting (2). The custom arguments are appended to the default kernel arguments defined in the image (3).
Complete Workflow
- Unpack a base image (2):
$ torizoncore-builder images unpack torizon-core-docker-colibri-imx6-Tezi_5.3.0+build.7.tar
(2)
- Set your custom kernel arguments (2):
$ torizoncore-builder kernel set_custom_args "console="
- Build your custom image using either the build command with a configuration file or the union command (2).
The kernel arguments are stored in a device tree overlay, so you can verify they’re applied using dto status (2).
Best regards, Toradex AI Assistant.
Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.