SPI programmer recommendation
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
I'm sure [your SPI programmer](https://trmm.net/SPI) works great, but for those who do not happen to have a teensy on hand and would end up buying some hardware to flash things anyway, I would recommend picking up a CH341A-based ([datasheet](http://www.datasheetspdf.com/datasheet/CH341A.html)) programmer. These:
- can read & write common SPI & I2C EEPROMs
- can be acquired for ~$3 USD including taxes and shipping (!) [on ebay](http://www.ebay.com/sch/i.html?_nkw=CH341A)
- have a [working open source driver](https://github.com/setarcos/ch341prog) to interface with them
- are decently fast: writes my 8mb ME region in ~100 seconds, reads it in ~60s, erases it in ~25s
SOIC8 clips can also be acquired (w/ tax & shipping!) for about $3 USD [on ebay](http://www.ebay.com/sch/i.html?_nkw=SOIC8+clip).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked SPI programmer recommendation, CH341A datasheet, ch341prog driver, and SOIC8 clip references first. Clarify where this hardware guidance belongs and what project documentation should be updated; done means the recommendation is incorporated in an agreed location with accurate links and usage context.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100