| /external/vboot_reference/ |
| D | Android.bp | 34 "firmware/include",
35 "firmware/lib/include",
36 "firmware/lib/cgptlib/include",
37 "firmware/lib/cryptolib/include",
38 "firmware/lib/tpm_lite/include",
39 "firmware/2lib/include",
46 "firmware/lib/crc8.c",
47 "firmware/lib/utility.c",
48 "firmware/lib/vboot_api_init.c",
49 "firmware/lib/vboot_common_init.c",
[all …]
|
| D | Makefile | 279 firmware/lib/crc8.c \
280 firmware/lib/utility.c \
281 firmware/lib/vboot_api_init.c \
282 firmware/lib/vboot_common_init.c \
283 firmware/lib/vboot_nvstorage.c \
284 firmware/lib/vboot_nvstorage_rollback.c \
285 firmware/lib/region-init.c \
289 firmware/lib/cryptolib/padding.c \
290 firmware/lib/cryptolib/rsa.c \
291 firmware/lib/cryptolib/rsa_utility.c \
[all …]
|
| D | README | 2 verified boot in firmware.
10 firmware/
15 Refer to firmware/README for futher details.
28 The "firmware utility" tool, used to create, sign, and validate Chrome OS
79 firmware image
92 Generating a signed firmware image:
124 firmware image.
140 --in <firmware blob file> \
143 Where <algoid> is based on the signature algorithm to use for firmware
155 --in <signed firmware image>
[all …]
|
| /external/u-boot/drivers/qe/ |
| D | qe.c | 380 int qe_upload_firmware(const struct qe_firmware *firmware) in qe_upload_firmware() argument
395 if (!firmware) { in qe_upload_firmware()
400 hdr = &firmware->header; in qe_upload_firmware()
420 if ((firmware->count < 1) || (firmware->count > MAX_QE_RISC)) { in qe_upload_firmware()
426 calc_size += (firmware->count - 1) * sizeof(struct qe_microcode); in qe_upload_firmware()
428 for (i = 0; i < firmware->count; i++) in qe_upload_firmware()
435 be32_to_cpu(firmware->microcode[i].count); in qe_upload_firmware()
447 crc = be32_to_cpu(*(u32 *)((void *)firmware + calc_size)); in qe_upload_firmware()
448 if (crc != (crc32(-1, (const void *) firmware, calc_size) ^ -1)) { in qe_upload_firmware()
456 if (!firmware->split) { in qe_upload_firmware()
[all …]
|
| /external/vboot_reference/msc/ |
| D | nmakefile | 22 CFLAGS = $(CFLAGS) /I $R\firmware\lib\include
23 CFLAGS = $(CFLAGS) /I $R\firmware\lib\cgptlib\include
24 CFLAGS = $(CFLAGS) /I $R\firmware\include
25 CFLAGS = $(CFLAGS) /I $R\firmware\stub\include
26 CFLAGS = $(CFLAGS) /I $R\firmware\lib\cryptolib\include
35 {$R\firmware\linktest}.c{$O}.obj:
38 {$R\firmware\lib}.c{$O}.obj:
41 {$R\firmware\lib\cgptlib}.c{$O}.obj:
44 {$R\firmware\lib\cryptolib}.c{$O}.obj:
47 {$R\firmware\stub}.c{$O}.obj:
[all …]
|
| /external/autotest/server/site_tests/firmware_UpdateFirmwareVersion/ |
| D | control | 9 PURPOSE = "Servo based firmware update test which checks the firmware version."
19 2. After firmware update, device restart with firmware A.
20 3. Firmware version does not increase after firmware update.
26 TEST_CLASS = "firmware"
30 This test requires a USB test image plugged in. The firmware id
31 the current running firmware must matches the system shellball's, or user
34 firmware version of the shellball and runs autoupdate. Check firmware
35 version after boot with firmware B, and then recover firmware A and B to
|
| /external/u-boot/doc/uImage.FIT/ |
| D | sec_firmware_ppa.its | 6 * For booting PPA (SEC Firmware), "firmware" is searched and loaded.
9 * respective load offsets from firmware image address.
16 firmware@1 {
19 type = "firmware";
34 type = "firmware";
44 description = "PPA Secure firmware";
45 firmware = "firmware@1";
|
| D | multi_spl.its | 8 * For booting U-Boot, "firmware" is searched first. If not found, "loadables"
18 description = "multiple firmware blobs and U-Boot, loaded by SPL";
33 type = "firmware";
40 mgmt-firmware {
41 description = "arisc management processor firmware";
42 type = "firmware";
92 loadables = "uboot", "atf", "mgmt-firmware";
|
| /external/autotest/ |
| D | global_config.ini | 316 # Released RO builds for running FAFT to qualify an AU firmware in which the
319 RELEASED_RO_BUILDS_auron_paine: auron_paine-firmware/R39-6301.58.6
320 RELEASED_RO_BUILDS_auron_yuna: auron_yuna-firmware/R39-6301.59.5
321 RELEASED_RO_BUILDS_banjo: banjo-firmware/R34-5216.334.4
322 RELEASED_RO_BUILDS_buddy: buddy-firmware/R39-6301.202.5
323 RELEASED_RO_BUILDS_candy: candy-firmware/R34-5216.310.1
324 RELEASED_RO_BUILDS_celes: celes-firmware/R46-7287.92.3
325 RELEASED_RO_BUILDS_cyan: cyan-firmware/R46-7287.57.32,cyan-firmware/R46-7287.57.25
326 RELEASED_RO_BUILDS_gandof: gandof-firmware/R39-6301.155.9
327 RELEASED_RO_BUILDS_gnawty: gnawty-firmware/R34-5216.239.34,gnawty-firmware/R34-5216.239.16
[all …]
|
| /external/autotest/server/site_tests/firmware_CorruptBothFwBodyAB/ |
| D | control | 9 PURPOSE = "Servo based both firmware body A and B corruption test"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
14 TEST_CLASS = "firmware"
19 This test corrupts both firmware body A and B and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the firmware verification fails on loading RW firmware and enters recovery
|
| D | control.dev | 9 PURPOSE = "Servo based both firmware body A and B corruption test"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
14 TEST_CLASS = "firmware"
19 This test corrupts both firmware body A and B and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the firmware verification fails on loading RW firmware and enters recovery
|
| /external/u-boot/arch/arm/cpu/armv8/ |
| D | Kconfig | 9 Say Y here if there is not any trust firmware to set
17 register may be controlled by EL3/EL2 firmware. To be more
18 precise, by default (if there is EL2/EL3 firmware running)
44 menu "ARMv8 secure monitor firmware"
46 bool "Enable ARMv8 secure monitor firmware framework support"
50 This framework is aimed at making secure monitor firmware load
54 - Address of secure firmware.
55 - Address to hold the return address from secure firmware.
56 - Secure firmware FIT image related information.
58 - The target exception level that secure monitor firmware will
[all …]
|
| /external/autotest/server/site_tests/firmware_CorruptFwBodyA/ |
| D | control | 9 PURPOSE = "Servo based firmware A body corruption test"
10 CRITERIA = "This test will fail if firmware verification mis-behaved"
14 TEST_CLASS = "firmware"
19 This test corrupts firmware body A and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the RW firwmare A corruption will result booting the firmware B.
|
| D | control.dev | 9 PURPOSE = "Servo based firmware A body corruption test"
10 CRITERIA = "This test will fail if firmware verification mis-behaved"
14 TEST_CLASS = "firmware"
19 This test corrupts firmware body A and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the RW firwmare A corruption will result booting the firmware B.
|
| /external/autotest/server/site_tests/firmware_CorruptFwBodyB/ |
| D | control | 9 PURPOSE = "Servo based firmware B body corruption test"
10 CRITERIA = "This test will fail if firmware verification mis-behaved"
14 TEST_CLASS = "firmware"
19 This test corrupts firmware body B and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the RW firwmare B corruption will result booting the firmware A.
|
| D | control.dev | 9 PURPOSE = "Servo based firmware B body corruption test"
10 CRITERIA = "This test will fail if firmware verification mis-behaved"
14 TEST_CLASS = "firmware"
19 This test corrupts firmware body B and checks the next boot results.
21 The expected behavior is different if the firmware preamble USE_RO_NORMAL
22 flag is enabled. In the case USE_RO_NORMAL ON, the firmware corruption
24 not load and verify the RW firmware body. In the case USE_RO_NORMAL OFF,
25 the RW firwmare B corruption will result booting the firmware A.
|
| /external/ltp/testcases/kernel/firmware/fw_load_kernel/ |
| D | README | 1 The aim of the test is to check device firmware loading. Since kernel 3.7
2 firmware loading changed to direct loading (by-pass udev). The test consists
7 This is a kernel module, which is a part of the device firmware loading test.
9 Template firmware file name and expected firmware file's data size are passed
10 as the insmod command line parameters. Then, the number of firmware test files
12 will initiate request firmware procedure. In the end, results can be read from
|
| /external/autotest/server/site_tests/firmware_Fingerprint/ |
| D | control.ro_can_update_rw | 10 Validates that the RO fingerprint firmware can update the RW firmware.
13 Fails if the RO fingerprint firmware cannot update the RW firmware.
18 TEST_CLASS = "firmware"
24 Flashes RW firmware with a version string that ends in '.rb0'
26 firmware with version string that ends in '.dev' (also has rollback ID '0')
|
| /external/autotest/server/site_tests/hardware_DiskFirmwareUpgrade/ |
| D | control | 15 The test uses a list of firmware packages and applies them to the DUT.
17 Each directory normaly contains a rule file and bzipped firmware image.
21 1 - the expected return code of chromeos-disk-firmware-update.sh:
24 - True if the update script should upgrade the firmware on the SSD.
25 - False if the update script is not supposed to touch the firmware on the SSD.
32 'broken_firmware_liteon': [0, True], # revert to previous firmware
43 'test_firmware' : [0, True], # revert to previous firmware
47 'test_firmware' : [0, True], # revert to previous firmware
51 'test_firmware' : [0, True], # revert to previous firmware
|
| /external/u-boot/drivers/net/fm/ |
| D | fm.c | 110 const struct qe_firmware *firmware) in fman_upload_firmware() argument
118 if (!firmware) { in fman_upload_firmware()
123 hdr = &firmware->header; in fman_upload_firmware()
130 firmware); in fman_upload_firmware()
142 if ((firmware->count != 1)) { in fman_upload_firmware()
148 calc_size += (firmware->count - 1) * sizeof(struct qe_microcode); in fman_upload_firmware()
150 for (i = 0; i < firmware->count; i++) in fman_upload_firmware()
157 be32_to_cpu(firmware->microcode[i].count); in fman_upload_firmware()
170 crc = be32_to_cpu(*(u32 *)((void *)firmware + calc_size)); in fman_upload_firmware()
171 if (crc != (crc32(-1, (const void *)firmware, calc_size) ^ -1)) { in fman_upload_firmware()
[all …]
|
| /external/ltp/testcases/kernel/firmware/fw_load_user/ |
| D | README | 1 The aim of the test is to check device firmware loading. Since kernel 3.7
2 firmware loading changed to direct loading (by-pass udev). The test consists
8 - create firmware files in the standard firmware paths
9 - load the module and initiate firmware request procedure
|
| /external/autotest/server/site_tests/enterprise_CFM_LogitechMeetupUpdater/ |
| D | control | 19 This test verifies that the Logitech Meetup firmware updater is working
22 - Backup the original firmware.
23 - Copy older firmware bundled with test.
24 - Force upgrade the Meetup device to older firmware.
25 - Powercycle the usb port to trigger the firmware updater.
26 - Confirm firmware has been updated.
|
| /external/autotest/server/site_tests/enterprise_CFM_Aver520Updater/ |
| D | control.vc520 | 20 This test verifies that the Aver VC520 camera firmware updater is working
23 - Backup the original firmware.
24 - Copy older firmware bundled with test.
25 - Force upgrade the Aver device to older firmware.
26 - Powercycle the usb port to trigger the firmware updater.
27 - Confirm firmware has been updated.
|
| D | control.cam520 | 19 This test verifies that the Aver CAM520 camera firmware updater is working
22 - Backup the original firmware.
23 - Copy older firmware bundled with test.
24 - Force upgrade the Aver device to older firmware.
25 - Powercycle the usb port to trigger the firmware updater.
26 - Confirm firmware has been updated.
|
| /external/autotest/server/site_tests/firmware_RollbackFirmware/ |
| D | control | 9 PURPOSE = "Servo based firmware rollback test."
10 CRITERIA = "This test will fail if firmware rollback doesn't fail verification."
14 TEST_CLASS = "firmware"
21 firmware A and results firmware B boot. It then rollbacks firmware B and
|