commit 563312c8cabd3f135c58df639634e741e241d638
author Timothy Trippel <ttrippel@google.com> Wed Feb 02 15:10:28 2022 -0800
committer Timothy Trippel <5633066+timothytrippel@users.noreply.github.com> Tue Feb 08 22:57:58 2022 -0800
tree d6b8181e0661f199de5c2f53bae7f6a230cf664e
parent 76f35f4bc2d6304aed1112fc3a3734bf135ac083

[sw/ottf] Rename test_rom_ext to ottf_start

Previously the boot sequence for chip level tests looked like:

chip reset --> test_rom --> test_rom_ext --> ottf --> test_main()

In the above sequence the `test_rom_ext` was really just an ASM file
that performed initializations prior to jumping to the OTTF `main()`.
However, as we refactor the OTTF to enable running chip-level tests at
various boot stages (e.g., ROM_EXT and BL0, see #10498), it makes more
sense to model the combined OTTF and test bundle as its own boot stage
that can be run in inplace of the ROM_EXT or BL0.

Therefore, this commit renames/consolidates the test_rom_ext into a
component of the OTTF, called the `ottf_start`. The `ottf_start` is kept
as a separate static library from the `ottf` to enable running tests
that do not use the OTTF, i.e. the crt_test (which tests the
functionality of the `ottf_start` library), and the "Hello World"
example programs. However, when test images are built, both the
`ottf_start` and `ottf` are linked with the test library itself, to
create one cohesive "test boot stage".

The new boot sequence for a test will look like:

chip reset --> test_rom --> ottf --> test_main(),

where OTTF = (ottf_start --> OTTF).

This partially addresses a task in #10498.

Signed-off-by: Timothy Trippel <ttrippel@google.com>