Intel-BMC on github
Wim Vervoorn
wvervoorn at eltan.com
Fri Mar 22 02:52:21 AEDT 2019
Hello James,
Good to see the Intel BMC code is on github so we can give it a try and use it.
In the mean time we downloaded and built the image without problem.
The issue is that we don't have a Wolfpass board. In order to get around this I create a woldpass-bmc devices in the OpenBMC qemu.
As far as I now the major difference is in the flash size(I added a 64 MB part), I also updated the strapping according to the schematic.
I can use this device in Qemu and it starts the image I built for the s2600wf (if I catenate two of them to achieve the 64MB).
The issue is that if I try the wolfpass image u-boot is starting, it also reports the kernel is loaded etc but it freezes after is passes control to the kernel.
I included the qemu logging below:
U-Boot 2016.07 (Mar 21 2019 - 14:30:46 +0000)
SOC : AST2500-A1
RST : 0x01
PLL : 25 MHz
CPU : 825 MHz
MEM : 2.333 MHz, EEC: Disable, Cache: Disable
VGA : 16 MiB
DRAM : init by SOC
Watchdog enabled
DRAM: 112 MiB
Flash: 64 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: MAC0 : RMII/NCSI
MAC1 : RGMII
FTGMAC100#0
Error: FTGMAC100#0 address not set.
, FTGMAC100#1
Error: FTGMAC100#1 address not set.
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20080000 ...
Using 'conf at aspeed-bmc-intel-purley.dtb' configuration
Trying 'kernel at 1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x20080110
Data Size: 2670096 Bytes = 2.5 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80001000
Entry Point: 0x80001000
Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 20080000 ...
Using 'conf at aspeed-bmc-intel-purley.dtb' configuration
Trying 'ramdisk at 1' ramdisk subimage
Description: obmc-phosphor-initramfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x2031897c
Data Size: 21827584 Bytes = 20.8 MiB
Architecture: ARM
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 20080000 ...
Using 'conf at aspeed-bmc-intel-purley.dtb' configuration
Trying 'fdt at aspeed-bmc-intel-purley.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x2030bfe8
Data Size: 51480 Bytes = 50.3 KiB
Architecture: ARM
Verifying Hash Integrity ... OK
Booting using the fdt blob at 0x2030bfe8
Loading Kernel Image ... OK
Loading Ramdisk to 856c0000, end 86b91000 ... OK
Loading Device Tree to 856b0000, end 856bf917 ... OK
## Transferring control to Linux (at address 80001000)...
Starting kernel ...
## youhou 2...
## Transferring control to Linux (at address 80001000)...
Message: 4
Date: Tue, 19 Mar 2019 19:34:02 +0000
From: "Mihm, James" <james.mihm at intel.com>
To: "openbmc at lists.ozlabs.org" <openbmc at lists.ozlabs.org>
Subject: Intel-BMC on github
Message-ID:
<C599FC839619124CAC44E062ABB7DFE2D7A61D0F at ORSMSX115.amr.corp.intel.com>
Content-Type: text/plain; charset="us-ascii"
Intel announces that its internal repository based on the OpenBMC project is being made public on github under the organization name of Intel-BMC.
Intel is sharing the latest internal repositories in response to requests from partners and customers to be able to build an OpenBMC firmware image that will run on an existing Intel server platform. The repositories include content that has not yet been upstreamed to the LF OpenBMC project.
Currently the only supported platform is the Wolf Pass platform (S2600WF). Support for more platforms will be added in the future.
The Intel-BMC can be found at https://github.com/Intel-BMC<https://github.com/Intel-BMC/openbmc>.
For further information, please refer to the readme file (https://github.com/Intel-BMC/openbmc/blob/intel/README.md).
James Mihm
Intel DCG BMC Core Firmware
(503) 264-5129
More information about the openbmc
mailing list