| Age | Commit message (Collapse) | Author | Files | Lines |
|
Addressed the following warning messages when building the FVP
machine configuration
1. WARNING: fvp-config.inc has a lack of whitespace around the
assignment
2. WARNING: Duplicate inclusion for mctp.inc in pldm.inc
Testing:
Before fix:
Warning messages were displayed when executing the "bitbake
obmc-phosphor-image" command.
After fix:
Warning messages are no longer displayed.
Change-Id: Ib63e4357a3abe0f383d6aa8c580286824f01bed8
Signed-off-by: Mohammed Javith Akthar M <mohammedjavitham@ami.com>
|
|
Enable virtio-net as an alternative NIC in FVP. FVP uses smsc_91c111
for NIC and its support is deprecated in uboot[1]. So, an
alternative NIC configuration is required for network access in uboot.
Testing:
Configured a TAP interface named 'tap1' for out-of-band access.
Sample setup on Ubuntu (requires sudo):
sudo apt update
sudo apt install qemu-kvm libvirt-daemon-system iproute2 bridge-utils
sudo ip tuntap add dev tap1 mode tap user $(whoami)
sudo ifconfig tap1 0.0.0.0 promisc up
sudo brctl addif virbr0 tap1
Execute 'ip a' command in BMC shell and observe the NIC configuration.
Before:
eth0 -> smsc_91c111
After:
eth0 -> virtio-net
eth1 -> smsc_91c111
References:
1. https://patchwork.ozlabs.org/project/uboot/patch/20220802113424.2988464-10-trini@konsulko.com
Change-Id: I445aecb6aefdb422a14fe131a64fc3de3b6865f9
Signed-off-by: Mohammed Javith Akthar M <mohammedjavitham@ami.com>
|
|
Change-Id: I1d53510329749ff122c8a65157a72c8ff88bd306
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
For some of the most commonly set bmcweb options, change them into
packageconfig entries.
Systems that used these config options have been moved to the
PACKAGECONFIG. Some systems that had CMAKE build options still had
those directly removed.
Change-Id: I741f60a725905d67f7a8ef698f95b25895088db4
Signed-off-by: Ed Tanous <etanous@nvidia.com>
|
|
Latest bitbake gives a QA warning for "lack of whitespace around the
assignment". Clean these up.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I7ec3f2a0471a99611071db0aefc2ec6b1323e3ca
|
|
Move evb-ast2500.conf and evb-ast2600.conf into meta-evb.
Change-Id: I64bd938eb63dfe77ffe74e1de25f177291fe65c2
Signed-off-by: Vince Chang <vince_chang@aspeedtech.com>
|
|
Enable IPMI SBMR commands to capture the boot progress code
and update on Redfish BootProgress property and Redfish
PostCodes log service.
Change-Id: I8e3b5eb777f69c8932fb088db09d3088635a4a9e
Signed-off-by: John Chung <john.chung@arm.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I6291eeaf0ca7d4bd674bf0717f1234bfd757f6fe
|
|
Currently I'm more active in the project than Joel, so make sure we have
someone looking at patches.
Change-Id: I86cd7eba2a95c7ecd4052a2da48ce4551a8e8c97
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
|
|
This commit enables host serial console access in base fvp (BMC).
In BMC, UART3(ttyAMA3) is mapped for SOL access.
Testing:
1. Verified using RD-V3-R1 FVP + Base FVP (running OpenBMC firmware)
2. Connect host console with BMC via socat command
> socat -x tcp:localhost:5005 tcp:localhost:5067
3. Update the host state as running in BMC in debug console
> busctl set-property xyz.openbmc_project.State.Host
/xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host
CurrentHostState s
xyz.openbmc_project.State.Host.HostState.Running
4. Log-in to BMC webui via https://127.0.0.1:4223
5. Accesss SOL console from Overview page
Change-Id: I5d797b2b6f57a16d5b53f32c8aa422d102b55c56
Signed-off-by: Mohammed Javith Akthar M <mohammedjavitham@ami.com>
|
|
* Add IPMI Serial interface and usage
* Update Neoverse FVP reference documents
Signed-off-by: John Chung <john.chung@arm.com>
Change-Id: I4abc56bb0ee1eb8f9cdb97743e04494230b911ce
|
|
Enable IPMI Serial interface support in meta-evb-arm that
allows to communicate with Arm Host FVP.
Signed-off-by: John Chung <john.chung@arm.com>
Change-Id: If991767caf57e7f2e7b13e21c66cd940908acf0f
|
|
FVPs are running independently, there can be an issue
with timeout. Increase mctp message timeout to avoid
issue.
Change-Id: I5ec074381c1d5c43c9e36f95852032a3c924fbe3
Signed-off-by: John Chung <john.chung@arm.com>
|
|
Enable redfish-dump-log feature in BMCWeb to enable FaultLog.
Change-Id: I9037f7fb371d7b6e65a8ef03ed8be6a1dc69c164
Signed-off-by: John Chung <john.chung@arm.com>
|
|
The openEmbedded is updated to use the MCTP D-Bus APIs V2.0 from Code
Construct. Update the MCTP API caller.
Change-Id: Ia990d2a1d3b772668d5ebfa38415785945da752b
Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com>
|
|
Update the meta-evb-arm recipe to support styhead and fix
the build break caused by poky upgrade.
Change-Id: I7457a9fb1083126270a93fe0553291f0c435c7db
Signed-off-by: John Chung <john.chung@arm.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I2665e9e7e37242d546eafdb4d1c65dd0369ca635
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8f74fcbb7bf66bb24fde1571ef09fac1095c7e59
|
|
The latest yocto release(styhead,5.1) has made a significant change[1]
to the use of the WORKDIR parameter.
This is not the complete change required but gets us going in the right
direction.
[1]: https://docs.yoctoproject.org/next/migration-guides/migration-5.1.html#workdir-changes
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4f184b361be69e7704a0657a4a00cdad981aff8a
|
|
- update the diagram to visually align with ARM SBMR
- update the SCP fw reference
Change-Id: I6f1fe2472085721f9f5a97f81b9e358e726fc22a
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
|
|
create mctp-local.service to
- configure serial parameters for /dev/ttyAMA1
- create the link with 'mctp' command
- configure local and remote EID for the link
- setup the endpoint with mctpd
Tested: pldm commands work and response is received from the MCP
Change-Id: If924376c4775229c1701924e154894e4eaefa362
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
|
|
This layer contains a reference implementation of OpenBMC for
Armv-A Base RevC AEM FVP.
Tested:
- Build success
- booted to bmc kernel shell
Change-Id: Ie1b100a78232fb986377e3b58d637b97bbf64f42
Signed-off-by: Lean Sheng Tan <sheng.tan@9elements.com>
|
|
Upstream poky made a commit that adds an `/etc/motd` with a strong
warning that meta-poky is not intended to be used for production
purposes. There isn't anything we use directly from meta-poky anymore,
so clean up all references to it.
See poky commit a226865c8683398b5f58628ba2ec5aee1ee6c19d for additional
context.
We could potentially switch from using the `poky` subtree to picking
up OECore directly, but right now it also provides us a qualified set of
OECore + bitbake.
Tested: Built yosemite4 and confirmed `motd` output is absent when
SSHing in.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9c08650d2278b3ba26794c009adad3e593767f58
|
|
Currently, openbmc upstream already update tfa to version v2.10.0
For compatibling with latest openbmc, we need to fix the version at v2.9.0. Otherwise, we will meet this kind of build error from upstream.
ERROR: No recipes in default available for:
openbmc/meta-nuvoton/dynamic-layers/arm-layer/recipes-bsp/
trusted-firmware-a/trusted-firmware-a_2.9.%.bbappend
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: If652ee5478cc9c42e833dd4d2a203d7d5ebddca1
|
|
There is build warning as below:
WARNING: No bb files in default matched BBFILE_PATTERN_evb-npcm845
Due to there is no any bb files in meta-evb-npcm845 layer now.
Add this BBFILE_PATTERN_IGNORE_EMPTY to allow those layers has
no bb files then clear this kind of WARNING messages.
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Ic266ce77e9dff1e068f0c3813f0a0717b2a99c1e
|
|
Make clean meta-evb layer back to description of OpenBMC EVB layer.
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Ia56fc7abfb46615c2150dd4e5acdff801e64a590
|
|
Adopt meta-evb-npcm845 from meta-evb layer that make
more clearer about the scope of evb layer's description.
Tested:
/openbmc$ . setup evb-npcm845
Common targets are:
obmc-phosphor-image
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Ib922057b5bce54b864f1c0ced1b132ea1e71fd91
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
|
|
The webui-vue package is now enabled by default. Clean up all the meta
layers to clean up the explicit enablement.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4895be56c70d2c8666dd96cec18d2c097f0c05a3
|
|
There are temperature, adc, and fan sensors on EVB board, enable them.
Change-Id: I533d4128e44ba8225356e80dcb74faa2fdaf07fb
Signed-off-by: Brian Ma <chma0@nuvoton.com>
|
|
Enable BIOS POST CODE functionality for Nuvoton BMC in postd.
Need to add this configuration and fix daemon load failed.
Due to default SNOOP_DEVICE is using Aspeed BMC.
Failed log:
lpcsnoop.service: Main process exited, code=exited
ExecStart=/usr/bin/snoopd -b 1 -d /dev/aspeed-lpc-snoop0 (code=exited)
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I3ec1c98787260e7a98f4a5135db0b9c5e23fc4af
|
|
Add len manager config for evb npcm845.
Change-Id: I35429f01724fba4882ac2f60c11ba0cc732c743b
Signed-off-by: Brian Ma <chma0@nuvoton.com>
|
|
Remote nuvoton-ipmi-oem from packagegroup due to the package is not exist
in Openbmc.
Change-Id: I90cd286f87cd485d1b406108736910e1766ef9a6
Signed-off-by: Brian Ma <chma0@nuvoton.com>
|
|
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: If575e370e4ee930a46e85bd9cdebd0b0c80bf35c
|
|
Similar to 0823bd2e6b84 ("meta-evb: fix build warning for this layer"),
but for the aspeed part of the layer too.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I4b223af17f7770fb784a5bf5a2d2ce9b2f2074d3
|
|
There are some build warning message as below:
WARNING: No bb files in default matched BBFILE_PATTERN_evb ''
WARNING: No bb files in default matched BBFILE_PATTERN_evb-nuvoton ''
Due to there is no any bb files in meta-evb and meta-evb-nuvoton layer.
Add this BBFILE_PATTERN_IGNORE_EMPTY to allow those layers has
no bb files then clear this kind of WARNING messages.
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Ie845a2001b4e903975ab646ebe72aabd4f73e700
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8e54833ac78e540e9dd5011533d53ff9a3af6763
|
|
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I1a0355aa09cecca7dbcbcbeed8ad5b17d6a40b9f
|
|
Create meta-evb-npcm845 layer under meta-evb-nuvoton then make "setup" script
looks for machine config files being present to know that the meta-layer
contains a valid machine for OpenBMC.
Also add symlinks for the machine config files from meta-nuvoton into
meta-evb-nuvoton so that setup recognizes them as valid machines, but
using the phosphor layers.
Tested:
/openbmc$ . setup evb-npcm845
Machine evb-npcm845 found in meta-evb/meta-evb-nuvoton/meta-evb-npcm845
Common targets are:
obmc-phosphor-image
Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I21de23ded94244bed52c571a8e68b38cf498fc54
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I65febeeec11e6e5b40ee728f42cfbe77023dae1e
|
|
We also need to move the conf-notes.txt files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic44e015c0216b526de4fec277ad42f162bca1f33
|
|
The latest poky commit is requiring us to have all of
our template configs in a subdirectory instead of directly in
the `conf` directory. Without this we end up with errors during
setup like:
```
Error: TEMPLATECONF value (which is .../openbmc/meta-facebook/meta-bletchley/conf) must point to meta-some-layer/conf/templates/template-name
```
Fix this by moving all of our template files into the 'default'
template subdirectory (following the pattern of poky) and modifying
`setup` as necessary to follow.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iecefde73d55acbb6bc63ae3d68c4311adaf327ae
|
|
phosphor-defaults.inc now automatically inherits extrausers and
configures the default root/0penBmc account, so individual platforms no
longer need to specify either explicitly.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ic2b725f0eaadfafef67069449497e57438fa0fba
|
|
WARNING: Layer evb should set LAYERSERIES_COMPAT_evb in its
conf/layer.conf file to list the core layer names it is compatible
with.
WARNING: Layer evb-aspeed should set LAYERSERIES_COMPAT_evb-aspeed in
its conf/layer.conf file to list the core layer names it is compatible
with.
WARNING: Layer evb-ast2500 should set LAYERSERIES_COMPAT_evb-ast2500 in
its conf/layer.conf file to list the core layer names it is compatible
with.
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: I1835b6ed28e4e2d77aadbe6f328001a3ce6e68ce
|
|
The only recipes which use content from meta-perl are openpower
machines:
```
meta-openpower/recipes-bsp/pdata/pdata_git.bb: libxml-libxml-perl-native \
meta-yadro/meta-nicole/recipes-phosphor/logging/openpower-esel-parser_git.bb: libxml-libxml-perl-native \
```
Remove meta-perl from the bblayers of every layer except openpower
machines.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I51f1a8fbfbe879295c64d2339fc115dbd8823681
|
|
No systems use content from meta-webserver (nginx, apache, etc.), so
remove the clutter from our bblayers.conf.samples.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I89ab5ac8c19cd8aa486a2f42d24dcf68688e2408
|
|
Now that the obmc-phosphor-image contains the Web UI, make it clear that
there are other options when building. In particular, the minimal and
'full' command line builds are useful for testing on an EVB or in Qemu.
Change-Id: Ie9df5f1bf0391c5dc34e147ca8bb4a051e333862
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
There's no current owner, and I have an interest in keeping the aspeed
evb platforms working so they can be used for testing.
Change-Id: Ic0af2f944b3822b81ac971968ab1f11fb591cf98
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
Avoids this warning:
WARNING: Layer evb-ast2500 should set LAYERSERIES_COMPAT_evb-ast2500 in
its conf/layer.conf file to list the core layer names it is compatible
with.
Change-Id: If580b22ff01eec259cd7fd1f0ead90a4b2327418
Signed-off-by: Joel Stanley <joel@jms.id.au>
|