= Developing Custom Flashing Standard Firmware = == SDKManager ==SDKManager is available only on Linux, and can be installed here: <code>https://developer.nvidia.com/sdk-manager</code># Start up the SDKManager# Put the Jetson into recovery mode. For the AGX, this can be done by pressing the recovery button while powering on the device. For the Jetson Orin Nano ==and NX, however, a jumper will be required. # Connect the Target Jetson to the host device and ensure that the target device is recognized.= Flashing = # Follow the instructions on the application, choosing configurations as necessary.

Notes:== Customizing Kernel ==- Current Design constraints: - Based off of # Within <code>source</code>, enter the <code>kernel</code> eventually navigate to the availability of parts in JLCPCB. Possibility of parts not being found or existing. <code>kernel-  jammy- Flashing is done with the flash.sh script through the following command $ sudo .src</flash.sh code> folder and run <boardcode> make menuconfig ARCH=arm64<rootdev/code> where board is the actual board (Jetson-Nano-XX, etc.)rootdev determines what type of device is being flahed. Use mmcblk0pc1 to flash This will bring up a local storage device (eMMC or SD card)- TO begin flashing, put the device into force recovery mode UI with configurable drivers and then press resetperipherals. - Run the flash script using the previous command specifiedSelect desired configurations and save. Flash using a convenient script: - To avoid having to specify the rootdev and the board # The configurations, can use the custom flashing script: -  Using GPIO Pins to program protocol:- you can use the rasberry pi libraries to interface with the pins, configuring them to whatever layout that is neededbe found within a <code>. - Example: it is possible to direclty interface with config</code> file located within the i2c system in the nano by using the linux terminal itselfsame directory.  Current Game Plan:- mess around with Copy the programming of contents and locate the GPIO pins: Figure out if there are ways to choose access teh data that the GPIO pins are Or Receiving<code>defconfig</code> file in <code>.Test if it is possible to reconfigure the pins on the jetson on the firmware side Build Time: - On a single Nvidia Nano/arch/arm64/configs/</code>, overwriting it takes about 45 mins - 1 hour to complete with the buildcopied contents. The build is encrypted through RSA. The source is still accessible and every time changes are made to the source files and want ot be reflected, the build files have to be remade. Current goal (Figure out if there's a way to make specific build files to decrease development time). 

Notes:== Flashing the Kernel ==- General requirements Ensure that the target Jetson is connected to the host device and is in recovery mode. Navigate to build the <code>Linux kernel still apply: efor Tegra</code> directory and run <code>sudo ./nvsdkmanager_flash.gsh</code>. `build-essentials`When prompted, `bc`disconnect the Jetson from host device and allow it to boot. Congratulations, `libssl-dev`, etc- Need to install `libssl-dev (depends on whether the certain packages are included when running the script)you have successfully flashed your Jetson with custom firmware.