-
-
Notifications
You must be signed in to change notification settings - Fork 55
Add google kano flashing guide #223
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
Draft
cwiggs
wants to merge
1
commit into
linuxboot:master
Choose a base branch
from
cwiggs:device-kano
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,77 @@ | ||
| --- | ||
| layout: default | ||
| title: Acer Chromebook Spin 714 (KANO) | ||
| permalink: /heads-flashing/ | ||
| nav_order: 1 | ||
| parent: Step 2 - Flashing Guides | ||
| grand_parent: Installing and configuring | ||
| --- | ||
|
|
||
| Acer Chromebook Spin 714 (KANO) | ||
| === | ||
|
|
||
|
|
||
| ## CCD with Suzyq cable | ||
| With Chromebooks there is an option called "Closed Case Debugging". A special usb cable called a SuzyQ cable | ||
| is required. A good guide on using the SuzyQ cable is | ||
| [MrChromebox](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html). | ||
|
|
||
|
|
||
| ### Disable Hardware Write Protection | ||
| The first thing you need to do is remove the battery of the laptop to disable hardware | ||
| write protection (but then we disable hardware write protection with the echo commands to /dev/ttyUSB0?) | ||
|
|
||
| TODO: insert images from https://github.com/linuxboot/heads/pull/2133 | ||
|
|
||
| Connect the USB-C end of the Suzy-Q cable to the CCD port on your ChromeOS device | ||
| (usually left USB-C port) and the USB-A end to your Linux device | ||
| Verify the cable is properly connected: | ||
|
|
||
| ``` | ||
| $ ls /dev/ttyUSB* | ||
| /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 | ||
| ``` | ||
|
|
||
| This command should return 3 items: ttyUSB0, ttyUSB1, and ttyUSB2. | ||
| If not, then your cable is connected to the wrong port or is upside down. | ||
| Adjust and repeat command until output is as expected. | ||
|
|
||
| TODO: Do we need to run `gsctool` from ChromeOS? I did not have to but maybe the previous owner of my Kano | ||
| device did it? [source](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html#step-1-enabling-closed-case-debugging-ccd) | ||
|
|
||
| Now we disable software write protection: | ||
|
|
||
| ``` | ||
| sudo -s | ||
| echo "wp false" > /dev/ttyUSB0 | ||
| echo "wp false atboot" > /dev/ttyUSB0 | ||
| echo "ccd reset factory" > /dev/ttyUSB0 | ||
| ``` | ||
|
|
||
| ## Extra step (What is this really doing?) | ||
| KANO requires an extra step before we flash with flashrom: | ||
|
|
||
| ``` | ||
| # Get the baud rate | ||
| $ sudo stty -F /dev/ttyUSB2 | ||
| speed 9600 baud; line = 0; | ||
|
|
||
| sudo minicom -D /dev/ttyUSB2 | ||
|
|
||
| run: apshutdown | ||
| wait 5s | ||
| run: gpioset en_S5_rails 1 | ||
| ``` | ||
|
|
||
| [source](https://forum.chrultrabook.com/t/flashrom-error-when-trying-to-unbrick-with-suzyq/8789/2?u=stonework5729) | ||
|
|
||
| ## Backup | ||
| TODO: add section about backing up rom first. | ||
|
|
||
| ## Flash heads | ||
|
|
||
| ``` | ||
| sudo flashrom --programmer raiden_debug_spi:target=AP,custom_rst=True \ | ||
| --chip "W25Q256JV_M" \ | ||
| --write heads-kano-202607081551-v0.2.1-3112-gb9dfd39.rom | ||
| ``` | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MrChromebox this is weird and we don't understand.
Even if IFD has all regions disabled per linuxboot/heads#2133 's linuxboot/heads@aece972
Heads flashprog -p internal still reports:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also Heads recovery shell
cbmem --console | grep '[DEBUG] ME'returns:So ME region still protected.