Age | Commit message (Collapse) | Author | Files | Lines |
|
Remove the IPMI service restart after writing the FRU binary,
as it makes the IPMI service unavailable for a while.
Tested:
1. Update the new FRU binary by ampere_firmware_upgrade.sh
2. Check new FRU content by "ipmitool fru print"
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Change-Id: Ibbe44b54d321c66b450acfdaa3efa363d2fc1762
|
|
Currently, the gpio-presence is configured to create CPU_1/2 object
paths when sokets 0/1 are presented. But in the SMBIOS service, it is
creating cpu0/1 object paths to indicate sockets 0/1 are presented.
By the missmatch between gpio-presence and SMIBIOS services, adc sensors
that depend on the "CPURequired" property in EM can be missed.
This commit updates the object path of CPU presence to synchronize
gpio-presence and SMBIOS services.
Tested:
1. PLDM sensors work correctly on both 1P and 2P systems.
2. ADC sensors are shown correctly.
Change-Id: Idc317b9a6280391aff7eb1aeebc70667acc29b28
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
|
|
Enable NFS distro to be able to mount NFS.
Tested:
1. Check below command (in BMC console) works
$ mount -t nfs 10.38.130.2:/tftpboot/ISO_file /tmp/mount_nfs
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I7991a268a5338da5a664403a6ba476e671481f42
|
|
It is expected to do power cycle on Mt.Mitchell with IPMI and Redfish
Host reset command.
As commit 41983bfe2 removes no-warm-reboot to be enabled by default,
need to enable in meta-ampere/meta-mitchell to support this behavior.
Tested:
1. Run ipmitool chassis power reset
--> expect to have the Host power off and then on
Change-Id: Ie61d7d5de170b0a26bd736c9b4e8789c566a93c9
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
|
|
Patrick Williams (1):
phosphor-host-condition-gpio: enable multi-host support
Fix up references in meta layers to non-numbered service name.
Change-Id: I3ae73c7e3ba7f117ade8eee5fea31d945ac0a696
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0dad5301339f6738c191bcb0dd1e226c0de079dc
|
|
The flash_bios option in PACKAGECONFIG is already defined at
meta-phosphor/recipes-phosphor/flash/phosphor-software-manager_git.bb so
don't need to duplicate it.
This commit removes the redundant declaration of flash_bios inside
meta-ampere.
Change-Id: I87cab91feaff61f53b3b9e5395d4c7b9e30d24bd
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
|
|
Most systems are fine with supporting a warm reboot so don't make it a
default.
Change-Id: Ifb906f0b0d81b97265b6b6a79104408161bded7e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Part of the functionality contained in the existing `cpuinfo` flag is
now split into a new flag `cpuinfo-peci`. The new flag is still
logically dependent on the existing one, but it gives finer control over
enabled features.
Remove all cpuinfo flags from default PACKAGECONFIG.
Update bbappend based on new defaults.
smbios-mdr: srcrev bump abdccd3af9..4e1cf09955
Jonathan Doman (1):
cpuinfoapp: Make PECI features optional
Change-Id: Ib9a1e634634f046b2ec6ff5629d4498bf0d5914b
Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
|
|
Update UBOOT_DEVICETREE from ast2600-bletchley to ast2600-ampere dtb
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Change-Id: Idb9935f693974326e4ca7cd64dce0c713015b4e4
|
|
This variable hasn't existed in upstream poky since 2016. See
commit d06c7b8ce6249529de0bde0a568c0658b7148bf4 from their repository.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I8c832b1f4abb30255bbe080c568d833df6b96a9e
|
|
Add dcmi_sensors.json to support the IPMI dcmi sensors command.
Tested:
1. Request list out the dcmi sensors
ipmitool dcmi sensors
2. 3 groups of sensors are dislayed (inlet, basebord, CPIU).
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I75981a5ef1101997d5519663e541cd57085d04e4
|
|
Update IPMI sensor configuration to correct EntityId and Entity Instance
for some sensors.
Tested:
1. Run "ipmitool sensor get" command and check the output for correct
Entity ID and Entity Instance information
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I17cb008975a00f55f0bfe142d63f698310b8b54f
|
|
Once https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69480 is merged,
any system not taking the defaults can be removed. Across the project
we should be consistent to make sure that the default behavior doesn't
cause log spamming or performance degredation.
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I95f319e6247f9b7dcf61e0d00c4366809bf3eba5
|
|
This variable, if set, creates a symlink of /var/log to
/var/volatile/log. In most cases if machines have configured
applications like obmc-console or journald to write to /var/log
they want it to be persistent. The symlink causes them to be written
to the non-persistent tmpfs space for /var/volatile.
Set all machines to `VOLATILE_LOG_DIR = no` by default.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0f973e6b8599b32451c83d5161be079e967de711
|
|
This commit removes only-run-apr-on-power-loss from PACKAGECONFIG in
meta-ampere phosphor-state-manager recipe as this has been configured
default by meta-phosphor.
Change-Id: Ia2740609c025b8f911054f6dfb6c4871bf851a14
Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
|
|
bmcweb already defaults to having the insecure options disabled, so
there is no need to additionally specify them in a bbappend.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icdee90ee62b0cf6adeeb63fabdee1c852cb9e26d
|
|
There is a preference in Yocto recipes for using PACAKGECONFIG instead
of EXTRA_OEMESON-style config. The phosphor-state-manager recipe seems
to be missing PACKAGECONFIG settings for some of the options being
applied by meta-ampere, but it does have one for
`only-run-apr-on-power-loss` so leverage that.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id91c1e53679409349e5ef681194e83f0237dd610
|
|
Any system using PLDM should already `include
conf/distro/include/pldm.inc`, which enables MCTP support as a
side-effect. By default, the pldm recipe already enables `af-mctp` (the
support for the kernel subsystem):
```
meta-phosphor/recipes-phosphor/pldm/pldm_git.bb
31:PACKAGECONFIG:append:df-mctp = " transport-af-mctp"
```
We shouldn't be setting meson options to begin with, but this one is
already duplicative and ends up being a bad example for others.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I891a4c36eb331f8af6cdef9943e178f3a524d2e7
|
|
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69228 enabled
redfish-new-powersubsystem-thermalsubsystem by default remove it here in
the bbappend to keep things cleaner.
Tested: I tested having this line removed in the meta-ibm bbappend when
testing 69228.
Change-Id: Ic91451a63ee19f6e80d61e9252de6e1bd5c3692f
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
This commit removes support for controlling uart muxes from Host. The
uart muxes will now be default to connect to BMC on AC/DC. This
therefore can remove all the mux control scripts in obmc-console recipe.
Tested:
Upon BMC AC/DC
Can successfully ssh to Host's uart consoles via BMC's IP
Example: ssh root@<BMC_IP> -p 2200
Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: Ia4f421956f182dcb5d8e2e2ef8cb4eb404a15f2d
|
|
Currently just one LED group for FAN fault check. This causes FAN
fault LED might be changed to OFF even when still having failure on
some FANs.
This commit changes to have LED group for each FAN to fix this issue.
Tested:
1. Unplug two random FANs
2. Plug one FAN into the board and verify that FAN Led status is
still on
3. Plug all FAN into the board and verify that FAN Led status is off.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I8cf2eeafbe7372b0eda85c133e88a228b5cd0a2a
|
|
Currently just one LED group for FAN fault check. This causes FAN
fault LED might be changed to OFF even when still having failure on
some FANs.
This commit changes to have LED group for each FAN to fix this issue.
Tested:
1. Unplug two random FANs
2. Plug one FAN into the board and verify that FAN Led status is
still on
3. Plug all FAN into the board and verify that FAN Led status is off.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Ic48fb402266bd3b95263ba8278e2f50d3bbb3bfe
|
|
phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This updates the led-group-config.json file to
com.ampere.Hardware.Chassis.Model.MtMitchell.json follow the
phosphor-led-manager.
Tested: verify that led config file in the system
root@mtmitchell-dcscm:~# ls /usr/share/phosphor-led-manager/
com.ampere.Hardware.Chassis.Model.MtMitchell.json
com.ibm.Hardware.Chassis.Model.Rainier1S4U.json
com.ibm.Hardware.Chassis.Model.Rainier4U.json
com.ibm.Hardware.Chassis.Model.Everest.json
com.ibm.Hardware.Chassis.Model.Rainier2U.json
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Id7a2f885a933319b8b09279689dfb627c843cf88
|
|
phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This updates the led-group-config.json file to
com.ampere.Hardware.Chassis.Model.MtMitchell.json follow the
phosphor-led-manager.
Tested: verify that led config file in the system
root@mtjade:~# ls /usr/share/phosphor-led-manager/
com.ampere.Hardware.Chassis.Model.MtJade.json
com.ibm.Hardware.Chassis.Model.Rainier1S4U.json
com.ibm.Hardware.Chassis.Model.Rainier4U.json
com.ibm.Hardware.Chassis.Model.Everest.json
com.ibm.Hardware.Chassis.Model.Rainier2U.json
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I83647f465506d3fc3202d2b8f7145a1342f86dcf
|
|
Remove shell scripts which are not used in core services.
Tested:
1. Compile Mt.Jade and Mt.Mitchell without errors
2. Check power control still works fine
Change-Id: I740b804a9e43b4826c5549a7a1e17eab745ded70
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
|
|
This commit adds bmc_ready and sw_heartbeat leds to bmc_booted group.
When BMC's status is Ready, phosphor-led-manager shall assert bmc_ready
GPIO and create bmc/sw heart-beat signals to CPLD/HOST.
By the heartbeat signals are create by leds, the service to create
heartbeat signals is redundant, therefore ampere-bmc-heartbeat.service
shall be removed.
Tested:
1. Turn on/off, power cycle, reboot host features work correctly.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: If21649c1a70a6b43acf8130561181e534f762b61
|
|
This corrects the name of the PSU from CPU1 to PSU1.
Tested:
1. Get PSUs name
busctl get-property xyz.openbmc_project.Inventory.Manager \
/xyz/openbmc_project/inventory/system/powersupply/PowerSupply0 \
xyz.openbmc_project.Inventory.Item PrettyName
s "PSU0"
busctl get-property xyz.openbmc_project.Inventory.Manager \
/xyz/openbmc_project/inventory/system/powersupply/PowerSupply1 \
xyz.openbmc_project.Inventory.Item PrettyName
s "PSU1"
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I3e1110d3b76335d7412006f75e79073f9f776151
|
|
Assert Fault LED when detecting OVERTEMP signal asserted.
This is done by adding new overtemp_fault LED group and
update the overtemp service to assert/de-assert the LED
group.
1. Start the ampere_overtemp@.service
2. Verify that the `Fault Led` is turned on and turn off after 10s.
3. Verify that Thermal Trip SEL is created.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Ifbc203bf79a13741082d84850b9e75ca6148a6cd
|
|
The phosphor-led-manager will monitors the
`xyz.openbmc_project.State.Decorator.OperationalStatus` interface
of the Inventory D-Bus object, and check whether the Inventory
D-Bus object is associated with the LED group D-Bus object, and
then update the Asserted property of the LedManager.
This adds the fan_fault led group to associations.json file to
monitors the FANs and turns on the fault led when the FANs fails.
1. Unplug the fan and verify that both `Fan Fault Led` and
`Fault Led` are turned on.
2. Plug the fan and verify that both `Fan Fault Led` and `Fault Led`
are turned off.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I2adc0fb8846c4690f8eaac3bb80e6dbf25077be3
|
|
Support FAN fault check via by enabling phosphor-led-manager's
monitor-operational-status with appropriate
phosphor-inventory-manager associations configuration.
Tested:
1. Get Led group list
$ busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/fan_fault
2. Change the fan pwm, then stop the fan control service and verify
that fault led is on
3. Start the fan control service and verify that fault led is off
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: If473ebfe288d80515217e7e5fb9dc6244dcb8ed3
|
|
Thang Q. Nguyen (2):
build: upgrade to C++23
meson_options.txt: Support for reading options from meson.options
Change-Id: I8ed2e0106b7e9be1af37f22bb98a2852c381e71a
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Change LED configuration format to json to adapt new default setting in
phosphor-led-manager application.
Tested:
1. Check if all LED Groups are created, the same as using yaml file
root@mtmitchell-dcscm:~# busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/bmc_booted
|- /xyz/openbmc_project/led/groups/power_on
|- /xyz/openbmc_project/led/groups/enclosure_identify
|- /xyz/openbmc_project/led/groups/enclosure_identify_blink
`- /xyz/openbmc_project/led/groups/systemFault
2. Check if no error message in journal log
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I7de6bfe333bad04f045c38bb9ff7aeb64eaed8bd
|
|
phosphor-led-manager changed to use json configuration by default.
However, Mt.Mitchell still uses yaml configuration which consequently
fail to parse for platform LED configuration.
This commit changes configuration from yaml to json to adapt upstream
codes.
Tested:
1. Check if all LED Groups are created, the same as using yaml file
root@mtmitchell-dcscm:~# busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/bmc_booted
|- /xyz/openbmc_project/led/groups/power_on
|- /xyz/openbmc_project/led/groups/enclosure_identify
|- /xyz/openbmc_project/led/groups/enclosure_identify_blink
`- /xyz/openbmc_project/led/groups/systemFault
2. Check if no error message in journal log
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ibdc2a566d89d8d661f299aff84539e471061090a
|
|
Add CPU and Power Supply presence interfaces using
phosphor-multi-gpip-presence.
Tested:
1. Check if CPU_x dbus exists
$ busctl get-property xyz.openbmc_project.Inventory.Manager \
/xyz/openbmc_project/inventory/system/chassis/motherboard/CPU_2 \
xyz.openbmc_project.Inventory.Item PrettyName`
s "CPU_2"
2. Check if sensors that are required with CPURequired are reported
$ ipmitool sdr list
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I7ce9819f39f8a2afb386fa6b00421f1ead935189
|
|
Remove ampere-fault-monitor application which should be implemented via
phosphor-led-manager framework.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Iecd482657383de31dae0ee74bd0ca4de41d22f63
|
|
Andrew Geissler (1):
OWNERS: Change maintainers to their user id's
Change-Id: I0125d30872a2721783358f41da688a4375195750
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I28ee50fa55ae47dd7fd8c99f8f6db8f5f6dfa53d
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I85272779478b66452acd11be93f5fea99e4c3a34
|
|
Switch to use phosphor-networkd's sync-mac feature to get and use MAC
address from FRU, replacing Ampere approach.
Tested:
1. Boot the BMC to Linux and login to console
2. Get BMC MAC address in FRU
$ ipmitool fru print 0 | grep "Board Extra"
Board Extra : 70:E2:84:8F:E3:56
3. Check eth0 HWaddr with MAC in FRU
$ ifconfig eth1 | grep HWaddr
eth1 Link encap:Ethernet HWaddr 70:E2:84:8F:E3:56
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Signed-off-by: Khang Nguyen <khangng@amperecomputing.com>
Change-Id: I7121fde2f7b8d673e3ae0b1e5a03f175a10ea578
|
|
Switch to use phosphor-networkd's sync-mac feature to get and use MAC
address from FRU, replacing Ampere approach.
Tested:
1. Boot the BMC to Linux and login to console
2. Get BMC MAC address in FRU
$ ipmitool fru print 1 | grep "Board Extra"
Board Extra : B4:05:5D:E1:01:BC
3. Check eth0 HWaddr with MAC in FRU
$ ifconfig eth0 | grep HWaddr
eth0 Link encap:Ethernet HWaddr B4:05:5D:E1:01:BC
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Signed-off-by: Khang Nguyen <khangng@amperecomputing.com>
Change-Id: Ia31589bf75306ad5a3639cb46a73813957e85e9d
|
|
This fixes packages in packagegroup as follows:
+ Removes phosphor-post-code-manager, phosphor-host-postd
which is already in packagegroup-bmc-apps
+ Adds missing phosphor-ipmi-blobs, phosphor-ipmi-blobs-binarystore
into mtjade.conf
Tested: code compiles.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Ic3f9668e4714566a814cc928067289d650a59f41
|
|
Refactor console configuration for Mt.Jade and Mt.Mitchell to avoid
duplication and make the configuration files simpler.
Tested:
1. IPMI sol on Mt.Jade and Mt.Mitchell works
2. SOL SSH on Mt.Jade and Mt.Mitchell work for all console ports
Change-Id: I68d1a3c6be530ca93f8adc1dd61906ba8b206dc5
Signed-off-by: Chau Ly <chaul@amperecomputing.com>
|
|
Update virtual sensor expression to better handle nan values by using
maxIgnoreNaN and sumIgnoreNaN functions.
Tested:
1. Check IPMI sensor report using `ipmitool sdr list`
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I901de9ad299fc318756902ded6bc938ae86579c9
|
|
Add front backplane and other on-board sensors that are available on the
Mt.Mitchell DVT board.
This commit also updates virtual sensor expression using sumIgnoreNaN
and maxIgnoreNaN functions to better handle nan values
Tested:
1. Run 'ipmitool sdr list' and check for sensor report
2. Check sensor report from Redfish and WebUI
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ia2a221929026141dbd6a2482f4017be7fe2026cc
|
|
This moves packagegroup to common to be used for all platforms.
Tested:
- All packages are available on RootFs
- ipmi sensor, fru report
- Web login
- Power control
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I87f7ddbd94e9321e452353ed21cacd0f8a4d8f74
|
|
Enable MCTP in kernel support with Mt.Mitchell MCTP configuration.
Tested:
1. Check for mctpi2c3 in ifconfig command.
2. Check for mctpd.service service started and is in running state.
3. Check for pldmd.service service started and is in running state.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I699e9bc93ae5815b8454a8cc42ec22d4cfd735e1
|
|
This commit supports log the power on sequence to analyze power on
failure. This would include:
- PSU power good monitoring to indicate PSU is powered on.
- System power good monitoring to indicate CPU is powered on.
Tested:
1. Power on Host, check the Event logs identify the system
/redfish/v1/Systems/system/LogServices/EventLog/Entries
"Message": "Host firmware boots with 1 Processor",
2. Check the Event logs in case power on failure.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: I15237d5f6be454b628529fce43424514bf445d53
|
|
In the commit 16bb75ab on the openbmc repo, it disables warm-reboot
build option in phosphor-state-manager by default. To enable warm-reboot
option, we have to remove no-warm-reboot packge configuration.
Tested:
1. Request power reset Host.
$ipmitool power reset
2. ForceWarmReboot target is called.
Change-Id: I4f7d4d4b148e77867562ed1a8efe7797f4a6d8dd
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
|
|
In the commit 16bb75ab on the openbmc repo, it disables warm-reboot by
default, we don't have to disable it again.
Tested:
1. Request power reset Host.
$ipmitool power reset
2. Reboot target is called.
Change-Id: Ie1ed12709c200d358ae4e93e55565ebd1ea68c4f
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
|