> The firmware in M57-CANARY-73 should work.

To do the update, the infra team needs the version of a canary or
release build with the desired firmware that has passed BVT.
That is, we need a name like kevin-release/R58-9207.0.0.

@dbasehore please provide the requested info! 

Presumably the latest push we made for dogfood R56 beta channel would work. So:

kevin-release/R56-9000.73.0

This passed part of BVT at least, and we have plenty of people using it in the field.

Derek, can you confirm that's OK?

I'll confirm that's OK.

That works.

I picked a recent canary that was green instead of the beta build so that we won't be forced to move the stable image backwards (the image has to contain the firmware version, so needs to change).

Went from:
pprabhu@pprabhu:/work/chromiumos/chromite$ atest stable_version list | grep kevin
kevin/rwfw             | Google_Kevin.8785.122.0
kevin                  | R57-9135.0.0

to:
pprabhu@pprabhu:/work/chromiumos/chromite$ atest stable_version list | grep kevin
kevin/rwfw             | Google_Kevin.8785.135.0
kevin                  | R58-9221.0.0

Note: DUTs will move over to the new firmware as they are repaired...

> Note: DUTs will move over to the new firmware as they are repaired...

Actually, each DUT will move over to new firmware at the very next
test it runs.

how does a firmware update get triggered? do we need to do anything special for machines that are not in the lab (on our desk).

> how does a firmware update get triggered? do we
> need to do anything special for machines that are
> not in the lab (on our desk).

If your device isn't in the lab, you're on your own.
You have to manually run "chromeos-firmwareupdate" from a CrOS
image that has the firmware you want.

For the 'toolchain' DUTs in the lab, you can force the update
using 'verify'.