Skip to content

U-Boot: refactor general info for the AM62Lx boot flow#204

Merged
praneethbajjuri merged 3 commits intoTexasInstruments:masterfrom
bryanbrattlof:am62lx-uboot
Mar 19, 2025
Merged

U-Boot: refactor general info for the AM62Lx boot flow#204
praneethbajjuri merged 3 commits intoTexasInstruments:masterfrom
bryanbrattlof:am62lx-uboot

Conversation

@bryanbrattlof
Copy link
Copy Markdown
Collaborator

Quite a lot has changed for the AM62Lx boot flow when compared to more traditional AM62 devices. After hiding un-necessary sections document via ASCII charts the bootflow between the SMS and A53 cores along with the memory layout of the 2 SRAM spaces during the boot sequence

Unfortunately this will create a lot of warnings about undefined references to optee. Other than creating an entirely new U-Boot file for 62L I don't think we can get rid of them now. One idea is to add optee back in with a simple landing page saying something along the lines of raise NotImplementedError() or something

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah a plugin was trying to be helpful :/ I fixed it now.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. I'm don't think I see the issue you're seeing. I'm assuming your talking about the boot flow diagrams which I had a little trouble myself so I just disabled the bootflow section on line 1324 if we're rendering for the AM62L and made a complete new section below that section.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cshilwant , Bryan's indentation is fine, it is 3 space indentation everywhere. The only place it is 4 space indentation is for Image formats tables and that is because everyone else in that section is also using 4 space indentation. This PR should be merged as is and then someone can go fix the indentation for that section IMO

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bryanbrattlof bryanbrattlof force-pushed the am62lx-uboot branch 2 times, most recently from 816dfdd to 5a75128 Compare March 6, 2025 22:16
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmenti
Copy link
Copy Markdown
Collaborator

jmenti commented Mar 11, 2025

@bryanbrattlof why are we explaining the bootflow under both "Image Formats" and under "Boot Flow"? Just leave the section under "Image Formats with no description and give a full description of the boorflow under the bootflow section, pretty please (:

@bryanbrattlof
Copy link
Copy Markdown
Collaborator Author

no worries. I've removed the paragraphs

@cshilwant cshilwant dismissed their stale review March 13, 2025 06:23

several updates after the last review

@cshilwant cshilwant dismissed StaticRocket’s stale review March 13, 2025 06:23

several updates after the last review

@cshilwant cshilwant requested review from a team, jeevantelukula and sadik-smd March 13, 2025 06:24
StaticRocket
StaticRocket previously approved these changes Mar 13, 2025
Copy link
Copy Markdown
Member

@StaticRocket StaticRocket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Close enough for now. There's still some indentation issues but I know this file is about to be reworked.

@cshilwant
Copy link
Copy Markdown
Member

Looks like 57f78ae was an accidental merge commit?

@StaticRocket
Copy link
Copy Markdown
Member

Well this was correct until @praneethbajjuri modified it. @bryanbrattlof you'll have to rebase and push now.

Copy link
Copy Markdown
Member

@cshilwant cshilwant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to fix - #204 (comment)

@praneethbajjuri
Copy link
Copy Markdown
Collaborator

Well this was correct until @praneethbajjuri modified it. @bryanbrattlof you'll have to rebase and push now.

Yes, my bad .. the rebase messed it up. @bryanbrattlof will send a update in a day removing the merge delta.

@bryanbrattlof bryanbrattlof requested a review from cshilwant March 18, 2025 17:57
@cshilwant cshilwant dismissed their stale review March 18, 2025 19:34

Author has updated the PR

Copy link
Copy Markdown
Collaborator

@jmenti jmenti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see no major issues but I did nitpick a few details @bryanbrattlof

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cshilwant , Bryan's indentation is fine, it is 3 space indentation everywhere. The only place it is 4 space indentation is for Image formats tables and that is because everyone else in that section is also using 4 space indentation. This PR should be merged as is and then someone can go fix the indentation for that section IMO

There are some weird whitespace inconsistencies. Fix them

Signed-off-by: Bryan Brattlof <bb@ti.com>
Quite a lot has changed for the AM62Lx boot flow when compared to more
traditional AM62 devices. After hiding un-necessary sections document
via ASCII charts the bootflow between the SMS and A53 cores along with
the memory layout of the 2 SRAM spaces during the boot sequence

Signed-off-by: Bryan Brattlof <bb@ti.com>
ARM's Trusted firmware Boot Loader (BL) stage 1, 2 and 3 provides a
reference software design for the different phases a CPU can be during
boot. To make things a little more uniform, standardize on using BL-1
for AP Trusted ROM code or BL-31 for EL3 Runtime Firmware

Signed-off-by: Bryan Brattlof <bb@ti.com>
@TexasInstruments TexasInstruments deleted a comment from jonaswood01 Mar 19, 2025
@praneethbajjuri praneethbajjuri merged commit 7feedc2 into TexasInstruments:master Mar 19, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants