Provide an example setup for generating distributing and applying updates.
Description of directories:
Resource directory: All local source archive materials needed to set up, build, and deploy are stored in
one directory kept under git version control for easy customization.
Archive Directory: For local storage of NVidia and other 3rd party upstream Sources.
Build directory: This is an area to generate work product and should be able to be erased after you build
and save. (Currently, work product is not collected outside the build area. You may want to archive the
complete build directory before generating a new one if you may want to deploy it again later.)
WorkProd Directory: This is the future
collection point for the versioned output. (Status: Currently, there
are no scripts or software to support work product yet.)
Instructions for setting up a project directory
Description of source files
c-w_c312_resource.tar.xz
description: archive containing the project resource kit
obtain from Curtiss Wright support team.
create: This is a git repo. You can make your own local branches to
customize this as needed.
nv_jetpack.sqsh
description: squashfs containing nv project area and base image
obtain: from Curtiss Wright support team.
create: follow instructions in Appendix D.... to make a custom version.
SFT-0778-01.tar
description: This is an archived set of release images.
You only need this if you are reflashing the original image. Some post
production work is done on the units after flashing, so this is not
recommended. We are using this in the example of flashing an existing
What you get today is a bit of framework, a few patches, (early) build scripts and instructions that
should get you rolling.
To Next Page
Loading...