c8e9da2615
The actual manifest is 1024 bytes, but we previously had padding bytes due to the implementation of SECTION_FUNC(). The manifest is not executable code so SECTION_VAR() is appropriate and produces a section of the appropriate size. Fixes: #82822 Signed-off-by: Shawn Nematbakhsh <shawn@rivosinc.com>
29 lines
834 B
ArmAsm
29 lines
834 B
ArmAsm
/*
|
|
* Copyright (c) 2023 Rivos Inc.
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <zephyr/toolchain.h>
|
|
|
|
/* exports */
|
|
GTEXT(__rom_header)
|
|
|
|
/* OpenTitan manifest consists of 1024 bytes (256 words) of manifest
|
|
* containing signature, device ID, version info, etc. The test ROM
|
|
* ignores all of these fields except for entry point.
|
|
*
|
|
* The layout below conforms to manifest version: 0x71c3 (major),
|
|
* 0x6c47 (minor). The manifest format is documented here:
|
|
* https://github.com/lowRISC/opentitan/blob/689a163294e1791bd30cfe096decf7f9233abad4/sw/host/opentitanlib/src/image/manifest.rs#L205
|
|
*/
|
|
SECTION_VAR(rom_header, __rom_header)
|
|
.rept(225)
|
|
.word 0
|
|
.endr
|
|
/* Entry point is relative to the beginning of manifest. */
|
|
.word(__start - __rom_header)
|
|
/* Extensions entry table goes here. */
|
|
.rept(30)
|
|
.word 0
|
|
.endr
|