From 9209e5b409c9eb4ffeabd660122e66e4b37cb0fb Mon Sep 17 00:00:00 2001 From: "dylan.frei" <dylan.frei@etu.hesge.ch> Date: Tue, 5 Mar 2024 23:25:59 +0100 Subject: [PATCH] Updated journal.md --- journal.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/journal.md b/journal.md index 2425443..0a7c77e 100644 --- a/journal.md +++ b/journal.md @@ -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 : -- GitLab