1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
# Copyright 2021 The ChromiumOS Authors
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.
if PLATFORM_EC_FLASH_CROS
config PLATFORM_EC_CONSOLE_CMD_CHARGEN
bool "Console command: chargen"
default y
help
Enables the "chargen" console command, which sends a continuous
stream of characters to the EC console.
This allows to create tests which validate console output by
verifying that no characters in the received sequence were lost.
config PLATFORM_EC_CONSOLE_CMD_FLASH
bool "Console commands: flasherase, flashread, flashwrite"
help
Enables various console commands:
flasherase - erase flash region
flashread - read from flash to memory
flashwrite - write memory to flash
config PLATFORM_EC_CONSOLE_CMD_FLASHINFO
bool "Console commands: flashinfo"
default y
help
Enables various console commands:
flashinfo - displays information about the flash storage
config PLATFORM_EC_CONSOLE_CMD_FLASH_WP
bool "Console commands: flashwp"
default y
help
Enables various console commands:
flashwp - change write-protection settings
config PLATFORM_EC_CONSOLE_CMD_SYSJUMP
bool "Console command: sysjump"
default y
help
Enables the sysjump console command used for testing and verifying
that we're able to jump between images. Normally, in an EC build,
there will exist 2 images (sometimes more): read-only (RO) and
read-write (RW). This console command allows us to manually jump
between the various images (or even to a random starting address) by
copying the image data from flash to ram, then jumping to the image's
entry point.
choice PLATFORM_EC_STORAGE_TYPE
prompt "Code storage type"
default PLATFORM_EC_EXTERNAL_STORAGE if SOC_FAMILY_NPCX
default PLATFORM_EC_EXTERNAL_STORAGE if SOC_FAMILY_MEC
default PLATFORM_EC_INTERNAL_STORAGE if SOC_FAMILY_RISCV_ITE
default PLATFORM_EC_INTERNAL_STORAGE if SOC_FAMILY_STM32
help
Sets the EC code storage type.
config PLATFORM_EC_EXTERNAL_STORAGE
bool "Flash is stored external to the EC"
help
This indicates that the EC's flash is stored separately and is it
not possible execute directly from it. Code must be loaded from
the flash into internal SRAM before it can be executed. It is still
possible to read and write the flash.
config PLATFORM_EC_INTERNAL_STORAGE
bool "Flash is stored internal to the EC"
help
This indicates that the EC code can reside on internal storage.
This option implies XIP(eXecute-In-Place) semantics.
i.e. code is being fetched directly from storage media.
endchoice
config PLATFORM_EC_RW_TOTAL_IMAGE_SIZE
hex
default $(dt_node_int_prop_hex,/binman/ec-rw,size)
help
Total size of the EC RW image, including the 32-byte RW_FWID. The
source of truth for this setting is the binman devicetree node.
# Workaround for not being able to have commas in macro arguments
DT_CHOSEN_CROS_FLASH := cros-ec,flash
config PLATFORM_EC_FLASH_SIZE_BYTES
hex "flash size"
default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_CROS_FLASH))
help
Total size of writable flash.
config PLATFORM_EC_MAPPED_STORAGE
bool "Flash is mapped into the EC's address space"
default y if SOC_FAMILY_NPCX || SOC_FAMILY_RISCV_ITE
help
This indicates that the EC's flash is directly mapped into
its address space. This makes it easier to read and write the flash.
If this is not defined, the flash driver must implement
flash_physical_read().
config PLATFORM_EC_MAPPED_STORAGE_BASE
hex "Mapped storage size"
default $(dt_chosen_reg_addr_hex,$(DT_CHOSEN_CROS_FLASH))
depends on PLATFORM_EC_MAPPED_STORAGE
help
Base address of memory-mapped flash storage, for platforms which
define CONFIG_MAPPED_STORAGE.
config PLATFORM_EC_FLASH_PSTATE
bool "Store persistent write protect for the flash inside"
default y if SOC_FAMILY_RISCV_ITE
help
Store persistent write protect for the flash inside the flash data
itself. This allows ECs with internal flash to emulate something
closer to a SPI flash write protect register. If this is not
defined, write protect state is maintained solely by the physical
flash driver.
if PLATFORM_EC_FLASH_PSTATE
config PLATFORM_EC_FLASH_PSTATE_BANK
bool "Store the pstate data in its own dedicated bank of flash"
default y
help
Store the pstate data in its own dedicated bank of flash. This allows
disabling the protect-RO-at-boot flag without rewriting the RO
firmware, but costs a bank of flash.
If this is not defined, the pstate data is stored inside the RO
firmware image itself. This is more space-efficient, but the only way
to clear the flag once it's set is to rewrite the RO firmware (after
removing the WP screw, of course).
config PLATFORM_EC_FLASH_PSTATE_LOCKED
bool "Lock the pstate by default"
depends on !PLATFORM_EC_FLASH_PSTATE_BANK
help
Lock the pstate by default, Currently only supported when
PLATFORM_EC_FLASH_PSTATE_BANK is not defined.
endif # PLATFORM_EC_FLASH_PSTATE
config PLATFORM_EC_USE_ZEPHYR_FLASH_PAGE_LAYOUT
bool "Use Zephyr flash page layout API to get sector information"
default y if SOC_FAMILY_STM32
select FLASH_PAGE_LAYOUT
help
When enabled, EC will use flash page layout API to get information
about flash sectors (index, offset, and size).
endif # PLATFORM_EC_FLASH_CROS
|
