linuxboot / linuxboot/heads-wiki

T530/w530 disassembling/flashing notes

Open
#83 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
96
Forks
58
Avg merge
1d 16h
Merged PRs (30d)
11

Description

@eganonoa wrote : "Note: it can be tricky to properly read the 8MB chip on the T530 and W530 (see #996). This appears to be because the two chips share a power source on these boards (see generally). This is true for both the Rasbperry Pi and the CH431a. There appears to be two workarounds: (1) the Wake on Lan method (which has the one downside of only working once, because it is not supported by coreboot and is, therefore, not available after flashing); or (2) keeping the CMOS battery plugged in, which works also post-flashing. Both methods provide a little extra power to the board and appear to then be sufficient to get enough power to the 8MB chip to get a proper read of it. The Skulls team generally suggest using an external power source with the CH341a, and it's possible that this might help, but I have not tested."

From https://github.com/osresearch/heads/pull/1072#issue-1071482504

This needs to be documented properly

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the T530/W530 disassembly and flashing documentation in this wiki, then compare the quoted notes with Heads pull request #1072 and issue #996. Document the 8MB-chip read problem, the Wake-on-LAN and CMOS-battery workarounds, and the CH341a power guidance, distinguishing tested observations from untested possibilities.

Written by the indexing model from the issue text.

Assessment

Tech stack
raspberry-pi
Domain
documentation, embedded-iot
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.