Curtiss-Wright DuraCOR 312 - Page 52

DuraCOR 312
Appendix C
Page 52 of 59
MNL-0670-01 Rev A2
ECO-5931
Effective: 03 Jun 20
Do your customizations now.
Now we are back to the standard build process.
C312_GetReadyToMake is a first nod toward doing this but for now do those steps by hand.
cd $DEVDIR/sources/kernel/kernel-4.9
make mrproper
make ARCH=arm64 O=$TEGRA_KERNEL_OUT mrproper
cp arch/arm64/configs/defconfig_B $DEVDIR/images/.config # this should
not be needed.
make ARCH=arm64 O=$TEGRA_KERNEL_OUT defconfig_B # this gives error
without it
make ARCH=arm64 O=$TEGRA_KERNEL_OUT menuconfig
Menuconfig will bring up a text-based dialog that will allow you to change kernel settings. Add any project-
specific drivers that you may need.
Now we can build:
C312_MakeWP
Then prepare the image
C312_PrepWPArea
5. Deploy the image that is now in the top level build directory.
Then you can flash the module
5
(See “How to deploy an image to C312” for detailed hardware setup)
 Connect the USB cable (tx2 micro-USB to dev-ubuntu USB-A
 Connect Ethernet cables on both to the same hub
6
5
The first time we deploy following changes there are a number of image creation and signing steps
done. The first deploy is done like this:
C312_ImageFlash
Subsequent deploys of the same image may now be done the same as the release image deploy:
C312_ImageFlash reuse

6
The Ethernet connection is needed to do the sdk deploy but may not be required for this
method.