Skip to content

fix(tools): update snagboot documentation - #776

Open
sadik-smd wants to merge 1 commit into
TexasInstruments:masterfrom
sadik-smd:snag
Open

fix(tools): update snagboot documentation#776
sadik-smd wants to merge 1 commit into
TexasInstruments:masterfrom
sadik-smd:snag

Conversation

@sadik-smd

Copy link
Copy Markdown
Contributor

update snagboot documentaion with latest additions
to the installer and github repo for yaml-configs

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

New warnings found with rstcheck:

source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst:87: (INFO/1) Duplicate implicit target name: "using the sdk installer (recommended)".
source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst:252: (ERROR/3) Inconsistent title style: skip from level 2 to 4.

@sadik-smd
sadik-smd force-pushed the snag branch 2 times, most recently from 4fcf4ef to f7ed529 Compare August 4, 2026 10:41
update snagboot documentaion with latest additions
to the installer and github repo for yaml-configs
update accpet.txt with snagboot vocabulary.

Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
Comment on lines +37 to +39
[Ss]nagfactory
[Ss]nagrecover
[Ss]nagflash

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.

The other entries are fine as they are project names. These ones though are command names which I'm a little more hesitant to treat as proper words, especially since most command names are compound words that omit punctuation or use unusual spelling for ease of use.

If you use inline code or the command role in the documentation, vale will properly ignore it's use. Additionally, it will make it clear to the reader when you are talking about a command or something else.

I don't really know how much to enforce this here though since the upstream Snagboot docs are so lax about their spelling.

Before using a YAML file, replace the two path placeholders with actual paths
to your binaries:

* ``<path_to_snagboot_binaries>/`` — recovery boot loader images built with

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.

the specified configuration.

The following table outline the board names for snagfactory yaml configuration.
The following table outlines the board names for snagfactory YAML configuration.

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.

For future reference: The yaml examples listed below can be tagged with yaml for language aware linting and syntax highlighting: https://pygments.org/docs/lexers/


The script installs Snagboot by using pip, sets up udev rules so USB access works
without root, and verifies the installation. If pip installs the tools to
``~/.local/bin`` but that directory is not on ``PATH``, add the following to ``~/.bashrc``:

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.

Suggested change
``~/.local/bin`` but that directory is not on ``PATH``, add the following to ``~/.bashrc``:
:file:`~/.local/bin` but that directory is not on ``PATH``, add the following to :file:`~/.bashrc`:

Pip has a built in warning about this. Not sure how old it is. If it's present for our supported Ubuntu host version then this should be safe to omit I think. Well, unless that setup script eats the message.

PVRTune
Sitara
Slint
SPL

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.

Acronyms should not be considered valid words

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.

7 participants