We welcome retro users & hardware gurus alike! Come and join the party :)
https://www.exxosforum.co.uk/forum/
@arkadiusz.makarenkoarkadiusz.makarenko wrote: 30 Oct 2023 17:43 As of mouse support I will add this to my todo list for this firmware, I am a little bit snowed in at work just now, but winters are long in Scotland.
NYYRIKKI wrote: 07 Nov 2023 02:27@arkadiusz.makarenkoarkadiusz.makarenko wrote: 30 Oct 2023 17:43 As of mouse support I will add this to my todo list for this firmware, I am a little bit snowed in at work just now, but winters are long in Scotland.
Yes, now that we got the keyboard working, we can start talking about the mouse support. :)
I did enhance the keyboard test one more time before I posted it on msx.org forums. In there someone pointed me that there is also another keyboard test program, but unfortunately I could not get it to run. :( In theory it might be interesting to you as it has also mouse test, but currently some more info is needed. The discussion is here:
https://www.msx.org/forum/msx-talk/hard ... ard-tester
While talking about MSX-mouse, one thing to keep in mind is that it is quite a low resolution device compared to modern mice (75dpi or so (?)) This means you need to implement some floating point/fixed point arithmetics in coordinate conversion to make it move smoothly. It should not be a big issue as long as you keep the resolution difference in mind from the start.
In theory MSX mouse is pretty simple device. It has two buttons, that work exactly like in joystick and beside that you only need to transfer X & Y deltas... Modern USB-mice are anyway more complex and have advanced features like scroll-wheel and extra buttons, that you may want to take into consideration.
If you just implement the basic mouse features (2 buttons & directions), it is more than enough... How ever, if you look the protocol specs that I posted all the way down, you will see that we enhanced the protocol to handle also these new features. I was personally involved making the new specs, but especially if you are worried about implementing useless features, I think you can more than safely skip this part... In theory, it sure is nice to scroll ie. Notepad window in SymbOS with scroll wheel same way as in Windows, but practically SymbOS is the only use case that even supports such things, and you can easily live without such features.
I did implement the enhanced protocol when I made PS/2 -> MSX mouse adapter on Arduino, but I also implemented another mode, where I can seamlessly adjust the mouse sensitivity/resolution with the wheel... And if you ask me now, what I use? It is running always in mode where I can adjust the sensitivity on the fly instead of having the scroll-functionality.
On MSX both X and Y are signed chars. (-128 to 127)arkadiusz.makarenko wrote: 07 Nov 2023 07:43 At this point I am still stuck on hardware protocol itself related to sending directions.
Code: Select all
- wait until joypin 8 = Low
- send X data bits 4-7 to Joypins 1-4
- wait until joypin 8 = High
- send X data bits 0-3 to Joypins 1-4
- set x to 0
- wait until joypin 8 = Low
- send -Y data bits 4-7 to Joypins 1-4
- wait until joypin 8 = High
- send -Y data bits 0-3 to Joypins 1-4
- sey y to 0
Since I managed to run even 57600 bps RS232 trough the port, I'm pretty sure you have implemented the joystick port correctly. (I used pins 1 & 6 only though) Now I don't remember if I actually tried mouse or not. In MSX pins 1, 2, 3 and 4 are input only. Pins 6, 7 ("button pins") can be configured as input or output and pin 8 is output only (pin8 in joystick mode is used as GND = If this pin is high, no value from joystick directions is returned.)arkadiusz.makarenko wrote: 08 Nov 2023 10:23 @terriblefire
I think because how pin 8 is used we might not be able to support mouse with current CPLD firmware?
Code: Select all
10 screen 1:sprite$(0)="0HH0":fori=0to1:r=pad(12):x=(x+pad(13))and255:y=(y+pad(14))and255:put sprite 0,(x,y),8:i=-strig(1):NEXT