Skip to content

Commit

Permalink
Merge pull request #3099 from balena-io/add_fan_powermode_info
Browse files Browse the repository at this point in the history
pages/learn: Add fan profile and power mode information
  • Loading branch information
acostach authored Dec 17, 2024
2 parents 3a52680 + ef6d2aa commit 9d1dfaa
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 0 deletions.
1 change: 1 addition & 0 deletions .cspell/computer-terms.txt
Original file line number Diff line number Diff line change
Expand Up @@ -277,6 +277,7 @@ ntpdata
ntpservers
nuctest
NVMe
nvpmodel
OCPDIR
Octalbonescript
odroid
Expand Down
10 changes: 10 additions & 0 deletions pages/learn/develop/hardware/i2c-and-spi.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ title: I2C and Other Interfaces
* [Serial ports](/hardware/i2c-and-spi#serial-ports)
* [Jetson Devices](/hardware/i2c-and-spi#jetson-devices)
* [Custom device trees](/hardware/i2c-and-spi#custom-device-trees)
* [Configurable fan profiles](/hardware/i2c-and-spi#configurable-fan-profiles)
* [Configurable power modes](/hardware/i2c-and-spi#configurable-power-modes)

## Raspberry Pi Family

Expand Down Expand Up @@ -348,6 +350,14 @@ After the custom device tree has been validated, it can be included in newer bal

Please note that if the changes for your carrier board expand past kernel device-trees, or require modifications to board configuration files like pin multiplexing configuration files or any other device-trees or files used by firmware, these may not be provided by the existing cloud images. During provisioning the resulting configuration changes are stored in the QSPI or in the hardware defined boot partitions, and thus will be replaced with the default values when updating the Host Operating System. Please [contact us](https://www.balena.io/contact-sales) if you would like to use a Jetson carrier board which may not be fully compatible with its' corresponding devkit, or with any of our cloud images for your Jetson module.

### Configurable fan profiles

Jetson Orin Devices running balenaOS revisions newer than v6.1.24 and supervisor versions greater than v16.10.0 offer support for configurable fan profiles. You can switch between the options provided by Jetpack by navigating to the Device/Fleet Configuration tab on the sidebar of the balenaCloud dashboard, clicking "activate" on the "Define the device fan profile" configuration option, and typing in the desired value. The input value should be a string, without quotes. The change will be applied at runtime and will not trigger a device reboot. Preloading the [fan profile configuration](/reference/OS/configuration/#fanprofile) before provisioning your device can be achieved by editing the [config.json](/reference/OS/configuration/#about-configjson) file.

### Configurable power modes

Jetson Orin Devices running balenaOS revisions newer than v6.1.24 and supervisor versions greater than v16.10.0 also offer the possibility for selecting the desired power mode. You can set the values *low*, *mid* and *high* or specify the power mode index directly by navigating to the Device/Fleet Configuration tab on the sidebar of the balenaCloud dashboard, clicking "activate" on the "Define the device power mode" configuration option, and typing in the desired value. The input value should be a string, or a single digit number, without quotes. Please note that your device(s) will automatically reboot to apply the new power mode. The available power modes indexes for your device type are visible in the host OS in `/etc/nvpmodel.conf`. Preloading the desired power mode configuration can be achieved by editing the [config.json](/reference/OS/configuration/#about-configjson) file and specifying the desired [power mode](/reference/OS/configuration/#powermode) before provisioning the device.

### Container packages

The Jetson specific packages installed in your container images need to be in sync with the Linux for Tegra version used by the Host Operating System. Our base images for Jetson devices come pre-populated with `/etc/apt/sources.list.d/nvidia.list` files, which include the necessary links so that the apt repositories are in sync with the L4T version used by our latest OS images. If you suspect you encountered a mismatch, please check the `L4T` version in your Host OS using `uname -r` and compare it to the release version in your container's `/etc/apt/sources.list.d/nvidia.list` file. Please check our [Jetson Examples](https://github.com/balena-io-examples/jetson-examples) repository for more information on how to set-up your container images.
Expand Down

0 comments on commit 9d1dfaa

Please sign in to comment.