• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 132 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6442: Question on TI U‑Boot AM64x Image Naming Constraints (tiboot3.bin / tispl.bin / u‑boot.img)

Kien
Expert 4546 points

Part Number: AM6442

Hi Champs,

My customer is working with TI U‑Boot on the AM64x platform and would like to clarify the flexibility around boot image naming.

From their current understanding and experimentation, the boot images appear to require the following fixed filenames:

  • Tiboot3.bin
  • Tispl.bin
  • u-boot.img

Could you please confirm whether these image names are strictly required by the ROM boot flow / SPL handoff on AM64x, or if it is possible to customize or rename them through configuration (for example via U‑Boot build options, environment settings, or bootloader code changes)?

Additionally, if the naming is fixed:

  • Which boot stages (ROM, SPL, etc.) explicitly depend on these filenames?
  • Is this behavior consistent across all boot modes (OSPI, eMMC, SD)?

Any references to documentation or code locations that define this requirement would be greatly appreciated.


Regards,

Kien

  • 0
    TI__Guru* 78690 points

    Hi Kien,

    1/. For file system based memory boot media (i.e. SD card, eMMC UDA etc...)
    - tiboot3.bin filename is fixed for onchip ROM to load the first stage BL from
    - tispl.bin/u-boot.img filename are the "default" file names used by SPL to load the next stage SW, but they might be changed by user in SPL code/configurations as necessary.

    2/. For raw offset based memory boot media (OSPI-NAND/OSPI-NOR, GPMC-NAND, eMMC boot partition...)
    tiboot3.bin/tispl.bin/u-boot.img file name is irrelevant, and only the offsets are used instead by ROM/SPL

    3/. For peripheral boot media (UART, USB-DFU...)
    tiboot3.bin/tispl.bin/u-boot.img file name are purely used by host to send them to target over UART/USB-DFU link.

    Best,
    -Hong