Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pages/learn: Add fan profile and power mode information #3099

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

pages/learn: Add fan profile and power mode information #3099

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions pages/learn/develop/hardware/i2c-and-spi.md
View file
Open in desktop
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 <TODO> and supervisor versions greater than <TODO> 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 in the balenaCloud dashboard and selecting the desired option. The change will be performed during runtime and doesn't 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 <TODO> and supervisor versions greater than <TODO> also offer the possibility for selecting the desired power mode. You can choose between "low", "mid" and "high" or specify the power mode index directly by navigating to the Device/Fleet Configuration tab on the sidebar in the balenaCloud dashboard. 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
Loading