doc: ti: Clarify required file names for K3 platforms

Now that we are using binman in all cases on these platforms, reword
things to be clearer that for filesystem booting we need to use a
specific name for each component.

Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
This commit is contained in:
Tom Rini 2023-07-25 12:44:16 -04:00 committed by Heinrich Schuchardt
parent 54edc37a22
commit f687c8f7b4
4 changed files with 9 additions and 4 deletions

View file

@ -169,7 +169,8 @@ Build procedure:
Target Images
--------------
Copy the below images to an SD card and boot:
In order to boot we need tiboot3.bin, tispl.bin and u-boot.img. Each SoC
variant (GP, HS-FS, HS-SE) requires a different source for these files.
- GP

View file

@ -170,7 +170,8 @@ Build procedure:
Target Images
--------------
Copy the below images to an SD card and boot:
In order to boot we need tiboot3.bin, sysfw.itb, tispl.bin and u-boot.img.
Each SoC variant (GP and HS) requires a different source for these files.
- GP

View file

@ -172,7 +172,8 @@ Build procedure:
Target Images
--------------
Copy the below images to an SD card and boot:
In order to boot we need tiboot3.bin, tispl.bin and u-boot.img. Each SoC
variant (GP, HS-FS, HS-SE) requires a different source for these files.
- GP

View file

@ -183,7 +183,9 @@ Build procedure:
Target Images
--------------
Copy the below images to an SD card and boot:
In order to boot we need tiboot3.bin, sysfw.itb, tispl.bin and u-boot.img.
Each SoC variant (GP, HS-FS and HS-SE) requires a different source for these
files.
- GP