diff options
| author | Vadim Bendebury <vbendeb@chromium.org> | 2016-02-19 16:34:56 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2016-02-23 12:19:38 -0800 |
| commit | 024a2447e9cc3897f567ef222e5613115cd0d720 (patch) | |
| tree | 4b64af6c05a213a310de6392faf204e3200e331a | |
| parent | 9f5782ba05dcf21e85e7c26e49df5630df38967b (diff) | |
| download | chrome-ec-024a2447e9cc3897f567ef222e5613115cd0d720.tar.gz | |
cr50: upgrade: fix debug messages to show address instead of offset
Debug messages generated by the firmware upgrade extension command
show flash offsets (the values used when calling flash API), but the
user is more interested in absolute addresses, as they are reported by
some other debug printouts.
Change fw_upgrade_command_handler() debug output to report absolute
flash addresses.
BRANCH=none
BUG=chrome-os-partner:37754
TEST=ran upgrade test, observed proper addresses reported:
fw_upgrade_command_handler: programming at address 0x84000
fw_upgrade_command_handler: programming at address 0x84400
...
Change-Id: I8a6cd6020e5ddcbf41f5931cf7632fc598d4745e
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/328810
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
| -rw-r--r-- | board/cr50/tpm2/upgrade.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/board/cr50/tpm2/upgrade.c b/board/cr50/tpm2/upgrade.c index 634c7fa9e4..dcc7acf631 100644 --- a/board/cr50/tpm2/upgrade.c +++ b/board/cr50/tpm2/upgrade.c @@ -161,7 +161,8 @@ static void fw_upgrade_command_handler(void *body, return; } - CPRINTF("%s: programming at offset 0x%x\n", __func__, block_offset); + CPRINTF("%s: programming at address 0x%x\n", __func__, + block_offset + CONFIG_PROGRAM_MEMORY_BASE); if (flash_physical_write(block_offset, body_size, cmd_body->block_body) != EC_SUCCESS) { *rv = UPGRADE_WRITE_FAILURE; |