Configure Torizon OS to use single antenna

Technical Support
, , , ,
1

I see here some steps to configure Torizon OS for single-antenna scenario.

I verified that the default setting of Torizon OS is dual-antenna.

Is there a way to configure Torizon OS for single-antenna scenario while building it with torizoncore-builder?

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I don’t have specific information about configuring single-antenna scenarios during the TorizonCore Builder build process in the available sources. However, I can provide you with an approach to achieve this configuration.

Approach: Capture Configuration Changes

Based on the TorizonCore Builder workflow, you can configure your Torizon OS for single-antenna scenario by capturing the configuration changes after applying them manually, then including those changes in your custom image build.

Steps to Configure Single-Antenna with TorizonCore Builder:

  1. Apply Single-Antenna Configuration Manually

    • First, configure your device for single-antenna mode following the runtime configuration steps you referenced
    • Make the necessary changes to your running Torizon OS device

  2. Capture the Configuration Changes

    • Use the isolate command to capture all configuration changes from your device(1):
$ torizoncore-builder isolate --remote-host <board_ip> --remote-username <username> --remote-password <password> --changes-directory changes1

(1)

  1. Include Changes in Your Custom Image Build
    • Create a configuration file (tcbuild.yaml) that includes your captured changes(1):
# Sample configuration file:
input:
  easy-installer:
    local: images/torizon-core-docker-<your-module>-Tezi_<version>.tar
# Include the captured configuration changes
customization:
  filesystem:
     - changes1/
output:
  easy-installer:
    local: torizon-core-docker-<your-module>-Tezi_<version>.CUSTOM

(1)

  1. Build Your Custom Image
    • Run the build command to generate your custom image(1):
$ torizoncore-builder build

(1)

Why This Approach Works

The isolate command captures all configuration changes made to the /etc directory of your board, including modifications, additions, deletions, and file/directory permissions and ownership(1). This method is specifically designed for capturing system configuration changes that need to be committed to the Torizon OS image(1).

TorizonCore Builder supports capturing device configuration as one of its key features, allowing you to preserve configuration changes made to a target device at runtime during development and embed them into your final OS image(2).

Best regards,
Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hi @vix,

My recommendation would be very similar to what the AI suggested. I would try to isolate the changes from the development platform with TorizonCore builder tool and then build the new custom image with those changes. Have you tried that already?

4

Hi @rudhi.tx

not yet.

I let you know.