New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 658082 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
gwendal@chromium.org
█ dhend...@chromium.org
█ sha...@chromium.org
saintlou@google.com
adurbin@chromium.org
josa...@google.com
puneetster@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

"flashrom --wp-range" reports wrong values in PD firmware

Project Member Reported by hungte@chromium.org, Oct 21 2016 
Version: All PD firmware existing versions

What steps will reproduce the problem?
(1) flashrom -p ec:dev=1 --wp-range X X --wp-enable 
(2) reboot
(3) flashrom -p ec:dev=1 --wp-status

What is the expected output?
wp-range should be the value we've set

What do you see instead?
All zero (SRP=0x80)

Not sure if this was intended (see issue http://crosbug.com/p/58753#8).
David is wondering if PD code does not report the write-protected range correctly.
Project Member

Comment 1 by sheriffbot@chromium.org, Nov 4 2016 

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by hungte@chromium.org, Nov 4 2016

Status: WontFix (was: Untriaged)
The report value was not wrong. The problem is we have to schedule a ec reboot.
Solved in other issues.
►

Sign in to add a comment