Seeįor details about the structure of a 699-level part number for modules.įor more information about the various Jetson modules and developer kits, see the The P-numbers for NVIDIA ® Jetson™ modules and developer kits are derived from their 699-level part numbers (PNs). Jetson AGX Xavier Industrial (P2888-0008) Jetson AGX Xavier Developer Kit (P2972-0000) includes P2888-0001 module Jetson Xavier NX Developer Kit (P3518-0000) includes P3668-0000 module Jetson AGX Orin Developer Kit (P3730) includes 3701-0000 module The NVIDIA Jetson Linux Developer Guide covers use of Jetson Linux with any of the module and reference carrier board combinations described in this table. This page has links to “Getting Started” guides and user guides for each Jetson module’s developer kit.Īdditional resources and important facts about Jetson Linux are on the Page contains links to several documents that are useful to developers who are new to artificial intelligence (AI) programming or to Jetson products. Use the Product dropdown to restrict your search to documents for a specific Jetson device. To find a document, enter any string of consecutive words from the document’s title in the Search box. Many of these documents and others are available through the Jetson Download Center. Several important ones are listed in the topic Related Documentation. NVIDIA publishes many other documents that address specific aspects of Jetson software and hardware. This developer guide is your primary resource for information about software development for Jetson modules. This developer guide contains the information you need to optimize your use of the complete Jetson product feature set.ĭocumentation for Jetson Modules and Developer Kits ¶ You can customize Jetson Linux software to fit the needs of your project. To flash your Jetson module with the bootloader and file system only, excluding other JetPack components.įor information about moving a completed application from a Jetson developer kit to a production Jetson module on your production carrier board, see the appropriate topic “Jetson Module Adaptation and Bring-Up” topic for your Jetson module. To install Jetson Linux and other JetPack components on your Jetson developer kit. It includes Jetson Linux together with accelerated software libraries, APIs, sample applications, developer tools, and documentation. JetPack SDK is a comprehensive resource for building AI applications. I'll be working in the Mac version of SourceTree, but the interfaces are similar enough that you should be able to follow along without any issues.Software for Jetson Modules and Developer Kits ¶ Don't worry, though, as we go through the series, we'll come back to SourceTree to help visualize what's going on in Git. Since we're justing getting started with Git, a lot of this might not make sense to you. If I click the "Log/History" tab at the bottom, I'll see a visual representation of the repo history. When I select that list item, SourceTree shows information about the repo with buttons that I can use to perform actions like Commit, Checkout, Push and Pull. When I do that, you'll see it in the list. Now, I'll click "File => Open", navigate to a git repo, and click "Select Folder", then click "OK". When asked to load an SSH key, click "No".When we create accounts on BitBucket and GitHub, we'll come back and add them at that time. I'm not going to add any accounts at this time. (This is a good practice, and will help keep your git repositories clean.) Click "Yes" when asked about a global ignore file.Allow SourceTree to "Configure automatic line ending handling".Choose whether or not you want to "Help improve SourceTree".When asked if you'd like to allow SourceTree to make changes to your computer, click "Yes".Then, as we progress in the series, we'll come back to SourceTree to see what our commands have done. So, in this video we'll install SourceTree which will do just that. However, when you're just getting started, it can be useful to use a GUI (or Graphical User Interface) to visualize what's happening each time you enter a command. And once you understand what happens when you type each Git command, chances are you'll be just as happy to do the same. If you ask the average Git user, what program they use to interface with Git, chances are pretty high that they'll say "the command line".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |