Age | Commit message (Collapse) | Author | Files | Lines |
|
Replace append directive with += in hotswap-power-cycle bb recipe
Signed-off-by: Ashwin Murali <ashwin.murali@fii-na.com>
Change-Id: I64e3f2c2dd96b5f42b089d380c3568d1f0f9d544
|
|
Replace append directive with += in kudo-bmc-update bb recipe
Signed-off-by: Ashwin Murali <ashwin.murali@fii-na.com>
Change-Id: I91e02e7c671783a885015610a59e3383a2bf3f60
|
|
Replace append directives with += in kudo-bios-update bb recipe
Signed-off-by: Ashwin Murali <ashwin.murali@fii-na.com>
Change-Id: I9ced6841b6f9d68d3697bb51be5e36186262b0ce
|
|
add comment on sel-logger to match kudo code "enable clear sel method"
Signed-off-by: Grant Williams <grant.williams@fii-na.com>
Change-Id: Iae39238880c5fd9ddf86c40743d8dd6c5be73041
|
|
The following are not used in Kudo and can be removed.
- obmc-bmc-service-quiesce@.target
- ${PN}-chassis-check-power-status
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Iad82935b3b0c621ec6b1c81cd0ed56a6be55baaf
|
|
Update Kudo Version ID to v0.10-00-kudo
Signed-off-by: Karthikeyan Sundaram <karthikeyan.sundaram@fii-na.com>
Change-Id: I86c0e0142b197b1be7acf426fc1f68e7f8482217
|
|
Upstream has removed the image-prelink bbclass[1], so remove it from any
local.conf.sample that still has it enabled.
1. https://git.openembedded.org/openembedded-core/commit/?id=857baaf9e3d181ca18264e85d90b899fd94acff9
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I70f42f8816f5dea207fcf5c34837d6796b3f6bb6
|
|
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
|
|
Add CPU detect to support 1p/2p virtual sensor json configuration
Add new thermal sensors
Add virtual sensor json selection support based on NBM chipset version
Signed-off-by: Mustafa Shehabi <mustafa.shehabi@fii-na.com>
Signed-off-by: Avenash Asai Thambi <avenash.thambi@fii-usa.com>
Change-Id: Ib5a442cc35f2402c521557d908a90a86dd091cc0
|
|
As mentioned by I970e06ca6f9d0a9792af122eb25da1bb9a06f058, append and
remove directives with '+=' are no longer valid Yocto syntax and raise a
warning.
See https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n40
One interesting caveat has to do with the difference between "append"
and "+=".
foo:append = "a"
foo:append = "b"
Results in `foo = "ab"`, but
foo += "a"
foo += "b"
Results in `foo = "a b"`. When `:append +=` is used it has behavior
like the `+=` operator. Therefore, in some cases we need to insert
additional whitespace after the `:append = "` to ensure concatenation
behaves as expected. I've manually reviewed the results to ensure there
is no ill side-effects from an additional space potentially being added.
Fix up the entire tree with the following one-liner (and similar for
`remove`):
git ls-files -- ':!:poky/**' ':!:meta-security/**' \
':!:meta-raspberrypi/**' ':!:meta-openembedded/**' \
| grep "\.bb" | xargs grep -l ":append.*+=" \
| xargs sed -i 's/:append\(.*\)+=\([^"]*\)" */:append\1=\2" /'
or ...
| xargs grep -l ":remove.*+=" \
| xargs sed -i "s/:remove\(.*\)+=/:remove\1=/"
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea6235e7c76e252f4d473652957c2925f6b8845a
|
|
The package, phosphor-hostlogger, is no longer required.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I17bede02ae32c47c5078368899248c734683c6a3
|
|
avenash.thambi (1):
foxconn-ipmi-oem: Add Maintainers and OWNERS into foxconn-ipmi-oem
Change-Id: I93a509b724a9531511dd7fd31d0a7d715e4525a9
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
e.g.
WARNING: Duplicate inclusion for /opt/openbmc/meta-phosphor/conf/distro/openbmc-phosphor.conf in /opt/openbmc/meta-google/conf/distro/gbmc.conf
WARNING: Duplicate inclusion for /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-base.inc in /opt/openbmc/meta-phosphor/conf/distro/openbmc-phosphor.conf
WARNING: Duplicate inclusion for /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-defaults.inc in /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-base.inc
WARNING: Duplicate inclusion for /opt/openbmc/meta/conf/distro/include/security_flags.inc in /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-defaults.inc
WARNING: Duplicate inclusion for /opt/openbmc/meta/conf/distro/include/no-static-libs.inc in /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-base.inc
WARNING: Duplicate inclusion for /opt/openbmc/meta/conf/distro/include/yocto-uninative.inc in /opt/openbmc/meta-phosphor/conf/distro/include/phosphor-base.inc
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I74856075638fe243974ebb4818e80f8e7e2022e6
|
|
The server.ttyS1.conf and server.ttyS3.conf files were missing from
the SRC_URI.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ic2762f8cfdb1a5b6e2965a77890a98afdc1ae31e
|
|
With the usage of new fans there is a delay in the rate of change
of fan pwm from 255 to lower level so the pwm-init.sh is updated to
configure the fan controller settings at boot.
Signed-off-by: avenash.thambi <avenash.thambi@fii-usa.com>
Change-Id: If43dd1de39702128bf61fa6483ea2d210410f67e
|
|
This file is no longer needed since we moved away from
using the intel-ipmi-oem.
Signed-off-by: avenash.thambi <avenash.thambi@fii-usa.com>
Change-Id: Ifadd213d9b26a11d88caeab37b4b5cb079ba0f52
|
|
e.g.
| CMake Error at /opt/openbmc/build/kudo/tmp/work/armv7a-openbmc-linux-gnueabi/fii-ipmi-oem/git-r0/recipe-sysroot-native/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
| Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Change-Id: Ie9667094c782072614ff5dccd61a1cf31ebd5589
Signed-off-by: Peter Foley <pefoley@google.com>
|
|
ERROR: Layer 'kudo-layer' depends on layer 'fii-layer', but this layer is not enabled in your configuration
Signed-off-by: Peter Foley <pefoley@google.com>
Change-Id: I419a42a8e5e8fd3452e5bdc1073aee8dd1699c37
|
|
Per [1], Yocto is going to start requiring both branch names and
`protocol=https` in GitHub SRC_URI variables. Ran the upstream tool to
automatically fix our URIs.
1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
|
|
The obmc-console recipe changes from
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/49336
add support for multiple port configurations. Therefore, the configs
do not need to occur in the bbappend.
Removed the additional configuration steps to configure multiple
ports and used OBMC_CONSOLE_TTYS override instead.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Iba14a8b5935cd3cd8718a8bf94d5eed18de9db9e
|
|
According to
https://github.com/openbmc/docs/blob/master/anti-patterns.md,
/usr/sbin is reserved for system administration executables. The
executables called by services or internal use are placed in
/usr/libexec/<package>.
Executables kept in /usr/sbin,
- kudo.sh
- kudo-ras.sh
- kudo-fw.sh
Executables moved to /usr/libexec,
- ampere-hostctrl/ampere_power_util.sh
- kudo-fw/kudo-fw-ver.sh
- kudo-fw/kudo-lib.sh
- kudo-boot/init_once.sh
- usb-network/usb_network.sh
- obmc-console/kudo_uart_mux_ctrl.sh
- pwm-init/pwm_init.sh
- phosphor-virtual-sensor/tla2024-enable.sh
Also removed /usr/bin/env from service files.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I270eee5cb9c0ca248f1b84a87d1cff5c6dc129f3
|
|
Restart psusensor service to ensure that the VBAT sensor
doesn't say "no reading" until it's second query after
a hotswap.
Signed-off-by: Ashwin Murali <ashwin.murali@fii-na.com>
Change-Id: I6bb8866bff011e4641e5f26b82a0b17e50cc5fc8
|
|
Modify the kudo.sh fw to display BMC version format in decimal
Signed-off-by: Mustafa Shehabi <mustafa.shehabi@fii-na.com>
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: Ifdc18e4b417bd764794750a2f7a28db849c17eca
|
|
1. ampere-host-power-cycle.service will force off host followed
by force on.
2. ampere-host-reset.service will pulse the sysreset pin
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I4736c82f8f462a21650d5abba55c036a05da8e25
|
|
`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required.
As it said by Yocto documentation it can be used by `Hob`
https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that already removed since Yocto-2.1
https://www.yoctoproject.org/tools-resources/projects/hob
Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
|
|
The ampere-host-reset.service and ampere-host-force-reset.service
are not used. Host is reset with ampere-host-power-cycle.service.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ie6c58c5c9d1179d79e5c5be307a37bdb263172ff
|
|
For shutdown, if it does not go through the power utility, the
Chassis state will not change.
For host reset, execute additional verification steps attached
to the power utility service performing the host reboot.
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I2f67a34ba8cfd80fd3dde999baa329d44288bdfe
|
|
The phosphor-pid-control package will be provided through
obmc-fan-mgmt, so it does not need to be provided through
obmc-fan-control as well.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I29ac8363056db866d6181d958d8a86e53605400d
|
|
The new yocto syntax was missing from,
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/46289
Also removed an extra empty line from the recipe.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Id7684b24ecd2a51e7e2a28c10a76b61519ea0872
|
|
Avenash Asai Thambi (1):
Add boot count into motherboard eeprom and clear command
Change-Id: Iedc41527654482c2a45c414ec3c778a451199c93
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Change-Id: I8711fa16a624c9f132310357f973cebd25f9b1d3
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The ampere_power_util.sh file has a syntax error of missing double
quotes in a echo print.
This is a follow up to the gerrit commit
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/48477
Signed-off-by: Mustafa Shehabi <mustafa.shehabi@fii-na.com>
Signed-off-by: avenash.thambi <avenash.thambi@fii-usa.com>
Change-Id: Iff734c390507201c2d539dc6468de09a888623c7
|
|
Adds support for BIOS verification process to execute before
issuing a host reset and boot from AC power.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I31c019a5ea8cb296749f671df15c658a7e2a3b9f
|
|
Adds support for Power On for power button press and Power Off when
holding the power button. This is a temporary and rudimentary method
to handle button presses. The intention is to eventually use
phosphor-buttons with Nuvoton support.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Iede64f89c716102a688880280c11ff7f3068021b
|
|
Kudo uses GPIO for checking the host status and does not use IPMI
SMS. Therefore, this will remove the host-check feature as some of
the recent recipe changes create stalls between host-state-manager
and IPMI host control. Reference changes made in,
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/45312
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I76b246dd003f94c95f194592647c4291014abf0b
|
|
Instead of a host or chassis restart for a Chassis PowerCycle,
have both the BMC and host perform a hard reset. This requires
changes to phosphor-state-manager to add the handling of
xyz.openbmc_project.State.Chassis.Transition.PowerCycle. Currently,
there is handling for On and Off, but not PowerCycle.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I3d934c47a68899b2fd8fcba966f8d92c97554a77
|
|
Summary of changes:
1. Adjust start time of xyz.openbmc_project.State.Chassis.service
to fix initial chassis state
2. Add shutdown ack service
3. Remove reset ack service
4. Remove heartbeat mode
5. Remove sysreset pin control from power_control.exe
6. Remove all phosphor-fan services that caused power off during
a system reset
7. Adjustments to ampere_power_util.sh (See below)
ampere_power_util.sh:
1. Use GPIO instead of dbus for host state
2. Wait 3 seconds before checking power status for power on
3. Wait 6 seconds before checking power status for power off
4. Have force_off act GPIO while power_off sets Chassis state
5. Graceful shutdown acts GPIO
6. Check host status before issuing system reset
7. Set Watchdog Expire Action to None before power off and reset
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ie2720ee60d489c4160165c6827a78a400ae4d30b
|
|
Corrects the nvparm to disable LPI mode NV_SI_CPU_LPI_FREQ_DISABLE
for SCP 1.07 and newer.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I43f4d090fae3ff202834d39c9161802f20e396e1
|
|
The other system components are not using this the MON_BMC_ALIVE
signal, so it no longer requires assertion.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ieedc2650d230dc3eff8c2d76d2f1ce70b68919cb
|
|
The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:
1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.
This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.
Tested:
* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.
```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.
```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```
* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.
Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b
|
|
Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e
|
|
Add log rotation for gpio trigger logging
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: I5e77b92115adc637fd4be48c5307f449519c281c
|
|
1. Based on newer version of Ampere's nvparm spec updated nvparm
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: I47a338fcb483c5c22f3a9799088c54de1a9a5153
|
|
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: I97ee9317df93480f68cd69ee3462f970970ba885
|
|
bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the
choice is functionally arbitrary for image generation but control over
the package format becomes important if we want to:
1. Include runtime package management functionality in the firmware image
2. Mess about with the packages on the build system
With respect to 1 the IPK format and opkg (an ipk package manager) are
designed for embedded systems[1] - by contrast to RPMs have heavier
dependencies and a greater impact on the size and complexity of the
firmware image.
Regarding 2, the embedded nature and the need for opkg to work without
much fuss leads to a lower configuration barrier by comparison to RPMs.
With ipk it becomes possible to reuse the packages built during image
preparation for core analysis without needing to generate an SDK:
```
$ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib
$ MY_DEBUG_ROOT=tmp/rootfs-debug
$ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \
-o $MY_DEBUG_ROOT \
update
$ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \
-f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \
-o $MY_DEBUG_ROOT \
install dbus-sensors dbus-sensors-dbg
$ gdb-multiarch
(gdb) set solib-absolute-prefix .../tmp/rootfs-debug
(gdb) add-auto-load-safe-path .../tmp/rootfs-debug
(gdb) file tmp/rootfs-debug/usr/bin/nvmesensor
(gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000
Core was generated by `/usr/bin/nvmesensor'.
Program terminated with signal SIGABRT, Aborted.
pthread_kill.c:45
45 pthread_kill.c: No such file or directory.
(gdb) bt
pthread_kill.c:45
../sysdeps/posix/raise.c:26
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
/home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6
"xyz.openbmc_project.NVMeSensor", this=0x488f04) at
/usr/include/sdbusplus/bus.hpp:234
../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159
(gdb)
```
This approach documented in the Poky Reference Manual:
https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins
Switch all machines to IPK to align the debugging experience with
upstream's documentation and to facilitate efficient use of packaged
software at runtime.
[1] https://openwrt.org/docs/guide-user/additional-software/opkg
Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
This will select the option within phosphor-sel-logger to clear the
IPMI SEL through its Clear method. Then there will not be a Record
ID sync issue from the clear of SEL and adding new entries.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I4ba21237b2726254b2a427d9bc26469c5267b565
|
|
Upstream bbclasses changed to typically use the `:${PN}` override
syntax, including the SYSTEMD_ variables. Change our systemd.bbclass
to do the same for consistency and perform a tree-wide variable
replacement.
Spot checked by building bletchley and witherspoon and checking
some of the SYSTEMD_LINK directives on installed packages under qemu.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20a9dd809bff8af8759488734f80486c7228c6eb
|
|
The SEL Record IDs are observed to skip in /var/log/ipmi_sel and
the issue has been traced to the rate-limit of rsyslog. When
messages are dropped due to rate-limiting, some of them are SEL
messages. Phosphor-sel-logger is inserting the Record ID into the
message without checking if previous records make it into ipmi_sel.
This causes the skip in Record IDs.
To prevent SEL messages from being dropped, the rate-limit has been
increased. The side-effect is that more messages are being allowed
within a minute to lower performance.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Iff015e1f45e7f79f73d1a03d05af88832b6f972d
|
|
Enable support for smbios-mdr using IPMI BLOB transport protocol,
and disable the cpuinfo feature.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I035889f3ce0792a06c85a8ea713a19e24c24e546
|