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

original logic analyzer traces #1

Open
Ashram56 opened this issue Feb 1, 2022 · 2 comments
Open

original logic analyzer traces #1

Ashram56 opened this issue Feb 1, 2022 · 2 comments

Comments

@Ashram56
Copy link

Ashram56 commented Feb 1, 2022

Good morning,

Would it be possible to get access to the original logic analyzer traces that were used to write this bridge ? I would be interested into it, as I'm really not a SW programmer, and reverse engineering from the Rust code, while certainly possible, would be a last resort (as I assume the information is available somewhere)

Regards

@jabdoa2
Copy link
Contributor

jabdoa2 commented Feb 1, 2022

Those would not be up to date with the current spike firmware. I guess the easiest way would be to capture new ones from an updated machine. One way (works on spike 1) is documented here: https://docs.missionpinball.org/en/latest/hardware/spike/troubleshooting.html#capturing-the-bus-traffic-of-your-game-using-interceptty

@Ashram56
Copy link
Author

Ashram56 commented Feb 1, 2022

Thank you for your prompt response

One point I'd like to clarify: the link you provided refer to shell commands (bash or otherwise), and I assume this is through the serial interface (as indicated in other sections of the link you provided) ? What is the speed/parity of this serial interface ?

Alternatively, I was going to connect a RS485 sniffer, but I would need some trial/error to determine the baud rate / parity of the original netbus

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

2 participants