2015-03-19 18:58:55 +00:00
|
|
|
/*
|
2016-02-01 11:04:46 +00:00
|
|
|
* Copyright (c) 2015-2016, ARM Limited and Contributors. All rights reserved.
|
2015-03-19 18:58:55 +00:00
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions are met:
|
|
|
|
*
|
|
|
|
* Redistributions of source code must retain the above copyright notice, this
|
|
|
|
* list of conditions and the following disclaimer.
|
|
|
|
*
|
|
|
|
* Redistributions in binary form must reproduce the above copyright notice,
|
|
|
|
* this list of conditions and the following disclaimer in the documentation
|
|
|
|
* and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* Neither the name of ARM nor the names of its contributors may be used
|
|
|
|
* to endorse or promote products derived from this software without specific
|
|
|
|
* prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
|
|
|
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
|
|
|
|
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
|
|
|
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
|
|
|
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
|
|
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
|
|
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
|
|
* POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
#ifndef __COMMON_DEF_H__
|
|
|
|
#define __COMMON_DEF_H__
|
|
|
|
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
2015-10-09 18:06:13 +01:00
|
|
|
#include <bl_common.h>
|
|
|
|
#include <platform_def.h>
|
|
|
|
|
2015-03-19 18:58:55 +00:00
|
|
|
/******************************************************************************
|
|
|
|
* Required platform porting definitions that are expected to be common to
|
|
|
|
* all platforms
|
|
|
|
*****************************************************************************/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Platform binary types for linking
|
|
|
|
*/
|
2016-06-28 16:58:26 +01:00
|
|
|
#ifdef AARCH32
|
|
|
|
#define PLATFORM_LINKER_FORMAT "elf32-littlearm"
|
|
|
|
#define PLATFORM_LINKER_ARCH arm
|
|
|
|
#else
|
2015-03-19 18:58:55 +00:00
|
|
|
#define PLATFORM_LINKER_FORMAT "elf64-littleaarch64"
|
|
|
|
#define PLATFORM_LINKER_ARCH aarch64
|
2016-06-28 16:58:26 +01:00
|
|
|
#endif /* AARCH32 */
|
2015-03-19 18:58:55 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Generic platform constants
|
|
|
|
*/
|
|
|
|
#define FIRMWARE_WELCOME_STR "Booting Trusted Firmware\n"
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Some of the platform porting definitions use the 'ull' suffix in order to
|
|
|
|
* avoid subtle integer overflow errors due to implicit integer type promotion
|
|
|
|
* when working with 32-bit values.
|
|
|
|
*
|
2015-12-14 09:35:25 +00:00
|
|
|
* The TSP linker script includes some of these definitions to define the BL32
|
2015-03-19 18:58:55 +00:00
|
|
|
* memory map, but the GNU LD does not support the 'ull' suffix, causing the
|
|
|
|
* build process to fail. To solve this problem, the auxiliary macro MAKE_ULL(x)
|
|
|
|
* will add the 'ull' suffix only when the macro __LINKER__ is not defined
|
|
|
|
* (__LINKER__ is defined in the command line to preprocess the linker script).
|
|
|
|
* Constants in the linker script will not have the 'ull' suffix, but this is
|
|
|
|
* not a problem since the linker evaluates all constant expressions to 64 bit
|
|
|
|
* (assuming the target architecture is 64 bit).
|
|
|
|
*/
|
|
|
|
#ifndef __LINKER__
|
|
|
|
#define MAKE_ULL(x) x##ull
|
|
|
|
#else
|
|
|
|
#define MAKE_ULL(x) x
|
|
|
|
#endif
|
|
|
|
|
2016-09-12 16:10:33 +01:00
|
|
|
#if LOAD_IMAGE_V2
|
|
|
|
#define BL2_IMAGE_DESC { \
|
|
|
|
.image_id = BL2_IMAGE_ID, \
|
|
|
|
SET_STATIC_PARAM_HEAD(image_info, PARAM_EP, \
|
|
|
|
VERSION_2, image_info_t, 0), \
|
|
|
|
.image_info.image_base = BL2_BASE, \
|
|
|
|
.image_info.image_max_size = BL2_LIMIT - BL2_BASE,\
|
|
|
|
SET_STATIC_PARAM_HEAD(ep_info, PARAM_EP, \
|
|
|
|
VERSION_2, entry_point_info_t, SECURE | EXECUTABLE),\
|
|
|
|
.ep_info.pc = BL2_BASE, \
|
|
|
|
}
|
|
|
|
#else /* LOAD_IMAGE_V2 */
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
2015-10-09 18:06:13 +01:00
|
|
|
#define BL2_IMAGE_DESC { \
|
|
|
|
.image_id = BL2_IMAGE_ID, \
|
2016-02-01 11:04:46 +00:00
|
|
|
SET_STATIC_PARAM_HEAD(image_info, PARAM_EP, \
|
|
|
|
VERSION_1, image_info_t, 0), \
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
2015-10-09 18:06:13 +01:00
|
|
|
.image_info.image_base = BL2_BASE, \
|
2016-02-01 11:04:46 +00:00
|
|
|
SET_STATIC_PARAM_HEAD(ep_info, PARAM_EP, \
|
|
|
|
VERSION_1, entry_point_info_t, SECURE | EXECUTABLE),\
|
|
|
|
.ep_info.pc = BL2_BASE, \
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
2015-10-09 18:06:13 +01:00
|
|
|
}
|
2016-09-12 16:10:33 +01:00
|
|
|
#endif /* LOAD_IMAGE_V2 */
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
2015-10-09 18:06:13 +01:00
|
|
|
|
2016-07-08 14:38:16 +01:00
|
|
|
/*
|
|
|
|
* The following constants identify the extents of the code & read-only data
|
|
|
|
* regions. These addresses are used by the MMU setup code and therefore they
|
|
|
|
* must be page-aligned.
|
|
|
|
*
|
|
|
|
* When the code and read-only data are mapped as a single atomic section
|
|
|
|
* (i.e. when SEPARATE_CODE_AND_RODATA=0) then we treat the whole section as
|
|
|
|
* code by specifying the read-only data section as empty.
|
|
|
|
*
|
|
|
|
* BL1 is different than the other images in the sense that its read-write data
|
|
|
|
* originally lives in Trusted ROM and needs to be relocated in Trusted SRAM at
|
|
|
|
* run-time. Therefore, the read-write data in ROM can be mapped with the same
|
|
|
|
* memory attributes as the read-only data region. For this reason, BL1 uses
|
|
|
|
* different macros.
|
|
|
|
*
|
|
|
|
* Note that BL1_ROM_END is not necessarily aligned on a page boundary as it
|
|
|
|
* just points to the end of BL1's actual content in Trusted ROM. Therefore it
|
|
|
|
* needs to be rounded up to the next page size in order to map the whole last
|
|
|
|
* page of it with the right memory attributes.
|
|
|
|
*/
|
|
|
|
#if SEPARATE_CODE_AND_RODATA
|
|
|
|
#define BL_CODE_BASE (unsigned long)(&__TEXT_START__)
|
|
|
|
#define BL_CODE_LIMIT (unsigned long)(&__TEXT_END__)
|
|
|
|
#define BL_RO_DATA_BASE (unsigned long)(&__RODATA_START__)
|
|
|
|
#define BL_RO_DATA_LIMIT (unsigned long)(&__RODATA_END__)
|
|
|
|
|
|
|
|
#define BL1_CODE_LIMIT BL_CODE_LIMIT
|
|
|
|
#define BL1_RO_DATA_BASE (unsigned long)(&__RODATA_START__)
|
|
|
|
#define BL1_RO_DATA_LIMIT round_up(BL1_ROM_END, PAGE_SIZE)
|
|
|
|
#else
|
|
|
|
#define BL_CODE_BASE (unsigned long)(&__RO_START__)
|
|
|
|
#define BL_CODE_LIMIT (unsigned long)(&__RO_END__)
|
|
|
|
#define BL_RO_DATA_BASE 0
|
|
|
|
#define BL_RO_DATA_LIMIT 0
|
2015-03-19 18:58:55 +00:00
|
|
|
|
2016-07-08 14:38:16 +01:00
|
|
|
#define BL1_CODE_LIMIT round_up(BL1_ROM_END, PAGE_SIZE)
|
|
|
|
#define BL1_RO_DATA_BASE 0
|
|
|
|
#define BL1_RO_DATA_LIMIT 0
|
|
|
|
#endif /* SEPARATE_CODE_AND_RODATA */
|
|
|
|
|
|
|
|
#endif /* __COMMON_DEF_H__ */
|