SUSE Hack Week: port coreboot to 96Boards HiKey

Hikey is a development board with HiSilicon Kirin 620 eight-core ARM Cortex-A53 64-bit SoC. The original firmware is based on Tianocore EDK II, and I'd like to port coreboot to this board.

Challenges:

Learn about ARMv8 ISA, ARM TrustZone and ARM Trusted firmware
Find out the key initialization code in the UEFI firmware
Find the way to use the non-free blobs

Goal:

Flash the firmware to the board and use of the serial console to debug
Boot coreboot firmware
Try to boot an operating system

Join this project Leave this project

Looking for hackers with the skills:

coreboot uefi arm arm64

This project is part of:

Hack Week 14

Activity

almost 8 years ago: tonghuix liked this project.

over 8 years ago: mbrugger liked this project.

over 8 years ago: vimacs started this project.

over 8 years ago: vimacs added keyword "uefi" to this project.

over 8 years ago: vimacs added keyword "arm" to this project.

over 8 years ago: vimacs added keyword "arm64" to this project.

over 8 years ago: vimacs added keyword "coreboot" to this project.

over 8 years ago: a_faerber liked this project.

over 8 years ago: vimacs originated this project.

Comments

over 8 years ago by algraf | Reply

There are no non-free blobs on the HiKey IIRC. You can build ATF, EDK2, U-boot, etc all from source code.
- over 8 years ago by vimacs | Reply
  
  I've found these blobs: - Watch Dog Driver - Flash Driver - SnpPV600 - MCU
  - over 8 years ago by a_faerber | Reply
    
    Surely upstream U-Boot does not contain such blobs. Is there a reason you specifically want coreboot?
    
    over 8 years ago by vimacs | Reply
    
    I just saw that u-boot supports this board, but it still needs the mcuimage.bin blob. The u-boot code base may be easier to understand than edk2, and the job can be easier.
    
    I think what coreboot can do better than other firmware projects is that it can use many customized payloads, a mature and simplified code base, features like cbmem for debugging and logging, etc.
    
    Edit Comment 1764
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    I just saw that u-boot supports this board, but it still needs the mcuimage.bin blob. The u-boot code base may be easier to understand than edk2, and the job can be easier. I think what coreboot can do better than other firmware projects is that it can use many customized payloads, a mature and simplified code base, features like cbmem for debugging and logging, etc.
    
    Reply to vimacs
    
    I just saw that u-boot supports this board, but it still needs the mcuimage.bin blob. The u-boot code base may be easier to understand than edk2, and the job can be easier.
    
    I think what coreboot can do better than other firmware projects is that it can use many customized payloads, a mature and simplified code base, features like cbmem for debugging and logging, etc.
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview