Skip to content

Conversation

@ArchUsr64
Copy link
Contributor

The PR documents the meta-ti and U-Boot patches that will not make it to 11.1 release but are required for falcon mode to work properly. Among some other minor fixes and additions :)

The entry node defines the entry point for a binary blob in a fitImage.
Even though the value is not relevant to the device-tree, ommiting it
causes a non-fatal error log in debug u-boot build as follows:

Can't get 'entry' property from FIT

Therefore, this patch adds the entry node which also makes the fitImage
generated using this its file consistent with one's generated during the
yocto build process.

Signed-off-by: Anshul Dalal <[email protected]>
A few patches required for falcon mode to work have not been tagged for
the 11.01 release. Therefore link to them in the docs so users can apply
them manually.

Signed-off-by: Anshul Dalal <[email protected]>
@github-actions
Copy link

New warnings found with rstcheck:

source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst:159: (WARNING/2) Explicit markup ends without a blank line; unexpected unindent.

Copy link
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.

vale workflow seems unhappy.
Checkout https://github.com/TexasInstruments/processor-sdk-doc/pull/359/files for the etrors and warnings reported

@ArchUsr64
Copy link
Contributor Author

ArchUsr64 commented Jul 11, 2025

vale workflow seems unhappy. Checkout https://github.com/TexasInstruments/processor-sdk-doc/pull/359/files for the etrors and warnings reported

The error is due to vale detecting the ========== of section headers as git markers and the other few errors from the release notes that are not relevant.

@ArchUsr64 ArchUsr64 requested a review from cshilwant July 11, 2025 09:03
Falcon mode is the U-Boot feature and not specific to our yocto distro.
Therefore document the usage of the feature for non-yocto users who
would have to run the commands implemented by `ti-falcon` override
manually.

Signed-off-by: Anshul Dalal <[email protected]>
Copy link
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.

After that I think it's good to go

@StaticRocket
Copy link
Member

vale workflow seems unhappy. Checkout https://github.com/TexasInstruments/processor-sdk-doc/pull/359/files for the etrors and warnings reported

The error is due to vale detecting the ========== of section headers as git markers and the other few errors from the release notes that are not relevant.

#368 will address that for now. Seems like some of the Red Hat rules are more tuned for asciidoc that I initially thought.

The memory map for the R5 SPL is modified in falcon mode to accommodate
the larger payload size of the fitImage. So, document the same.

Signed-off-by: Anshul Dalal <[email protected]>
The release notes for AM62AX were missing any mention of the falcon mode
feature, add it to make it consistent with other falcon supported
platforms.

Signed-off-by: Anshul Dalal <[email protected]>
@ArchUsr64 ArchUsr64 force-pushed the falcon_fixes branch 3 times, most recently from 4ba735e to 0316678 Compare July 13, 2025 03:15
Use file markup tag instead of double backticks for consistency with
rest of the docs alongside making the language more clear in some
sections.

Signed-off-by: Anshul Dalal <[email protected]>
@StaticRocket StaticRocket merged commit 60bfdc3 into TexasInstruments:master Jul 14, 2025
4 of 6 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.

9 participants