Repository navigation
Conversation
Measured on a V4 UniCorn (Core 12856) with a SanDisk 128 GB CF card: ID=0..2 write and read correctly at about the same speed, ID=3 writes corrupted blocks (SFS checksum error, same on every reread). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
A new hardware pitfall,
hardware/pitfalls/ide-speed-cf-write-corruption.md(the first file inhardware/pitfalls/).ApolloControl ID=3(IDESPEED "Fastest") corrupted writes to a CF card on the V4 IDE port: an SFS block written at ID=3 had a wrong checksum, and it stayed wrong on every reread at ID=2. With ID=0, 1 and 2, a 16 MB file was written and checked by SHA-256 on the V4 without errors, at about the same speed (write 2.7–2.9 s). So ID=3 gained nothing on this card.The advice is to measure each card (write, hash, reread at a lower level) before putting an IDE speed into the Startup-Sequence. Only one card was tested, and the file says so.
Found during
The ApolloOS R10 port, moving its work volume to a CF card with SFS (V4 UniCorn, Core 12856, SanDisk SDCFXS 128 GB).
Knowledge base files relied on
guides/testing-on-v4-hardware.md(ApolloControl, test setup)CONTRIBUTING.md(folder, frontmatter, evidence table)Local checks:
check_frontmatter,check_linksandcheck_saga_addressespass.🤖 Generated with Claude Code