Jetson Orin Devkit schematics duality

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

Hello,

Can someone please explain the presence of two sets of Devkit schematics PDFs? The file names are: P3768_A04_Concept_schematics.pdf and P3768_A04_OrCAD_schematics(base_version).pdf.

(The former file appears to have a lot more ‘no stuff’ parts.)

2

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

The presence of two sets of Devkit schematics PDFs, specifically P3768A04_Concepts_schematics.pdf and P3768A04_OrCAD_schematics_base_version.pdf, is likely due to the different design tools and purposes they serve.

  1. P3768A04_Concepts_schematics.pdf: This file appears to have more components and details, which might be related to the conceptual or high-level design of the Jetson Orin NX Devkit. It could include additional components, such as no-stuff parts (components that are not populated on the board), which are used for design and testing purposes. This file might be used for:
    • High-level design and planning
    • Component selection and verification
    • Design reviews and discussions
    • Documentation and reference purposes
  2. P3768A04_OrCAD_schematics_base_version.pdf: This file seems to be a more simplified version of the schematic, possibly generated from the OrCAD design tool. OrCAD is a popular electronic design automation (EDA) software used for designing and simulating electronic circuits. This file might be used for:
    • Detailed circuit design and simulation
    • Netlist generation and verification
    • PCB layout and manufacturing
    • Production and testing purposes

The main differences between the two files are:

  • Level of detail: P3768A04_Concepts_schematics.pdf appears to have more components and details, while P3768A04_OrCAD_schematics_base_version.pdf is more simplified.
  • Design tool: P3768A04_OrCAD_schematics_base_version.pdf is likely generated from OrCAD, while P3768A04_Concepts_schematics.pdf might be created using a different design tool or manually.
  • Purpose: P3768A04_Concepts_schematics.pdf is likely used for high-level design and planning, while P3768A04_OrCAD_schematics_base_version.pdf is used for detailed circuit design, simulation, and production.

In summary, the two files serve different purposes and are used at different stages of the design process. The P3768A04_Concepts_schematics.pdf file provides a more comprehensive view of the design, including no-stuff parts, while the P3768A04_OrCAD_schematics_base_version.pdf file is a more simplified version, focused on the actual circuit design and production.

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

4

NVIDIA provides design files for both Concept and OrCAD schematic capture that customers can use to start their custom carrier board designs.

The OrCAD files do not have any stuffing options (nothing labeled as NO_STUFF in the PDF, hence “base version”), so the BOM in P3768_A04_BOM.xls needs to be applied on top of the OrCAD design files.

The Concept PDF directly shows the stuffing options NVIDIA uses on the Dev Kit carrier board, which also matches P3768_A04_BOM.xls.

5

Hi Chris:

Thanks for the explanation.

We have an Orin NX unit (please see attached pictures). It does not match the DevKit schematics (please see attached section of the schematics). For example, the schematics show that J25, the HDMI connector, is not installed, but our unit has an HDMI port, and its id is J5. Hm!? What is the explanation to that?

Mark

DisplaySchematics
DisplaySchematics1743×863 380 KB

OrinnNx_back
OrinnNx_back1920×1440 438 KB

OrinNx_front
OrinNx_front1920×1440 484 KB

OrinNX_top
OrinNX_top1920×1440 582 KB

6

That appears to be a customized board. The J17 and J14 headers in the top left of your photo do not match P3768_A04_PCB_assembly_drawing.pdf. The NVIDIA reference design’s J14 has a 1x12 pin header compared to your board’s 2 pins and the ref design’s J17 has 1x4 pin header for the CAN BUS compared to your board’s 2x5 pin header. On the schematic page you included, note the “PCB CO-LAYOUT” text beneath the DisplayPort connector, meaning the DP and HDMI connectors are co-located. Whoever created your board deviated from the reference and decided on the HDMI option rather than DP.

7

Hi Chris,

Thanks for the explanation.

When I saw that our Devkit did not match the Devkit Reference design schematics, I was concerned thinking that I am not working with latest schematics. What I failed to realize is that the supplier of Devkit chose to use its own version of carrier board.

Mark