| /openbmc/docs/designs/ |
| H A D | psu-firmware-update.md | 1 # PSU firmware update
11 There is no support in OpenBMC to update the firmware for PSUs.
15 In OpenBMC, there is an existing interface for [software update][1].
17 The update process consists of:
23 Currently, BMC and BIOS firmware update are supported:
25 - [phosphor-bmc-code-mgmt][2] implements BMC code update, and it supports all
27 - [openpower-pnor-code-mgmt][3] implements BIOS code update, and it only
32 For PSU firmware update, it is preferred to re-use the same function for the
39 1. The user manually invokes the APIs to do the update;
40 2. After BMC code update and if there is a newer PSU image in the BMC's
[all …]
|
| H A D | code-update.md | 1 # Code Update Design
12 1. Current code update flow is complex as it involves 3 different daemons -
13 Image Manager, Image Updater and Update Service.
14 2. Update invocation flow has no explicit interface but rather depends upon the
25 - [Code Update Design](https://github.com/openbmc/docs/tree/master/architecture/code-update)
29 1. Able to start an update, given a firmware image and update settings.
31 - Update settings shall be able to specify when to apply the image, for example
34 2. Able to retrieve the update progress and status.
38 a firmware update.
39 5. Update request shall respond back immediately, so client can query the status
[all …]
|
| H A D | firmware-update-via-usb.md | 1 # In-Band Update of BMC Firmware using USB
15 In order to perform an update, need first to bring the image into the BMC
38 phosphor-usb-code-update). The design process is as follows:
40 - Define a macro switch (`usb-code-update`) in [phosphor-software-manager][1]
41 repository to identify whether to enable the USB Code Update function, which
43 - If `usb-code-update` enabled, install the udev rules file to
46 start the phosphor-usb-code-update daemon.
49 - Set ApplyTime to OnReset so that the proposed usb code update app does not
51 - Set RequestedActivation to Active, follow the updated status, start to update
53 - Exit the phosphor-usb-code-update daemon.
[all …]
|
| H A D | firmware-update-via-blobs.md | 1 # In-Band Update of BMC Firmware (and others) using OEM IPMI Blob Transport
19 update mechanism that can be done in-band between the host and the BMC.
39 - Any update mechanism must provide support for UBI tarballs and legacy (static
43 - Any update mechanism must allow for triggering an image verification step
46 - Any update mechanism must allow implementing the data staging via different
49 - Any update mechanism must provide a handshake or equivalent protocol for
54 - Any update mechanism must attempt to maintain security, insomuch as not
100 `/flash/bios` without completing (or later aborting) the first update process
132 successfully, it'll add an update blob id, defined below.
136 #### Update Blob
[all …]
|
| /openbmc/u-boot/arch/x86/cpu/intel_common/ |
| H A D | microcode.c | 6 * Microcode update for Intel PIII and later CPUs
25 * whether the update is applicable or not. We also use the same structure
41 struct microcode_update *update) in microcode_decode_node() argument
43 update->data = fdt_getprop(blob, node, "data", &update->size); in microcode_decode_node()
44 if (!update->data) in microcode_decode_node()
47 update->header_version = fdtdec_get_int(blob, node, in microcode_decode_node()
49 update->update_revision = fdtdec_get_int(blob, node, in microcode_decode_node()
50 "intel,update-revision", 0); in microcode_decode_node()
51 update->date_code = fdtdec_get_int(blob, node, in microcode_decode_node()
53 update->processor_signature = fdtdec_get_int(blob, node, in microcode_decode_node()
[all …]
|
| /openbmc/openbmc-test-automation/redfish/update_service/ |
| H A D | test_redfish_bmc_code_update.robot | 2 Documentation Update firmware on a target BMC via Redifsh.
7 # Firmware update states:
45 Redfish Code Update With ApplyTime OnReset
46 [Documentation] Update the firmware image with ApplyTime of OnReset.
48 [Template] Redfish Update Firmware
54 Redfish Code Update With ApplyTime Immediate
55 [Documentation] Update the firmware image with ApplyTime of Immediate.
57 [Template] Redfish Update Firmware
63 Redfish Code Update Same Firmware Multiple Times
64 [Documentation] Multiple times update the firmware image for update service.
[all …]
|
| H A D | test_redfish_host_code_update.robot | 2 Documentation Update firmware on a target Host via Redifsh.
7 # Firmware update states:
34 Redfish Host Code Update With ApplyTime OnReset
35 [Documentation] Update the firmware image with ApplyTime of OnReset.
37 [Template] Redfish Update Firmware
43 Redfish Host Code Update With ApplyTime Immediate
44 [Documentation] Update the firmware image with ApplyTime of Immediate.
46 [Template] Redfish Update Firmware
52 BMC Reboot When PNOR Update Goes On
53 [Documentation] Trigger PNOR update and do BMC reboot.
[all …]
|
| H A D | test_redfish_signed_image_update.robot | 2 Documentation Redfish BMC/Host signed and unsigned code update
8 # Firmware update states:
36 Redfish Signed Code Update
37 [Documentation] BMC/Host signed code update over functional signed
40 [Template] Redfish Signed Firmware Update
46 Redfish Fail Unsigned Code Update
47 [Documentation] BMC/Host unsigned code update over functional signed
50 [Template] Redfish Unsigned Firmware Update
77 Redfish Signed Firmware Update
78 [Documentation] Update the BMC/Host firmware via redfish interface.
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/opkg-utils/ |
| H A D | opkg-utils_0.7.0.bb | 2 SUMMARY:update-alternatives-opkg = "Utility for managing the alternatives system"
8 PROVIDES += "${@bb.utils.contains('PACKAGECONFIG', 'update-alternatives', 'virtual/update-alternati…
11 file://0001-update-alternatives-correctly-match-priority.patch \
27 PACKAGECONFIG = "python update-alternatives"
29 PACKAGECONFIG[update-alternatives] = ",,,"
33 if ! ${@bb.utils.contains('PACKAGECONFIG', 'update-alternatives', 'true', 'false', d)}; then
34 rm -f "${D}${bindir}/update-alternatives"
43 if [ -e "${D}${bindir}/update-alternatives" ]; then
44 …sed -i ${D}${bindir}/update-alternatives -e 's,/usr/bin,${bindir},g; s,/usr/lib,${nonarch_libdir},…
52 PACKAGES =+ "update-alternatives-opkg"
[all …]
|
| /openbmc/docs/architecture/code-update/ |
| H A D | code-update-deprecated.md | 1 # OpenBMC Code Update
6 [code-update.md](code-update.md) for the new APIs to do code update.
9 The host code update can be found here:
10 [host-code-update.md](host-code-update.md)
50 ## Preparing for BMC code Update
66 monitored over the network. The `update` script can then be called to write the
69 ## Update from the OpenBMC shell
71 To update from the OpenBMC shell, follow the steps in this section.
73 It is recommended that the BMC be prepared for update (note that the environment
85 (preserving the filename), then run the `update` script to apply the images:
[all …]
|
| H A D | firmware-update-over-redfish.md | 1 # Firmware update over Redfish
15 OpenBMC's existing firmware update implementation over to Redfish.
19 The existing firmware update details for OpenBMC can be found [here][2]. It uses
22 The Redfish schema for firmware update can be found [here][3]. Note the
29 - Redfish has a single upload and update API. OpenBMC has a concept of uploading
41 - Redfish does support the ability to update multiple targets with the same
46 - Redfish has the ability to schedule when a firmware update is applied
51 commands for their firmware update implementations ([ref a][5], [ref b][6]).
53 Redfish firmware update within OpenBMC has already started within [bmcweb][7]
68 - Support firmware update for all supported targets (BMC, BIOS) using existing
[all …]
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | release-notes-4.0.rst | 312 * gstreamer1.0: update licenses of all modules to LGPL-2.1-or-later (with some exceptions that are …
318 * libx11-compose-data: update :term:`LICENSE` to "MIT & MIT-style & BSD-1-Clause & HPND & HPND-sell…
319 * libx11: update :term:`LICENSE` to "MIT & MIT-style & BSD-1-Clause & HPND & HPND-sell-variant" to …
333 script can be used to update your recipes.
379 - adwaita-icon-theme: update 3.34/38 -> 41.0
386 - at: update 3.2.2 -> 3.2.5
388 - automake: update 1.16.3 -> 1.16.5
394 - boost: update 1.77.0 -> 1.78.0
396 - buildtools-installer: Update to use 3.4
398 - ca-certificates: update 20210119 -> 20211016
[all …]
|
| H A D | release-notes-4.2.rst | 56 - New :ref:`ref-classes-cargo-update-recipe-crates` class to
325 - ``poky-bleeding`` distro: update and rework
327 - ``cve-update-nvd2-native``: new NVD CVE database fetcher using the 2.0 API
389 - adwaita-icon-theme: update 42.0 -> 43
393 - apr: update 1.7.0 -> 1.7.2
394 - apr-util: update 1.6.1 -> 1.6.3
399 - base-passwd: Update to 3.6.1
400 - bash: update 5.1.16 -> 5.2.15
403 - bluez: update 5.65 -> 5.66
404 - boost-build-native: update 1.80.0 -> 1.81.0
[all …]
|
| /openbmc/linux/tools/testing/selftests/bpf/progs/ |
| H A D | htab_mem_bench.c | 58 struct update_ctx update; in overwrite() local
60 update.from = bpf_get_smp_processor_id(); in overwrite()
61 update.step = nr_thread; in overwrite()
62 bpf_loop(OP_BATCH, overwrite_htab, &update, 0); in overwrite()
70 struct update_ctx update; in batch_add_batch_del() local
72 update.from = bpf_get_smp_processor_id(); in batch_add_batch_del()
73 update.step = nr_thread; in batch_add_batch_del()
74 bpf_loop(OP_BATCH, overwrite_htab, &update, 0); in batch_add_batch_del()
76 update.from = bpf_get_smp_processor_id(); in batch_add_batch_del()
77 bpf_loop(OP_BATCH, del_htab, &update, 0); in batch_add_batch_del()
[all …]
|
| H A D | test_bpf_cookie.c | 23 static void update(void *ctx, __u64 *res) in update() function
34 update(ctx, &kprobe_res); in handle_kprobe()
41 update(ctx, &kretprobe_res); in handle_kretprobe()
48 update(ctx, &uprobe_res); in handle_uprobe()
55 update(ctx, &uretprobe_res); in handle_uretprobe()
67 update(ctx, &tp_res); in handle_tp1()
73 update(ctx, &tp_res); in handle_tp2()
79 update(ctx, &tp_res); in handle_tp3()
86 update(ctx, &pe_res); in handle_pe()
93 update(ctx, &fentry_res); in BPF_PROG()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.update | 1 Automatic software update from a TFTP server
10 boot. The update file should be a FIT file, and can contain one or more
11 updates. Each update in the update file has an address in NOR Flash where it
13 TFTP transfer is successful, the hash of each update is verified, and if the
14 verification is positive, the update is stored in Flash.
16 The auto-update feature is enabled by the CONFIG_UPDATE_TFTP macro:
21 Note that when enabling auto-update, Flash support must be turned on. Also,
27 The auto-update feature uses the following configuration knobs:
31 Normally, TFTP transfer of the update file is done to the address specified
48 Since the update file is in FIT format, it is created from an *.its file using
[all …]
|
| /openbmc/linux/drivers/gpu/drm/amd/display/dc/core/ |
| H A D | dc_debug.c | 186 const struct dc_surface_update *update = &updates[i]; in update_surface_trace() local
188 SURFACE_TRACE("Update %d\n", i); in update_surface_trace()
189 if (update->flip_addr) { in update_surface_trace()
194 update->flip_addr->address.type, in update_surface_trace()
195 update->flip_addr->address.grph.addr.quad_part, in update_surface_trace()
196 update->flip_addr->address.grph.meta_addr.quad_part, in update_surface_trace()
197 update->flip_addr->flip_immediate); in update_surface_trace()
200 if (update->plane_info) { in update_surface_trace()
211 update->plane_info->color_space, in update_surface_trace()
212 update->plane_info->format, in update_surface_trace()
[all …]
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | meson.options | 9 option('host-bios', type: 'boolean', value: false, description: 'Install default BIOS update config…
10 option('reboot-update', type: 'boolean', value: false, description: 'Enable use of reboot update me…
11 option('update-status', type: 'boolean', value: false, description: 'Enable use of update status fi…
13 option('update-type', type : 'combo', choices : ['none', 'static-layout', 'tarball-ubi'], descripti…
32 …alue : '/run/initramfs/bmc-image', description : 'The file to use for staging the firmware update')
33 …, type : 'string', value : '/tmp/image-update.tar', description : 'The file to use for staging the…
36 option('update-status-filename', type : 'string', value : '/tmp/bmc.update', description : 'The fil…
39 …prepare.target', description : 'The systemd target started when the host starts to send an update')
41 option('update-dbus-service', type : 'string', value : 'phosphor-ipmi-flash-bmc-update.target', des…
42 …, value : 'bios-staged-name', description : 'The file to use for staging the bios firmware update')
[all …]
|
| /openbmc/openbmc-test-automation/redfish/extended/ |
| H A D | redfish_bmc_code_update.robot | 2 Documentation Update the BMC code on a target BMC via Redifsh.
7 # Firmware update states:
44 # New code update path.
45 ${REDFISH_UPDATE_URI} /redfish/v1/UpdateService/update
49 Redfish BMC Code Update
50 [Documentation] Update the firmware image.
78 Print Timen Performing firmware update ${image_version}.
80 Redfish Update Firmware
83 Redfish BMC Code Update Running And Backup Image With Same Firmware
84 [Documentation] Perform the firmware update with same image back to back, so that
[all …]
|
| /openbmc/openbmc-test-automation/oem/nuvoton/ |
| H A D | test_ipmi_flash.robot | 2 Documentation Module to test In band firmware update.
25 Test BIOS Firmware Update
26 [Documentation] Test BIOS firmware update over IPMI.
32 Update BIOS Firmware ${IMAGE_HOST_FILE_PATH_0}
38 Update BIOS Firmware ${IMAGE_HOST_FILE_PATH_1}
44 Test Invalid BIOS Firmware Update
45 [Documentation] Test Invalid BIOS firmware update over IPMI.
51 ${cmd}= Catenate ${HOST_WORK_DIR}/burn_my_bmc --command update --interface ipmilpc
58 Test BMC Firmware Update
59 [Documentation] Test BMC firmware update over IPMI.
[all …]
|
| /openbmc/openbmc-test-automation/redfish/account_service/ |
| H A D | test_ldap_configuration.robot | 67 # After update, LDAP login.
79 # After update, LDAP login.
84 Verify LDAP Config Update With Incorrect AuthenticationType
101 Verify LDAP Config Update With Incorrect LDAP URL
149 Update LDAP Configuration with LDAP User Role And Group ${LDAP_TYPE}
164 Update LDAP Configuration with LDAP User Role And Group ${LDAP_TYPE}
187 Update LDAP Configuration with LDAP User Role And Group ${LDAP_TYPE}
223 Update LDAP Group Name And Verify Operations
224 [Documentation] Verify that LDAP group name update and able to do right
227 [Template] Update LDAP Config And Verify Set Host Name
[all …]
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | upd.c | 8 * Jan 2007: Alexander Schmidt, hacked per-volume update.
12 * This file contains implementation of the volume update and atomic LEB change
15 * The update operation is based on the per-volume update marker which is
16 * stored in the volume table. The update marker is set before the update
17 * starts, and removed after the update has been finished. So if the update was
18 * interrupted by an unclean re-boot or due to some other reasons, the update
20 * device next time. If the update marker is set for a volume, the volume is
21 * treated as damaged and most I/O operations are prohibited. Only a new update
24 * Note, in general it is possible to implement the update operation as a
40 * set_update_marker - set update marker.
[all …]
|
| /openbmc/linux/drivers/mtd/ubi/ |
| H A D | upd.c | 8 * Jan 2007: Alexander Schmidt, hacked per-volume update.
12 * This file contains implementation of the volume update and atomic LEB change
15 * The update operation is based on the per-volume update marker which is
16 * stored in the volume table. The update marker is set before the update
17 * starts, and removed after the update has been finished. So if the update was
18 * interrupted by an unclean re-boot or due to some other reasons, the update
20 * device next time. If the update marker is set for a volume, the volume is
21 * treated as damaged and most I/O operations are prohibited. Only a new update
24 * Note, in general it is possible to implement the update operation as a
34 * set_update_marker - set update marker.
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | pwm.h | 18 * @dev: PWM device to update
19 * @channel: PWM channel to update
30 * @dev: PWM device to update
31 * @channel: PWM channel to update
39 * @dev: PWM device to update
40 * @channel: PWM channel to update
52 * @dev: PWM device to update
53 * @channel: PWM channel to update
64 * @dev: PWM device to update
65 * @channel: PWM channel to update
[all …]
|
| /openbmc/openbmc-test-automation/extended/code_update/ |
| H A D | host_code_update.robot | 2 Documentation Update the PNOR code on a target BMC.
10 ... Code update method BMC
11 ... Update work flow sequence:
16 ... - Wait for code update to complete
30 Test Teardown Code Update Test Teardown
46 REST Host Code Update
47 [Documentation] Do a PNOR code update by uploading image on BMC via REST.
49 # 1. Do code update.
50 # 2. Do post update the following:
53 [Setup] Code Update Setup
[all …]
|