Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using a RaSCSI board as a pi-parport device #40

Open
quorten opened this issue Oct 26, 2020 · 2 comments
Open

Investigate using a RaSCSI board as a pi-parport device #40

quorten opened this issue Oct 26, 2020 · 2 comments

Comments

@quorten
Copy link
Collaborator

quorten commented Oct 26, 2020

Investigate writing a Device Tree Overlay and building a DB25 rewiring dongle to allow using the RaSCSI board as a pi-parport parallel port interface.

https://github.com/akuker/RASCSI

Though it's a hack, passive SCSI bus termination (resistor-based) could be just good enough to get reliable communications with parallel port devices. Or it might require crude modifications to get sufficient termination behavior.

This could also address issue #4 since RaSCSI uses sequential BCM GPIO ordering for the data signals and (to the extent it matters) the control and status signals.

@quorten
Copy link
Collaborator Author

quorten commented Oct 26, 2020

The interesting thing about the RaSCSI project is that it is very similar to the v1 design of pi-parport. Personally I plan on using the RaSCSI board as a SCSI hard drive and I'll see if I can make it double as parallel port interface.

@quorten
Copy link
Collaborator Author

quorten commented Oct 27, 2020

We should have considered ourselves foolish not to realize this...

On pi-parport, if we connect A13, Y13, PERI_IN, and PERI_OUT rather than grounding the input and not using the output, api-parport board is also capable of being used as a RaSCSI board. However, you can only use it as exclusively an initiator or a target at a time, changing roles requires switching a DB25 rewiring dongle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant