summaryrefslogtreecommitdiffstats
path: root/Documentation/soc/intel/icelake/iceLake_coreboot_development.md
blob: 5f8e279841bd066c6fcebf243a1532abea8b9a9c (plain)
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
# Intel Ice Lake coreboot development

## Introduction

This document captures the coreboot development strategy for Intel SoC named Ice lake.

The Ice Lake processor family is the next generation Intel® Core processor family.
These processors are built using Intel's 10 nm+ process.

* [What is Ice Lake?](https://www.intel.in/content/www/in/en/design/products-and-solutions/processors-and-chipsets/ice-lake/overview.html)

## Development Strategy

Like any other Intel SoC, Ice Lake coreboot development is also based on "Intel common code development model".

1. Intel develops initial Firmware code for Ice Lake SoC.

2. Additionally provides Firmware code support for Intel Reference Platform (RVP), known as Ice lake RVP with same SoC.
   ```eval_rst
   :doc:`../../../mainboard/intel/icelake_rvp`
   ```

3. OEMs to design based on reference platform and make use of mainboard sample code. Dragonegg is Ice Lake based mainboard developed by Google
   ```eval_rst
   :doc:`../../../mainboard/google/dragonegg`
   ```

### Summary:
* SoC is Ice Lake.
* Reference platform is icelake_rvp.
* OEM board is Dragonegg.

## Create coreboot Image

1. Clone latest coreboot code as below
   ```bash
   $ git clone https://review.coreboot.org/coreboot.git
   ```

2. Place blobs (ucode, me.bin and FSP packages) in appropriate locations

   Note:
   Consider the fact that ucode and ME kit for Ice Lake SoC will be available from Intel VIP site.
   After product launch, FSP binary will be available externally as any other program.

3. Create coreboot .config

4. Build toolchain
   ```bash
   CPUS=$(nproc--ignore=1)  make  crossgcc-i386  iasl
   ```

5. Build image
   ```bash
   $ make # the image is generated as build/coreboot.rom
   ```

## Flashing coreboot

Flashing mechanism might be different between Intel RVP (Reference Validation Platform) and Chromebooks:

* Make use of dediprog while flashing coreboot image on Intel-RVP
* For Chromebook related platform like dragonegg, one can flash via servo:

```bash
   $ dut-control spi2_vref:pp3300 spi2_buf_en:on spi2_buf_on_flex_en:on warm_reset:on
   $ sudo flashrom -n -p ft2232_spi:type=servo-v2 -w <bios_image>
   $ dut-control spi2_vref:off spi2_buf_en:off spi2_buf_on_flex_en:off warm_reset:off
```
### References
* [flashrom](https://flashrom.org/Flashrom)
* [Servo](https://www.chromium.org/chromium-os/servo)