jetson_agx_orin_development
差異處
這裏顯示兩個版本的差異處。
| Both sides previous revision 前次修改 下次修改 | 前次修改 | ||
|
jetson_agx_orin_development [2024/03/19 17:42] don [Modified] |
jetson_agx_orin_development [2024/04/16 15:34] (目前版本) don [AGX Stable Diffusion] |
||
|---|---|---|---|
| 行 13: | 行 13: | ||
| Before JetPack 5.1.1\\ | Before JetPack 5.1.1\\ | ||
| Jetson Orin module to be emulated Flashing command\\ | Jetson Orin module to be emulated Flashing command\\ | ||
| - | Jetson AGX Orin 64GB sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1\\ | + | Jetson AGX Orin 64GB\\ '' |
| - | Jetson AGX Orin 32GB sudo ./flash.sh jetson-agx-orin-devkit-as-jao-32gb mmcblk0p\\ | + | Jetson AGX Orin 32GB\\ '' |
| - | Jetson Orin NX 16GB sudo ./flash.sh jetson-agx-orin-devkit-as-nx16gb mmcblk0p1\\ | + | Jetson Orin NX 16GB\\ '' |
| - | Jetson Orin NX 8GB sudo ./flash.sh jetson-agx-orin-devkit-as-nx8gb mmcblk0p1\\ | + | Jetson Orin NX 8GB\\ '' |
| - | Jetson Orin Nano 8GB* sudo ./flash.sh jetson-agx-orin-devkit-as-nano8gb mmcblk0p1\\ | + | Jetson Orin Nano 8GB*\\ '' |
| - | Jetson Orin Nano 4GB sudo ./flash.sh jetson-agx-orin-devkit-as-nano4gb mmcblk0p1\\ | + | Jetson Orin Nano 4GB\\ '' |
| 行 27: | 行 27: | ||
| sudo ./flash.sh jetson-agx-orin-devkit internal | sudo ./flash.sh jetson-agx-orin-devkit internal | ||
| </ | </ | ||
| + | |||
| + | ==== Build Kernel ==== | ||
| + | < | ||
| + | export CROSS_COMPILE_AARCH64_PATH=$HOME/ | ||
| + | export CROSS_COMPILE_AARCH64=$HOME/ | ||
| + | cd ~/ | ||
| + | mkdir kernel_out | ||
| + | ./ | ||
| + | cd ../../ | ||
| + | ./fl.sh | ||
| + | </ | ||
| ==== Install Vscode on Target Device ==== | ==== Install Vscode on Target Device ==== | ||
| 行 122: | 行 133: | ||
| </ | </ | ||
| - | === 3. https:// | + | === 3. Get deepstream-6.3_6.3.0-1_arm64.deb |
| - | Get deepstream-6.3_6.3.0-1_arm64.deb for Jetson not to download for x86\\ | + | [[https:// |
| - | < | + | |
| + | <color #ed1c24>Get deepstream-6.3_6.3.0-1_arm64.deb for Jetson not to download for x86</ | ||
| + | < | ||
| === 4. Copy the generated libraries to the deepstream directory: | === 4. Copy the generated libraries to the deepstream directory: | ||
| 行 187: | 行 200: | ||
| < | < | ||
| - | === Fan Control === | + | ==== Fan Control |
| < | < | ||
| FAN_DEFAULT_PROFILE cool \\ | FAN_DEFAULT_PROFILE cool \\ | ||
| 行 193: | 行 206: | ||
| < | < | ||
| - | === Power Mode Setting === | + | ==== Power Mode Setting |
| Nvidia Power Model Tool to config ID=0 “MAXN” \\ | Nvidia Power Model Tool to config ID=0 “MAXN” \\ | ||
| 行 200: | 行 213: | ||
| < | < | ||
| - | === AGX Stable Diffusion === | + | ==== AGX Stable Diffusion ==== |
| + | |||
| + | [[https:// | ||
| < | < | ||
| - | https:// | + | git clone https:// |
| cd stable-diffusion | cd stable-diffusion | ||
| git checkout jetson | git checkout jetson | ||
| + | cp ~/ | ||
| ./ | ./ | ||
| python3 scripts/ | python3 scripts/ | ||
| </ | </ | ||
| - | === JETSON AGX Orin performance test === | + | ==== JETSON AGX Orin performance test ==== |
| https:// | https:// | ||
| - | |||
| - | |||
| < | < | ||
| 行 306: | 行 321: | ||
| </ | </ | ||
| + | |||
| + | |||
| + | ===== Pinmux Changes ===== | ||
| + | |||
| + | If your carrier board schematic differs from that of the reference carrier board in Jetson Xavier NX Developer Kit, you must change the pinmux configuration applied by the software. | ||
| + | |||
| + | To define your board’s pinmux configuration, | ||
| + | |||
| + | The pinmux table is a spreadsheet that: | ||
| + | |||
| + | * Shows the locations and default pinmux settings | ||
| + | |||
| + | * Acts as a data source for software that defines the pinmux settings in the source code or device tree | ||
| + | |||
| + | You must customize the spreadsheet for the configuration of your board, then convert the .dtsi file generated by Excel to a .cfg file. For instructions, | ||
| + | |||
| + | Linux_for_Tegra/ | ||
| + | You must perform the same conversion for gpio.dtsi and padvoltage.dtsi. | ||
| + | |||
| + | |||
| + | |||
| + | [[https:// | ||
| + | |||
| + | ===== GPIO Changes ===== | ||
| + | If you designed your own carrier board, to translate from SOM connector pins to actual GPIO numbers you must understand the GPIO mapping formula below. The translated GPIO numbers can be controlled by the driver. | ||
| + | |||
| + | To check a GPIO number | ||
| + | This example procedure checks the GPIO number of signal name SPI0_CS1. | ||
| + | |||
| + | - Open the Jetson AGX Orin pinmux table. (See Pinmux Changes, above.) | ||
| + | - Search the table for SPI0_CS1. | ||
| + | - Confirm that the Customer Usage field contains the GPIO name GPIO3_PZ.07. | ||
| + | - Search PZ.07 using the following command: | ||
| + | |||
| + | cat / | ||
jetson_agx_orin_development.1710841366.txt.gz · 上一次變更: 2024/03/19 17:42 由 don
若無特別註明，本 wiki 上的內容都是採用以下授權方式： CC Attribution-Share Alike 4.0 International
