| /openbmc/openbmc-test-automation/redfish/update_service/ |
| H A D | test_redfish_image_upload.robot | 20 # TFTP_SERVER The host name or IP of the TFTP server.
81 Redfish TFTP Failure To Upload BMC Image With Bad Manifest
82 [Documentation] Upload a BMC firmware with a bad MANIFEST file via TFTP.
84 [Template] Redfish TFTP Bad Firmware Update
90 Redfish TFTP Failure To Upload Empty BMC Image
91 [Documentation] Upload a BMC firmware with no kernel image via TFTP.
93 [Template] Redfish TFTP Bad Firmware Update
99 Redfish TFTP Failure To Upload Host Image With Bad Manifest
100 [Documentation] Upload a PNOR firmware with a bad MANIFEST file via TFTP.
102 [Template] Redfish TFTP Bad Firmware Update
[all …]
|
| H A D | test_firmware_tftp_upload_image.robot | 2 Documentation Firmware image (BMC and Host) upload test using TFTP protocol.
5 # TFTP_SERVER The TFTP server host name or IP address.
33 TFTP Download Install With ApplyTime OnReset Policy
34 [Documentation] Download image to BMC using TFTP with OnReset policy and verify installation.
36 [Template] TFTP Download Install
42 TFTP Download Install With ApplyTime Immediate Policy
43 [Documentation] Download image to BMC using TFTP with Immediate policy and verify installation.
45 [Template] TFTP Download Install
88 TFTP Download Install
89 [Documentation] Download image to BMC using TFTP with ApplyTime policy and verify installation.
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.update | 1 Automatic software update from a TFTP server
7 This feature allows to automatically store software updates present on a TFTP
8 server in NOR Flash. In more detail: a TFTP transfer of a file given in
13 TFTP transfer is successful, the hash of each update is verified, and if the
31 Normally, TFTP transfer of the update file is done to the address specified
39 These knobs control the timeouts during initial connection to the TFTP
41 have a long delay when a TFTP server is not present.
55 If an optional, non-zero address is provided as argument, the TFTP transfer
75 Place 'update_uboot.itb' on a TFTP server, for example as
82 Now, when the system boots up and the update TFTP server specified in the
[all …]
|
| H A D | README.dfutftp | 7 Device Firmware Upgrade (DFU) - extension to use TFTP
13 * Update TFTP (CONFIG_UPDATE_TFTP) only supports writing
14 code to NAND memory via TFTP.
26 via TFTP protocol.
28 By using Ethernet (TFTP protocol to be precise) it is
39 for USB based DFU (CONFIG_DFU_*) and DFU TFTP update
42 The "dfu" command has been extended to support transfer via TFTP - one
81 * set "updatefile" - the file name to be downloaded via TFTP (stored on
119 * Extend dfu-util command to support TFTP based transfers
120 * Upload support (via TFTP)
|
| H A D | README.iscsi | 10 address of a boot script. TFTP or NFS can be used to load the boot script, the
20 a new kernel version the boot files have to be copied to the TFTP server
30 Thus a better solution than DHCP/TFTP/NFS boot would be to load a boot script
|
| /openbmc/openbmc-test-automation/gui/test/server_config/ |
| H A D | test_obmc_gui_firmware_update.robot | 52 # BMC Firmware File Path located at TFTP server.
54 [Template] Upload Firmware using TFTP Server
55 [Documentation] Verify BMC image is download from TFTP server.
60 # Host Firmware File Path located at TFTP server.
62 [Template] Upload Firmware using TFTP Server
63 [Documentation] Verify Host image is download from TFTP server.
77 Upload Firmware using TFTP Server
78 [Documentation] Upload firmware using TFTP server.
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Common/TFTP/ |
| H A D | meson.build | 3 sdbusplus_current_path = 'xyz/openbmc_project/Common/TFTP'
8 '../../../../../yaml/xyz/openbmc_project/Common/TFTP.interface.yaml',
28 'xyz/openbmc_project/Common/TFTP',
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | license_service.hpp | 18 TFTP, enumerator
31 {TransferProtocolType::TFTP, "TFTP"},
|
| H A D | update_service.hpp | 19 TFTP, enumerator
53 {TransferProtocolType::TFTP, "TFTP"},
|
| H A D | virtual_media.hpp | 35 TFTP, enumerator
79 {TransferProtocolType::TFTP, "TFTP"},
|
| H A D | protocol.hpp | 38 TFTP, enumerator
84 {Protocol::TFTP, "TFTP"},
|
| H A D | log_service.hpp | 95 TFTP, enumerator
192 {TransferProtocolType::TFTP, "TFTP"},
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | tftpy_0.8.2.bb | 1 SUMMARY = "Tftpy is a TFTP library for the Python programming language. It includes client and serv…
2 DESCRIPTION = "Tftpy is a TFTP library for the Python programming language. It \
|
| /openbmc/u-boot/doc/SPL/ |
| H A D | README.am335x-network | 52 - If you plan to use TFTP server on another machine you have to set
73 2. Setup TFTP server.
74 Install TFTP server and put image files to it's root directory
90 3. Copy debrick.scr to TFTP root directory. You also need to copy
91 there all the files your script tries to load via TFTP. Example script
|
| /openbmc/docs/architecture/code-update/ |
| H A D | firmware-update-over-redfish.md | 45 Existing OpenBMC only has support for TFTP.
77 - Support a TFTP based SimpleUpdate
172 TFTP, ...). The existing back end of OpenBMC only supports TFTP so initially
177 interface on OpenBMC requires two parameters, the TFTP server address and the
191 # Request OpenBMC to download from TFTP server and activate the image
193 [ImageURI=<tftp server ip>/<file name>, TransferProtocol=TFTP]
196 TFTP is an insecure protocol. There is no username or password associated with
200 they are doing and the level of security available with TFTP.
202 Due to the security concerns with TFTP, this feature will be disabled by default
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rarpd/rarpd/ |
| H A D | 0001-rarpd.8-add-man-file.patch | 39 +in hexadecimal uppercase letters is present in the TFTP boot directory
58 +Skip the check for bootable image in the TFTP boot directory. If not
69 +as the TFTP boot directory for bootable image checks.
|
| /openbmc/u-boot/drivers/dfu/ |
| H A D | Kconfig | 18 bool "DFU via TFTP"
22 sent via TFTP boot.
|
| /openbmc/linux/Documentation/arch/arm/sa1100/ |
| H A D | cerf.rst | 26 both BOOTP and TFTP. Detailed instructions should have come with your
33 cp arch/arm/boot/zImage <TFTP directory>
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Common/ |
| H A D | meson.build | 12 subdir('TFTP') subdir
276 input: ['../../../../yaml/xyz/openbmc_project/Common/TFTP.interface.yaml'],
277 output: ['TFTP.md'],
289 'xyz/openbmc_project/Common/TFTP',
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/tftp-hpa/ |
| H A D | tftp-hpa_5.2.bb | 3 "The Trivial File Transfer Protocol (TFTP) is normally used only for \
5 interface for TFTP, which allows users to transfer files to and from a \
6 remote machine. This program and TFTP provide very little security, \
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/atftp/atftp/ |
| H A D | atftpd.service | 2 Description=Advanced TFTP Server
|
| /openbmc/phosphor-bmc-code-mgmt/bmc/ |
| H A D | download_manager.hpp | 17 sdbusplus::server::xyz::openbmc_project::common::TFTP>;
|
| /openbmc/docs/ |
| H A D | REDFISH-cheatsheet.md | 146 TFTP Firmware update using TransferProtocol: Note: The `<image file path>`
147 contains the address of the TFTP service:
151 …UpdateService/Actions/UpdateService.SimpleUpdate -d '{"TransferProtocol":"TFTP","ImageURI":"<image…
154 TFTP Firmware update with protocol in ImageURI:
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/inetutils/inetutils/ |
| H A D | tftpd.xinetd.inetutils | 4 # Pro-tocol (RFC 783). The TFTP server operates at the port indicated
|
| /openbmc/u-boot/board/freescale/mpc8544ds/ |
| H A D | README | 101 After placing the DTB file in your TFTP disk area,
112 Place a linux uImage in the TFTP disk area too.
|