Can you give more details? Not sure which team needs to do this work? 

ideally infra team needs to do that.  Otherwise we can manually on individual DUT to setup the servo with keyboard map.

For chromeboxes, we traditionally require to use a serial cable to simulate the keyboard.  With the key code programmed into the servo, the serial cable is no longer needed. (see go/fwkeyboard for detail)

I manually scheduled the test firmware_FlashServoKeyboardMap to install the new keyboard map to servo for the pool:faft-test. Doing once is fine. As the number of machines in pool:faft-test is not too many, manual work is doable.

I think this request is to do it on all the servos in lab. In case, some servo in pool:faft-test may be swapped to one with old keyboard map, FAFT will fail. So updating all servos to the new keyboard map can prevent this issue.

Can you describe the work needed in more detail (which units, process that needs to be taken, etc)

danny, assigning back to you to get more info on the workflow needed, you can unassing once that's done

- the keyboard map is needed for FAFT tests
- the test firmware_FlashServoKeyboardMap can be executed manually to install keyboard maps on the servo.  This is a one time operation and the keyboard maps does not effect device running non-FAFT tests.
- waihong already execute the test on servo running FAFT in lab.

Let close this for now and use the manual update procedure.