Lines Matching full:firmware
7 Repair actions and verifiers relating to CrOS firmware.
10 with the firmware installed on ChromeOS DUTs, and when necessary, to
11 fix problems by updating or re-installing the firmware.
15 corrupted firmware. The module supplies `FirmwareStatusVerifier`
17 re-install firmware of current faft stable_version via servo
20 designated "stable" firmware version. This module supplies
22 firmware that is out-of-date from the designated version. This model
23 also supplys `GeneralFirmwareRepair` to re-install firmware that
29 and install the stable firmware using `FirmwareVersionVerifier`.
30 * DUTs in pools used for FAFT testing. These check for bad firmware
33 stable firmware.
71 check if a host is dedicated for firmware testing.
86 Return whether a DUT should be running the standard firmware.
89 pool) need their firmware kept up-to-date with
91 policies for firmware management. This returns whether a given DUT
103 """Get the available RW firmware version given the model.
105 @param host The host to get available firmware for.
106 @param model The model name to get corresponding firmware version.
107 @return The available RW firmware version if found, else, None.
125 Verify that a host's firmware is in a good state.
127 For DUTs that run firmware tests, it's possible that the firmware
129 appears that firmware should be re-flashed using servo.
137 # Read the AP firmware and dump the sections that we're
146 # Verify the firmware blocks A and B.
154 'Firmware %c is in a bad state.' % c)
161 return 'Firmware on this DUT is clean'
166 Reinstall the firmware image using servo.
169 designated "stable firmware version".
179 # Use firmware in current stable os build.
202 'Could not determine which firmware image to use'
203 ' due to signed firmware image variant exists but'
208 # Before flash firmware we want update the build into health profile.
213 logging.info('Attempting to flash ec firmware...')
216 logging.info('Attempting to flash bios firmware...')
222 # flash firmware via servo will turn DUT into dev mode, so disable
231 Reinstall the firmware for DUTs in faft related pool.
241 ' use firmware on OS stable_version.')
254 return 'Re-install the stable firmware(faft) via servo'
258 """Reinstall the firmware for non-faft DUTs.
259 We need different RepairAction for non firmware testing DUT because
260 we want only try re-install firmware if all other RepairAction could
279 ' minimum requirement to flash firmware.', host.hostname)
280 # Flash firmware via servo is consider an expansive opertation, so we
282 # firmware repair is need.
286 ' determine if firmware repair is needed.')
294 'Firmware repair will only applies to DUT that'
300 # If we had an success firmware flash in this repair loop,
301 # there is no need to retry flash the same firmware build.
305 'Firmware from %s has been already installed on %s,'
311 'Firmware from %s has been attempted and failed 3 '
318 return 'Re-install the stable firmware(non-faft) via servo'
323 Check for a firmware update, and apply it if appropriate.
325 This verifier checks to ensure that either the firmware on the DUT
326 is up-to-date, or that the target firmware can be installed from the
332 2. The DUT's board has an assigned stable firmware version.
333 3. The DUT is not running the assigned stable firmware.
334 4. The firmware supplied in the running OS build is not the
335 assigned stable firmware.
338 supplies the necessary firmware, the verifier installs the new
339 firmware using `chromeos-firmwareupdate`. Failure to install will
349 out-of-band. But a firmware update will likely hit all DUTs at
353 the stable repair image. If the firmware is out-of-date, but the
354 stable repair image does *not* contain the proper firmware version,
369 Check that two firmware versions identify the same hardware.
371 Firmware version strings look like this:
374 the firmware was built. This function checks that the hardware
378 firmware on a DUT when a board label has somehow gone astray.
380 @param version_a First firmware version for the comparison.
381 @param version_b Second firmware version for the comparison.
386 message = 'Hardware/Firmware mismatch updating %s to %s'
394 from installing the firmware from bad/broken/no-tested image. Bad
395 image can have broken updater or corrupted firmware.
408 'Firmware update can be run only from stable image.'
417 # Test 2 - The DUT has an assigned stable firmware version.
421 'Can not verify firmware version. '
433 # This DUT doesn't have a firmware update target
442 # Test 3 - The DUT is not running the target stable firmware.
445 logging.error('DUT firmware version can\'t be determined.')
450 # Test 4 - The firmware supplied in the running OS build is not
451 # the assigned stable firmware.
454 logging.error('Supplied firmware version in OS can\'t be '
460 'DUT firmware requires update from %s to %s' %
462 # Time to update the firmware.
463 logging.info('Updating firmware from %s to %s',
484 return 'The firmware on this DUT is up-to-date'