2
2
3
3
## Key changes
4
4
5
- 1 . Added RAM initialization
6
- 2 . Added SCOM registers support
5
+ 1 . Added SCOM registers support
6
+ 2 . Added RAM initialization
7
+ 3 . Added support for reading from VPD partition
7
8
8
9
---
9
10
## Statistics
10
11
11
12
Since bootblock release: \
12
- <span style =" color :yellow " >59</span > files were changed including <span style =" color :lightgreen " >48</span > new files created \
13
+ <span style =" color :yellow " >59</span > files were changed including
14
+ <span style =" color :lightgreen " >48</span > new files created \
13
15
<span style =" color :lightgreen " >12407</span > lines of code were added \
14
16
<span style =" color :orangered " >76</span > lines of code were removed
15
17
@@ -117,7 +119,7 @@ In order to build coreboot image, follow the steps below:
117
119
* In the ** ROM chip size** option select ` 512 KB `
118
120
* Save the configuration and exit.
119
121
120
- ![ make menuconfig] ( images/cb_menuconfig .png )
122
+ ![ make menuconfig] ( images/cb_menuconfig_romstage .png )
121
123
122
124
5 . Start the build process of coreboot inside the container:
123
125
@@ -136,7 +138,6 @@ In order to build coreboot image, follow the steps below:
136
138
```
137
139
scp build/coreboot.rom.signed.ecc root@<BMC_IP>:/tmp
138
140
```
139
- > If that file is not present, use ` coreboot.rom ` instead
140
141
141
142
2 . Backup the HBB partition (for faster later recovery) by invoking this
142
143
command on BMC:
@@ -150,7 +151,6 @@ In order to build coreboot image, follow the steps below:
150
151
```
151
152
pflash -e -P HBB -p /tmp/coreboot.signed.ecc
152
153
```
153
- > Again, if that file is not present, use ` coreboot.rom ` instead
154
154
155
155
Answer yes to the prompt and wait for the process to finish.
156
156
@@ -175,20 +175,22 @@ Configuration with a single IBM POWER9 64bit CPU is supported. \
175
175
Dual CPU setup not supported currenctly.
176
176
177
177
Following RAM configurations were tested and are proved to be properly initialized.
178
- ```
179
- MCS0, MCA0
180
- DIMM0: 1Rx4 16GB PC4-2666V-RC2-12-PA0
181
- DIMM1: not installed
182
- MCS0, MCA1
183
- DIMM0: 1Rx8 8GB
184
- DIMM1: not installed
185
- MCS1, MCA0
186
- DIMM0: 2Rx4 32GB PC4-2666V-RB2-12-MA0
187
- DIMM1: not installed
188
- MCS1, MCA1
189
- DIMM0: 2Rx8 16GB PC4-2666V-RE2-12
190
- DIMM1: not installed
191
- ```
178
+ <pre >
179
+ MCS0, MCA0
180
+ DIMM0: <a href =https://www.samsung.com/semiconductor/dram/module/M393A2K40CB2-CTD >1Rx4 16GB PC4-2666V-RC2-12-PA0</a >
181
+ DIMM1: not installed
182
+ MCS0, MCA1
183
+ DIMM0: <a href =https://www.crucial.com/memory/server-ddr4/mta9asf1g72pz-2g6j1 >1Rx8 8GB PC4-2666V-RD1-12</a >
184
+ DIMM1: not installed
185
+ MCS1, MCA0
186
+ DIMM0: <a href =https://www.samsung.com/semiconductor/dram/module/M393A4K40CB2-CTD/ >2Rx4 32GB PC4-2666V-RB2-12-MA0</a >
187
+ DIMM1: not installed
188
+ MCS1, MCA1
189
+ DIMM0: <a href =https://mis-prod-koce-homepage-cdn-01-blob-ep.azureedge.net/web/static_file/12701730956286135.pdf >2Rx8 16GB PC4-2666V-RE2-12</a >
190
+ DIMM1: not installed
191
+ </pre >
192
+
193
+ All 3 major DRAM vendors are supported, namely Samsung, Micron and Hynix.
192
194
193
195
---
194
196
## Binaries
0 commit comments