fix(rpi3): expose BL1_RW to BL2 map for mboot

BL2 requires the ability to access the TCG Event Log during
Measured Boot. Currently the Platform hangs since the Event Log
is not exposed to BL2's mmap. Define a RPI3_BL1_RW region to be
added to the BL2 Image, if Measured Boot is enabled.

Change-Id: Ic236a80e73ea342b4590cfb65bafbb8ffac17085
Signed-off-by: Abhi Singh <abhi.singh@arm.com>
This commit is contained in:
Abhi Singh 2024-11-07 17:41:58 -06:00 committed by Abhi Singh
parent 4f9894db35
commit 9acaaded3c
2 changed files with 11 additions and 0 deletions

View file

@ -75,6 +75,9 @@ static const mmap_region_t plat_rpi3_mmap[] = {
#endif #endif
MAP_DEVICE0, MAP_DEVICE0,
MAP_FIP, MAP_FIP,
#if MEASURED_BOOT
RPI3_MAP_BL1_RW,
#endif
MAP_NS_DRAM0, MAP_NS_DRAM0,
#ifdef BL32_BASE #ifdef BL32_BASE
MAP_BL32_MEM, MAP_BL32_MEM,

View file

@ -171,6 +171,14 @@
#define BL1_RW_BASE (BL1_RW_LIMIT - PLAT_MAX_BL1_RW_SIZE) #define BL1_RW_BASE (BL1_RW_LIMIT - PLAT_MAX_BL1_RW_SIZE)
#define BL1_RW_LIMIT (BL_RAM_BASE + BL_RAM_SIZE) #define BL1_RW_LIMIT (BL_RAM_BASE + BL_RAM_SIZE)
/*
* In order to access the TCG Event Log in BL2, we need to expose the BL1_RW region
* where the log resides.
*/
#define RPI3_MAP_BL1_RW MAP_REGION_FLAT(BL1_RW_BASE, \
BL1_RW_LIMIT - BL1_RW_BASE, \
MT_MEMORY | MT_RW | MT_SECURE)
/* /*
* BL2 specific defines. * BL2 specific defines.
* *