Skip to content

Commit 6d8e48c

Browse files
committed
shared/jetson-orin: Specify device-type slugs for Seeed and Orin NX
These three Orin devices used to have common instructions, but now that they have individual pages, we can specify their slugs directly in the instructions. Change-type: patch Signed-off-by: Alexandru Costache <[email protected]>
1 parent d20834f commit 6d8e48c

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

shared/jetson-orin/jetson-orin-nano-seeed-j3010.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,10 +170,10 @@ carrier board before starting the provisioning process.
170170

171171
1) Make sure you have <a href="https://jqlang.org/download/">jq</a> and the <a href="https://docs.balena.io/reference/balena-cli/latest/">balena CLI</a> installed on your host/development PC. You can obtain it from <a href="https://github.com/balena-io/balena-cli/blob/master/INSTALL.md">here</a>.
172172

173-
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one. Use the <a href="https://docs.balena.io/reference/hardware/devices/">balena device type list</a> to obtain the device-type SLUG (machine name).
173+
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one.
174174

175175
```shell
176-
balena os download <device-type slug> -o balena.img
176+
balena os download jetson-orin-nano-seeed-j3010 -o balena.img
177177
```
178178

179179
3) Download a configuration file from your balenaCloud dashboard or generate a new one using the balena CLI:

shared/jetson-orin/jetson-orin-nx-seeed-j4012.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,10 +166,10 @@ carrier board before starting the provisioning process.
166166

167167
1) Make sure you have <a href="https://jqlang.org/download/">jq</a> and the <a href="https://docs.balena.io/reference/balena-cli/latest/">balena CLI</a> installed on your host/development PC. You can obtain it from <a href="https://github.com/balena-io/balena-cli/blob/master/INSTALL.md">here</a>.
168168

169-
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one. Use the <a href="https://docs.balena.io/reference/hardware/devices/">balena device type list</a> to obtain the device-type SLUG (machine name).
169+
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one.
170170

171171
```shell
172-
balena os download <device-type slug> -o balena.img
172+
balena os download jetson-orin-nx-seeed-j4012 -o balena.img
173173
```
174174

175175
3) Download a configuration file from your balenaCloud dashboard or generate a new one using the balena CLI:

shared/jetson-orin/jetson-orin-nx-xavier-nx-devkit.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -168,10 +168,10 @@ carrier board before starting the provisioning process.
168168

169169
1) Make sure you have <a href="https://jqlang.org/download/">jq</a> and the <a href="https://docs.balena.io/reference/balena-cli/latest/">balena CLI</a> installed on your host/development PC. You can obtain it from <a href="https://github.com/balena-io/balena-cli/blob/master/INSTALL.md">here</a>.
170170

171-
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one. Use the <a href="https://docs.balena.io/reference/hardware/devices/">balena device type list</a> to obtain the device-type SLUG (machine name).
171+
2) Download the balenaOS image from the balenaCloud dashboard or use the balena CLI to obtain one.
172172

173173
```shell
174-
balena os download <device-type slug> -o balena.img
174+
balena os download jetson-orin-nx-xavier-nx-devkit -o balena.img
175175
```
176176

177177
3) Download a configuration file from your balenaCloud dashboard or generate a new one using the balena CLI:

0 commit comments

Comments
 (0)