config.yaml

#
# HSS Payload Generator - sample configuration file
#

# First, we can optionally set a name for our image, otherwise one will be created dynamically
set-name: 'PolarFire-SoC-HSS::TestImage'

#
# Next, we'll define the entry point addresses for each hart, as follows:
#
hart-entry-points: {u54_1: '0x80200000', u54_2: '0x80200000', u54_3: '0xB0000000', u54_4: '0x80200000'}

#
# Optionally define the seg register values. If undefined, the values set in Libero will be used.
#
seg-reg-config: {seg0_0: '0x7FC0', seg0_1: '0x7000', seg1_2: '0x7FB0', seg1_3: '0x0', seg1_4: '0x7FA0', seg1_5: '0x0', }

#
# Finally, we'll define some payloads (source ELF files) that will be placed at certain regions in memory
# The payload section is defined with the keyword payloads, and then a number of individual
# payload descriptors.
#
# Each payload has a name (path to its ELF file), an owner-hart, and optionally 1-3 secondary-harts.
#
# Additionally, it has a privilege mode in which it will start execution.
#  * Valid privilege modes are PRV_M, PRV_S and PRV_U.
#
#
# In the following example:
#  * test/baremetal.elf is assumed to be a bare metal application that runs in u54_3, 
#    and expects to start in PRV_M
#  * test/u-boot is the Das U-Boot bootloader, and it runs on U54_1, U54_2 and U54_4. 
#    It expects to start in PRV_S.
#
# Case only matters for the ELF path names, not the keywords.
#
payloads:
  test/baremetal.elf: {exec-addr: '0xB0000000', owner-hart: u54_3, priv-mode: prv_m, skip-opensbi: true}
  test/u-boot:    {exec-addr: '0x80200000', owner-hart: u54_1, secondary-hart: u54_2, secondary-hart: u54_4, priv-mode: prv_s}