-
Notifications
You must be signed in to change notification settings - Fork 4
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
A600 Pins #23
Comments
For reference: Use https://amigapcb.org to confirm any or all signals before attaching. The rev 2A is extremely similar to the 1.5. |
I checked all pins on this website, seems fine. |
What I did not try is : |
Hello again.
This is possible, yes; the keyboard aspect is not mandatory, and as a result, you do not need to internally mount it if you just want the controller port access. Joystick emulation hasn't been finished, and I have smatterings sitting in a git repository on my dev machine; I've been focussing on full-HID support for the mouse for a while and haven't yet finished that but it's closest to release. What I'm saying is, mouse support is the only thing other than keyboard right now 😄
It's worth checking that the USB keyboard has been picked up and that there's not some sort of issue. If you have a 3.3V serial adapter (FTDI or similar), then pins 1 & 2 on the pico provide serial, and by default, unless you've edited If you've built one of my PCBs, then the serial pins are marked on IDC connector J2. Another good indicator is turning on caps lock; if the LED illuminates, it indicates that the firmware is talking to the keyboard, and caps lock is triggered via command in the event loop. If you want to increase the startup pause, look in Out of interest, have you customised anything in |
Hello,
I had no problem attaching the device to my A500, but the A600 is not so easy.
SMD soldering is no problem for me, but before I destroy the A600, where exactly do I need to solder the wires to ? A picture would be great, but if not possible, please give me a hint. My board is a rev 1.5, if you need this information.
The text was updated successfully, but these errors were encountered: