a2stuff / a2stuff/prodos-drivers
DClock: test for presence of Slinky
Nobody has claimed this yet.
- Dominant language
- Assembly
- Stars
- 37
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Driver should test for the presence of a slinky-style RAM card before attempting to unlock and read the time. The clock hardware is required to be installed onto a //c expansion RAM card to function. @qkumba suggested the following "take the value from DATA, increment, write it back, check if the new value is there". I unfortunately don't have a DClock to test, but the DClock module is occasionally triggered instead of my Cricket (Cricket is further down the jumbo chain).
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
Start by locating the DClock module and its DATA access, then review where it unlocks and reads the time. Use the suggested DATA increment/write-back/check approach to determine whether the slinky-style RAM card is present before the clock is triggered. Done means DClock does not claim the chain when its required expansion RAM card is absent, preserving access to Cricket.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100