cros_bundle_firmware: fix debug output problem

Verbose log output generated by cros-{bundle,write}-firmware utilities
does not include commands invoked through cros_build_lib.RunComand()
anymore - this method now prints into a log sent into /dev/null by
default, and reconfiguring log destination would be a non-trivial
change, requiring a much tighter integration with the chromite

Let's just print the command ourselves when required, as the rest of
debug printouts in these utilities.

Also added a comment in the ReadFileAndConca() docstring to pacify the
pre-upload check.

   verified that log generated with -v=4 includes the list of commands
   executed by tools.Tools.Run()

Change-Id: I818f04dd659c820bbe78539ed46859c9b813edd8
Signed-off-by: Vadim Bendebury <>
Reviewed-by: Simon Glass <>
1 file changed