-
Notifications
You must be signed in to change notification settings - Fork 1
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
Having trouble reading 68681 registers #5
Comments
Are you using the socket console, or the stdout console ( |
I'm using the socket console, running a process with --console server |
I would expect this to work; what host are you running on? The console server is very generic Python/socket code, but there's always a possibility of something odd. I've only tested on macOS. Note that CRA/CRB are write-only; I would expect reading from them to return nothing useful. Most of the time, SRx.TXRDY/TXEMT should be set (and generally speaking you shouldn't be putting anything in TBx unless TXRDY is set...), so I'd focus on getting to that point first. If you haven't already, you might try turning on tracing ( |
That sounds promising. If you work out what's going on with WSL2 please share, since that would be worth fixing. |
Is there something I'm missing when trying to use the mc68681? I have no issue writing to it and get console output, but reading data from the recieve buffer always returns 0xff, and reading CRA and SRA always returns 0x00, and MR1A always returns 0x07.
The text was updated successfully, but these errors were encountered: