-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asus_kgpe-d16: hardware write protection not works #67
Comments
The code used for testing was still in review and has changed before landing in |
I've built |
Work also with flashrom built from this branch |
This is based on information from: * commit a850fd0 - GD25LQ128C/GD25LQ128D/GD25LQ128E - GD25LQ64(B) - GD25Q127C/GD25Q128C - GD25Q256D/GD25Q256E - GD25Q64(B) * commit a8204dd - GD25Q32(B) * commit 7b4c4f3 - W25Q64BV/W25Q64CV/W25Q64FV * Dasharo/dasharo-issues#67 - W25Q128.V..M * Dasharo#8 - W25Q64.W Change-Id: I090188bad568885f78778e7fc7d8dbe20fb2445f Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com> Tested-by: Nikolai Artemiev <nartemiev@google.com> Tested-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com> Tested-by: Kamil Pokornicki <kamil.pokornicki@3mdeb.com> Tested-by: Przemyslaw Banasiak <przemyslaw.banasiak@3mdeb.com> Tested-by: Maciej Pijanowski <maciej.pijanowski@3mdeb.com> Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/68180 Reviewed-by: Anastasia Klimchuk <aklm@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Dasharo version
asus_kgpe-d16_v0.3.0
Dasharo variant
ASUS KGPE-D16
Affected component(s) or functionality
Write Protection Mechanism
Brief summary
Write Protection Mechanism does not work on the platform ASUS KGPE-D16 with 16MB flash chip.
How reproducible
Always
How to reproduce
Steps to reproduce the behavior:
Expected behavior
Hardware Write protection works on ASUS KGPE-D16 with 16MB flash chip.
Actual behavior
Hardware Write protection does not work on ASUS KGPE-D16 with 16MB flash chip.
Screenshots
Additional context
Solutions you've tried
The text was updated successfully, but these errors were encountered: