mipidisaster / mipidisaster/mipiInk.Software
Issue with using same SPI bus for BOTH the SD card, and the eInk display
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Ran into this issue whilst trying to work on #3.
The wiring all is working correctly, however if the eInk display is connected the pico doesn't appear to be able to communicate with the SD card. However, removing the eInk connections (and nothing else), allows for the SD card to be read with no further issues.
It could be that I need some pull-up resistors?
Putting into the "Software" repo for now, until I determine if this is a hardware problem or not.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by reproducing the setup with both the SD card and eInk display connected, then inspect the embedded client’s shared SPI configuration and the wiring assumptions. Done means the Pico can communicate with the SD card while the eInk display remains connected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100