Other Parts Discussed in Thread: AM62P, AM67
Hello,
I have some questions about the AM67A boot process and the boot media associated. This assumes that there is eMMC and NOR Flash (via OSPI) available. The goal is to achieve sub-2 second boot times:
- Does the tispl/tisbl require being in the boot partition of the eMMC? For reference, some non-TI MPUs allow for their SPL to exist in Userspace (UDA), which works in a customer's favor for cheaper eMMC with smaller boot partitions that can't fit TI's SPL. The goal is for the path to be all within the eMMC: tiboot3 (boot partition) -> tispl/tisbl (UDA) -> rootfs (UDA)
- Can a tiboot3 file in NOR Flash reference a tispl/tisbl in eMMC UDA? This is optimal for the customer, with no need to use FASTXSPI, as well as avoiding pitfalls with differences in eMMC boot partitions that vary from eMMC to eMMC. This pathing would be tiboot3 (NOR) -> tispl/tisbl (eMMC UDA) -> rootfs (eMMC UDA)
An additional question about using FASTXSPI on AM67A: AM62P has a section in its documentation covering pre-flashing FASTXSPI parameters to avoid PHY tuning on every bootup. The customer has discovered this tuning incurs a ~300ms penalty that is highly problematic. Is there a similar solution for AM67, where flashing binary at a specific address will write these parameters to avoid PHY tuning?
Best,
Ryan
