diff options
Diffstat (limited to 'docs/fingerprint/fingerprint-factory-requirements.md')
-rw-r--r-- | docs/fingerprint/fingerprint-factory-requirements.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/fingerprint/fingerprint-factory-requirements.md b/docs/fingerprint/fingerprint-factory-requirements.md index 4aaf564570..0b9659efb3 100644 --- a/docs/fingerprint/fingerprint-factory-requirements.md +++ b/docs/fingerprint/fingerprint-factory-requirements.md @@ -61,11 +61,13 @@ dartmonkey The corresponding firmware for the above command would be `/opt/google/biod/fw/dartmonkey_*.bin`. +<!-- mdformat off(b/139308852) --> *** note **NOTE**: If you get an empty response when running the above commands, the Chrome OS Config settings may not have been updated for the Chrome OS board. See the instructions on [updating Chrome OS Config] for fingerprint. *** +<!-- mdformat on --> Note that the fingerprint team continuously releases updates to the firmware, so SIEs should watch for version changes in ToT if they are maintaining a separate @@ -88,12 +90,14 @@ the rootfs. Note that this update process can take around 30 seconds; if that length of time is an issue then the factory or module house should pre-flash the latest firmware beforehand. +<!-- mdformat off(b/139308852) --> *** note **NOTE**: If the FPMCU is not flashed in the factory as part of development builds (EVT, etc.), it's possible for developers (or Chromestop) to manually run [`flash_fp_mcu`], as long as they can disable [hardware write protect]. Obviously this only applies during development, not mass production. *** +<!-- mdformat on --> ## biod and timberslide @@ -187,10 +191,12 @@ Perform median analysis on the resulting image as described in the `MTS` document. The factory toolkit does this in [`fingerprint_mcu.py`][Checkerboard Test]. +<!-- mdformat off(b/139308852) --> *** note **TIP**: You can view the `.pnm` files generated by the commands below on your Linux desktop with ImageMagick: `display /path/to/file.pnm`. *** +<!-- mdformat on --> ##### Success/Failure @@ -461,10 +467,12 @@ To convert the images from FPC’s proprietary format to PNG, you will need to have `cros deploy`’d `libfputils-nocturne`, which will install the required utilities in `/opt/fpc`. +<!-- mdformat off(b/139308852) --> *** note **NOTE**: As of 2019-05-21, the `libfputils` library only works for the FPC 1145 sensor (in nocturne), not the FPC 1025 sensor (hatch). *** +<!-- mdformat on --> Convert the buffer in proprietary format into png: |