Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 679df8aee342c26ef7f7e9e96ddf3cfed94cf526
commit679df8aee342c26ef7f7e9e96ddf3cfed94cf526[log] [tgz]
authorPotin Lai <potin.lai@quantatw.com>Thu Dec 08 14:50:04 2022 +0800
committerPatrick Williams <patrick@stwcx.xyz>Fri Feb 10 16:12:18 2023 +0000
tree19905091a9abb38be995ef763fdca412fb10990a
parent864cc43bcd478cb31e4ab607e596ba9baf46cd3e [diff]
meta-bletchley: add 99-platform-init

Add 99-platform-init to archive following items
1. Disable FMC_WDT2
AST2600 use FMC_WDT2 to archive ABR feature.
Disable FMC_WDT2 before systemd start.

2. Detect boot flash source
Write boot source into /run/media/slot
0: boot from primary
1: boot from alternate

Tested result:
- In u-boot, FMC_WDT2 is enabled and timer is counting down
```
U-Boot 2019.04 (Nov 10 2022 - 00:12:58 +0000)

SOC: AST2620-A3
RST: WDT1 SOC
PCI RST: #2
RST: External
FMC 2nd Boot (ABR): Enable, Dual flashes, Source: Primary
Set FMC_WDT2 timer reload value to 0x0BB8
eSPI Mode: SIO:Enable : SuperIO-2e
Eth: MAC0: RMII/NCSI, MAC1: RMII/NCSI, MAC2: RGMII, MAC3: RMII/NCSI
Model: Facebook Bletchley BMC
DRAM:  already initialized, 2 GiB (capacity:2048 MiB, VGA:0 MiB, ECC:off)
MMC:
Loading Environment from SPI Flash... SF: Detected w25q01jv with page size 256 Bytes, erase size 4 KiB, total 128 MiB
*** Warning - bad CRC, using default environment

In:    serial@1e784000
Out:   serial@1e784000
Err:   serial@1e784000
Model: Facebook Bletchley BMC
Net:   Could not get PHY for eth2: addr 0
Failed to initialize PHY: -19
eth-1: ftgmac@1e670000
Hit any key to stop autoboot:  0
ast# md.l 0x1e620064 2
1e620064: 00000001 0b560bb8                      ......V.
```

- After BMC boot into Linux OS, FMC_WDT2 is disabled
```
bletchley login: root
Password:
root@bletchley:~# devmem 0x1e620064
0x00000000
root@bletchley:~# devmem 0x1e620068
0x0BB80BB8
```

- check boot source (primary)
```
root@bletchley:~# cat /run/media/slot
0
```

Signed-off-by: Potin Lai <potin.lai@quantatw.com>
Change-Id: If5e41dd9745ba5c4ec45637772136e847954c56e
2 files changed
tree: 19905091a9abb38be995ef763fdca412fb10990a
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-arm/
  5. meta-aspeed/
  6. meta-asrock/
  7. meta-bytedance/
  8. meta-delta/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-ibm/
  15. meta-ingrasys/
  16. meta-inspur/
  17. meta-intel-openbmc/
  18. meta-inventec/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-qualcomm/
  24. meta-quanta/
  25. meta-raspberrypi/
  26. meta-security/
  27. meta-supermicro/
  28. meta-tyan/
  29. meta-wistron/
  30. meta-yadro/
  31. poky/
  32. .templateconf ⇨ poky/.templateconf
  33. bitbake ⇨ poky/bitbake/
  34. LICENSE ⇨ poky/LICENSE
  35. meta ⇨ poky/meta
  36. meta-poky ⇨ poky/meta-poky/
  37. meta-skeleton ⇨ poky/meta-skeleton
  38. oe-init-build-env ⇨ poky/oe-init-build-env
  39. scripts ⇨ poky/scripts/
  40. .eslintrc.json
  41. .gitignore
  42. .gitreview
  43. openbmc-env
  44. OWNERS
  45. README.md
  46. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.

Setting up your OpenBMC project

1) Prerequisite

See the Yocto documentation for the latest requirements

Ubuntu

sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \
    hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
cd openbmc

3) Target your hardware

Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

bletchley               mori                    s8036
dl360poc                mtjade                  swift
e3c246d4i               mtmitchell              tatlin-archive-x86
ethanolx                nicole                  tiogapass
evb-ast2500             olympus-nuvoton         transformers
evb-ast2600             on5263m5                vegman-n110
evb-npcm750             p10bmc                  vegman-rx20
f0b                     palmetto                vegman-sx20
fp5280g2                qcom-dc-scm-v1          witherspoon
g220a                   quanta-q71l             witherspoon-tacoma
gbs                     romed8hm3               x11spi
greatlakes              romulus                 yosemitev2
gsj                     s2600wf                 zaius
kudo                    s6q
lannister               s7106

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.

Features of OpenBMC

Feature List

  • Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
  • Full IPMI 2.0 Compliance with DCMI
  • Code Update Support for multiple BMC/BIOS images
  • Web-based user interface
  • REST interfaces
  • D-Bus based interfaces
  • SSH based SOL
  • Remote KVM
  • Hardware Simulation
  • Automated Testing
  • User management
  • Virtual media

Features In Progress

  • OpenCompute Redfish Compliance
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

  • Roxanne Clarke, IBM
  • Nancy Yuen, Google
  • Patrick Williams, Meta
  • Terry Duncan, Intel
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm

Contact