Skip to content
Snippets Groups Projects
Commit 9209e5b4 authored by dylan.frei's avatar dylan.frei
Browse files

Updated journal.md

parent 4a85b7f9
Branches
No related tags found
No related merge requests found
......@@ -296,6 +296,12 @@ This software, unlike my previous assumptions, does not need to run on an Ubuntu
# Week 9 : 05.03.2024
## Objectives
- Get back into the project and refresh my memory
- Figure out necessary component changes
- Get deeper into MB1/MB2 configuration, flashing, and their location
After a long break in exploration, my main goal was getting back to the understanding of the boot sequence. One remaining question was about the storage of the boot components which fortunately could be found [here](https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/SO/JetsonOrinSeries.html#bootloader).
Our goal will be to understand the necessary steps in modifying the configuration in lower level bootloaders (MB1, MB2) to work with our custom carrier board. It turns out MB1 and MB2 are both stored in an on-module QSPI flash. All the configuration changes necessary to have the module work with a custom carrier board are detailed [here](https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html#hr-jetsonmoduleadaptationandbringup-jetsonagxorinseries). The wiki specifies that changes need to be made to the following components :
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment