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

4nes4snes - player 4 not read #3

Open
Roet-Ivar opened this issue Jan 20, 2024 · 2 comments
Open

4nes4snes - player 4 not read #3

Roet-Ivar opened this issue Jan 20, 2024 · 2 comments

Comments

@Roet-Ivar
Copy link

Roet-Ivar commented Jan 20, 2024

When flashing the 4nes4snes.bin onto this ch552 port 1 - 3 works perfectly but port 4 is not read at all on p1.7.
Swapping port 3 and 4 gives the same result, port 3 (which confirmed working) is not read on p1.7.

I've also replicated this beviour in a second ch552, nothing on p1.7.

Any ideas what's up?
Thanks!

@ishiyakazuo
Copy link
Owner

Sorry, I got myself locked out of my Github account for awhile, finally got back in.
I haven't looked at this project for awhile, but I remember that there were some OS-specific quirks with how I was handling the USB endpoints. I'd test some things in Windows and it'd work, then I'd switch to Linux and it'd fail, and vice-versa. The AVR project this project was forked from did everything through one endpoint, which Windows was OK with but Linux didn't like, and I wanted to be able to use this with a Raspberry Pi, but it didn't work too well most of the time.
I guess I'd better ask -- how do you know there's nothing on P1.7? P1.7 should be an input from the controller.

@Roet-Ivar
Copy link
Author

Roet-Ivar commented Feb 4, 2025

Hi! As I remember correctly p1.7 should read the forth controller and it never did for some reason

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