Skip to content

fix(security): correct AM62L removing R5 SPL reference#690

Merged
jeevantelukula merged 1 commit intoTexasInstruments:masterfrom
shiva-ti:auth_boot_upd
Apr 24, 2026
Merged

fix(security): correct AM62L removing R5 SPL reference#690
jeevantelukula merged 1 commit intoTexasInstruments:masterfrom
shiva-ti:auth_boot_upd

Conversation

@shiva-ti
Copy link
Copy Markdown
Collaborator

Correct existing diagram showing R5 SPL for AM62L as well. Add reference to fTPM based secure storage guide.

Correct existing diagram showing R5 SPL for AM62L as well.
Add reference to fTPM based secure storage guide.

Signed-off-by: Shiva Tripathi <s-tripathi1@ti.com>
@StaticRocket
Copy link
Copy Markdown
Member

Kind of a general comment: Do we want to mask this stuff with the AM62L platform or define a new configuration parameter to describe bootflows that do not use R5. I assume this will include other platforms in the future.

@shiva-ti
Copy link
Copy Markdown
Collaborator Author

Kind of a general comment: Do we want to mask this stuff with the AM62L platform or define a new configuration parameter to describe bootflows that do not use R5. I assume this will include other platforms in the future.

Yes we could use a "R5-SPL" config to differentiate. But I see AM62L being used across the doc at present for this distinction, specifically in bootflow the information is very platform specific, might have to add more branches of R5-SPL going ahead to completely skip using platforms. So kept it as is for now

Copy link
Copy Markdown
Contributor

@Pratham-T Pratham-T left a comment

Choose a reason for hiding this comment

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

LGTM.

@jeevantelukula jeevantelukula merged commit a0a74d0 into TexasInstruments:master Apr 24, 2026
6 checks passed
@shiva-ti shiva-ti deleted the auth_boot_upd branch April 24, 2026 06:22
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.

10 participants