Agx orin custom carrier board ,standalone module configurations

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hi
Let me tell you about my situation. We are working on jetson agx orin modules
what we have :

  • It includes the following:
    We have AGX Orin devkit module (P3701-0000 Developer Kit module) and AGX Orin devkit
    Jetson AGX Orin reference carrier board (P3737-0000)

  • Then I designed a carrier. The pins and pinmuxes are the same as the devkit carrier, but there’s no data in the eeprom.

  • Then we bought a standalone module (P3701-0004) (id 7223) that’s 32GB, not flashed.

When I plug the devkit module (P3701-0000 Developer Kit module) into my design custom carrier, the USB, Display Port, and all other functions work, but

When I try to flash standalone module in my custom carrier, the Jetson AGX Orin appears as 32GB in the Target Hardware section of the SDK Manager . (I’m not sure if it’s because the eeprom is empty or the module doesn’t have a devkit ID. so not like in devkit )

Then I flash it in preconfig mode this time, linux is okay but ,it doesn’t see the USB drives. Can you help?
Do I need to edit the device trees? Could you create a system from scratch that shows me the way to do it?

Also, is the reason why I can’t select the device target as devkit in the SDK Manager due to the carrier or module ID?I would appreciate it if you could specify which of the two

The carrier I designed has the same pinout as the Jetson AGX Orin reference carrier board (P3737-0000).
So, I don’t understand why it’s not working even though I flashed it.
When this target hardware(P3701-0004 Developer Kit module) )is selected, doesnt it implement devkits (P3701-0000 Developer Kit module) existing configs bsp and all other configs ? is it setting a different default config for (P3701-0004 Developer Kit module)(so not settled )?

Also, what do I need to configure one by one? Is there any documentation?

Where can I find sample devkit SDK images?

2

Hello @electronxx,

Quick question, just to make sure I am getting it right.

When you say:

You mean that the stand alone module should be 64GB instead?

I am a bit confused because you mentioned that the module was 32GB here:

Then you mention that is weird that it shows as 32GB module on SDK manager.. so I am a bit confused there.

Any way, I guess the issue is that when you flash it the USB ports on the orin do not work as expected, right ?

best regards,
Andrew
Embedded Software Engineer at ProventusNova

5

image
image1024×651 121 KB

  1. combination : custom carrier + standalone Jetson AGX Orin 32GB-DRAM (P3701-0004) sdk view above (USB Ports not working)
    —————————————————————————————————————————————————

    1. combination:
      (P3701-0000 Developer Kit module) +custom carrier board (everything is okay ,usbs are okay )
      ———————————————————————————————————————————————————–
    2. combination (This image is representative of the 64 or 32 GB devkit module. You can choose the image. its devkit)
      and below
      here sdk view of that combination
      (P3701-0000 Developer Kit module) +
      Jetson AGX Orin reference carrier board (P3737-0000) its already devkit kit so just for sdk view

image
image1024×655 90.3 KB

image
image991×636 105 KB

7

Hello @electronxx,

Just out of curiosity, what happens if you first flash your stand alone SOM on the DevKit and then you re-try flashing it on your custom carrier?

best regards,
Andrew
Embedded Software Engineer at ProventusNova

8

Hi, @proventusnova
I couldn’t try that combination because I don’t have the devkit with me.

Combination: custom carrier + standalone Jetson AGX Orin 32GB-DRAM (P3701-0004). Linux displays the image. Then, after Linux boots up, the USB ports don’t work. This is the message I receive.
Do you think this is related to the device tree and kernel configurations? Actually, I am a hardware engineer, but I also took over the flashing work.

image
image1920×1440 550 KB

image
image1920×1440 528 KB

image
image1920×1440 570 KB

9

@electronxx,

We helped one of our clients fix a similar issue recently with their custom built AGX Orin carrier. Just like you they were also HW engineers, which I find to be a pleasant coincidence.

At the end, we found the issue was the pinmux and device tree configuration. That being said, I don’t think that could be the case in your specific station, since that same pinmux and DTB you are flashing to your Devkit SOM via your custom carrie board and is working as expected.

I would lean towards thinking that there is something that is already flashed in devkit SOM and not flash on your stand alone module, that for some reason the flashing procedure is failing to flash. And that is causing USB issues.

I see in the last image you sent, the very last message recommends checking the systemctl status of a service. Can you try running that command and sharing its output ?

best regards,
Andrew
Embedded Software Engineer at ProventusNova

10

@proventusnova
thanks for ur feedback There’s an eeprom for an id on my custom carrier, but it’s not programmed. Another issue is that the standalone Jetson AGX Orin 32GB-DRAM (P3701-0004) id isn’t P3701-0000 like in the devkit, but perhaps it’s creating a generic device tree.
Therefore, I think there might be an error in the cvb and cvm read commands.

12

I fixed , it was because of ı dont have usb pd IC ,in device tree, usb pd was blocking usb c ports,it has aalso dependicies with other usb ports ,i changed device tree and compile dtb again,I learned the kernel structure in 8 days thanks to AI
its working thank you