Reflash only partitions affected by pinmux spreadsheet output (AGX Orin R35.4.1)

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

We have a custom AGX Orin board running R35.4.1 that we would like to update the pinmux for. We could reflash it completely, but would like to reflash only those partitions that are affected by changes to the pinmux spreadsheet. We have already fully flashed other units, but would like to only update the pinmux for some units.

It looks like we can do that with something like

sudo ./flash.sh -r -k MB1_BCT jetson-agx-orin-devkit mmcblk0p1

but is MB1_BCT the only partition where the pinmux value changes will exist, or are there others. If so, which?

Thanks in advance!

2

*** Please note that this reply is generated by LLM automatically ***

To update the pinmux on your custom AGX Orin board running R35.41, you can use the image-based over-the-air (OTA) update feature. This allows you to update specific partitions without reflashing the entire board.

The pinmux values are stored in the MB1BCT (Boot Configuration Table) partition. However, there are other partitions that may be affected by changes to the pinmux spreadsheet.

According to the documentation, the following partitions may need to be updated when changing the pinmux:

  • MB1BCT: This partition contains the boot configuration table, which includes the pinmux settings.
  • kernel-dtb: This partition contains the device tree binary, which may need to be updated to reflect changes to the pinmux.
  • dtb: This partition contains the device tree blob, which may need to be updated to reflect changes to the pinmux.

To update only the pinmux-related partitions, you can use the following command:

sudo flash.sh -k MB1BCT -k kernel-dtb -k dtb <other_options>

This command will update the MB1BCT, kernel-dtb, and dtb partitions with the new pinmux settings.

Note that you should only update the partitions that are affected by the changes to the pinmux spreadsheet. Updating other partitions may cause unintended changes to your system.

It’s also important to note that the flash.sh command is used to update the partitions, and the -k option is used to specify the partitions to update. The <other_options> placeholder should be replaced with any additional options required for your specific use case.

In comparison to reflashing the entire board, updating only the pinmux-related partitions is a more targeted approach that can save time and reduce the risk of introducing unintended changes to your system. However, if you’re unsure about which partitions need to be updated or if you’re making significant changes to the pinmux, it may be safer to reflash the entire board to ensure that all necessary partitions are updated correctly.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

Hi,

We strongly recommend flashing the entire QSPI.

Please refer to the examples flash only QSPI section in the NVIDIA Jetson Linux Developer Guide for detailed instructions.

Thanks

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.