# AGX Orin flash and boot up on pcie C0

**URL:** <https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252>\
**Category:** Jetson AGX Orin\
**Tags:** usb, board-design\
**Created:** [November 5, 2025, 8:37am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252 "2025-11-05T08:37:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wilson\_Lin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Wilson\_Lin](https://forums.developer.nvidia.com/u/Wilson_Lin)\
**Post date:** [November 5, 2025, 8:37am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/1 "2025-11-05T08:37:23Z")

</div>

Hi Nvidia,

接續以下topic

> [@AGX Orin flash and boot up on pcie C0](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/346995):
>
> Hi Nvidia, I’m using AGX Orin , customer carrier board, L4T36.4.3 When I flash the OS on Pcie C4. It works fine and pcie C0 can read/write M.2 storage. But when I try to flash OS on C0, the l4t\_initrd\_flash.sh will time out on Step3. Can AGX Orin flash and boot up on C0 Storage?

目前我們針對type-C connect跳線，vbus接到GPIO22，以下是線路圖

[DSC-NV003-WT\_R100\_Type-C.pdf](https://forums.developer.nvidia.com/uploads/short-url/hP0lL7ssdGscrTLxJitfjqbrxQl.pdf) (291.7 KB)

我依照document在usb2-0加入connector

```auto
usb2-0 {
        mode = "peripheral";
        usb-role-switch;
        role-switch-default-mode = "peripheral";
        status = "okay";
        connector {
                compatible = "gpio-usb-b-connector";
                label = "micro-USB";
                type = "micro";
                vbus-gpio = GPIO_ACTIVE_LOW>;
        };
};

```

但目前還無法燒錄

以下是我的device tree

[flash.dts.txt](https://forums.developer.nvidia.com/uploads/short-url/ssvm7tsy6U5D1LoDQmZBscST1YP.txt) (319.6 KB)

---

<div class="post-metadata">

**Author:** ![carolyuu](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/carolyuu/32/14043_2.png) [@carolyuu](https://forums.developer.nvidia.com/u/carolyuu)\
**Post date:** [November 5, 2025, 9:01am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/3 "2025-11-05T09:01:00Z")

</div>

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

The issue you’re facing is related to flashing the OS on PCIe C0 on the Jetson AGX Orin module. You’ve mentioned that flashing on PCIe C4 works fine, but when you try to flash on C0, the `l4tinitrdflash.sh` script times out on Step 3.

Firstly, let’s understand the difference between PCIe C0 and C4 on the Jetson AGX Orin module. PCIe C0 is a PCIe x4 slot, while C4 is a PCIe x1 slot. Both slots can be used for storage, but they have different configurations and requirements.

To flash the OS on PCIe C0, you need to ensure that the storage device is properly configured and connected to the C0 slot. The storage type you’re using is a Type-C device, which requires a specific configuration in the device tree.

The `flashdtb.txt` file you mentioned is used to configure the device tree for the Jetson AGX Orin module. You need to modify this file to enable the PCIe C0 slot and configure it for your storage device.

Here’s a comparison of the device tree configurations for PCIe C0 and C4:

- PCIe C4:
  - Device tree configuration: `pcie-controller@10003000 { ... }`
  - Storage device configuration: `nvme@1 { ... }`

- PCIe C0:
  - Device tree configuration: `pcie-controller@10000000 { ... }`
  - Storage device configuration: `nvme@0 { ... }`

To enable PCIe C0, you need to modify the `flashdtb.txt` file to include the following configuration:

```bash
pcie-controller@10000000 {
    ...
    num-lanes = <4>;
    pci@0 {
        ...
        nvme@0 {
            ...
        }
    }
}

```

Additionally, you need to ensure that the storage device is properly connected to the C0 slot and configured in the device tree.

After modifying the `flashdtb.txt` file, you can try flashing the OS on PCIe C0 again. If you still encounter issues, you may need to check the storage device configuration and the device tree configuration for any errors or inconsistencies.

In summary, to flash the OS on PCIe C0 on the Jetson AGX Orin module, you need to:

1. Modify the `flashdtb.txt` file to enable PCIe C0 and configure it for your storage device.
2. Ensure that the storage device is properly connected to the C0 slot.
3. Check the device tree configuration for any errors or inconsistencies.

By following these steps, you should be able to flash the OS on PCIe C0 successfully.

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

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [November 5, 2025, 9:49am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/5 "2025-11-05T09:49:42Z")

</div>

Is it possible that you make a design of micro usb port first instead of type C? I feel that type C port has lots of problem here.

---

<div class="post-metadata">

**Author:** ![Wilson\_Lin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Wilson\_Lin](https://forums.developer.nvidia.com/u/Wilson_Lin)\
**Post date:** [November 24, 2025, 6:40am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/7 "2025-11-24T06:40:02Z")

</div>

Hi Wayne,

Our HW team make a micro usb port right now. How could I test it to flash the cpie C0?

The topic will close. Could I need to open a new topic to countie this issue?

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [November 24, 2025, 6:55am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/8 "2025-11-24T06:55:57Z")

</div>

All the procedure is same. You need to write a correct device tree to match your ID pin and vbus det pin for your custom board. Try initrd flash command and check if usb device mode is correctly running.

Basically all the concept is already listed in previous post.

> [@AGX Orin flash and boot up on pcie C0](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/346995/):
>
> Hi Nvidia, I’m using AGX Orin , customer carrier board, L4T36.4.3 When I flash the OS on Pcie C4. It works fine and pcie C0 can read/write M.2 storage. But when I try to flash OS on C0, the l4t\_initrd\_flash.sh will time out on Step3. Can AGX Orin flash and boot up on C0 Storage?

---

<div class="post-metadata">

**Author:** ![Wilson\_Lin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Wilson\_Lin](https://forums.developer.nvidia.com/u/Wilson_Lin)\
**Post date:** [November 24, 2025, 10:03am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/9 "2025-11-24T10:03:43Z")

</div>

Hi Wayne,

We connect the vbus pin to GPIO22.  
And we don’t connect the id pin to gpio.  
For the Xaver NX Carrier board. The micro usb id pin doesn’t connect to NX. But it can flash the pcie C0.

I set the usb2-0 to mode = “peripheral”;  
But still failed.

This is the dtb.  
[tegra234-p3737-0000+p3701-0004-nv.dts.txt](https://forums.developer.nvidia.com/uploads/short-url/4Alx4cuXIXALS0NQpSiCe8rSwKG.txt) (319.4 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [November 24, 2025, 1:31pm UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/10 "2025-11-24T13:31:23Z")

</div>

Why do you remove this from your device tree when you need it…?

```auto
        connector {
                compatible = "gpio-usb-b-connector";
                label = "micro-USB";
                type = "micro";
                vbus-gpio = < your_GPIO GPIO_ACTIVE_LOW>;

```

It is there in your first comment but didn’t appear anymore in your actual dts.

---

<div class="post-metadata">

**Author:** ![Wilson\_Lin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Wilson\_Lin](https://forums.developer.nvidia.com/u/Wilson_Lin)\
**Post date:** [November 25, 2025, 2:33am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/11 "2025-11-25T02:33:56Z")

</div>

Hi Wayne,

I have added the connector. But still failed.  
[tegra234-p3737-0000+p3701-0004-nv.dts.txt](https://forums.developer.nvidia.com/uploads/short-url/3HhGDzoujXd4nZA6kKr4gswWglx.txt) (319.6 KB)

---

<div class="post-metadata">

**Author:** ![Wilson\_Lin](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@Wilson\_Lin](https://forums.developer.nvidia.com/u/Wilson_Lin)\
**Post date:** [November 25, 2025, 3:25am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/13 "2025-11-25T03:25:38Z")

</div>

Hi Wayne,

The PCIE C0 can be flashed.

I edit the nvidia,usb2-companion form 0 to 1.

```auto
usb3-1 {
                                        nvidia,usb2-companion = <1>;
                                        status = "okay";
                                };

```

之前你有解釋說  
usb3-1沒有跟usb2-0搭配，需要拿掉  
但因為我註解掉  
nvidia,usb2-companion = \<0\>;時，dtb會出錯無法燒錄，  
因為我們需要用到USB3-1，所以我就一直放著，沒想到這是主因。

不好意思這問題打擾你很久，真的非常感謝你的解釋問題和幫助，謝謝。

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [December 9, 2025, 3:26am UTC](https://forums.developer.nvidia.com/t/agx-orin-flash-and-boot-up-on-pcie-c0/350252/14 "2025-12-09T03:26:15Z")

</div>

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