PS/2 Direction for the Commander X16

Announcements by the development team or forum staff.
paulscottrobson
Posts: 300
Joined: Tue Sep 22, 2020 6:43 pm

PS/2 Direction for the Commander X16

Post by paulscottrobson »



On 1/6/2022 at 8:00 PM, Wavicle said:




I think moving the PS/2 keyboard handling to a microcontroller is the right thing to do in this case.



Yes.

I don't know for the current design, but AFAIK the Vic20 and C64 do not use NMI - it appears to be connected to RESTORE. An NMI would not be suitable for keyboard polling per se perhaps, there may be some hardware accesses that it would mess up, but you could make it an IRQ with a pull up transistor or something. There are pretty stable i2c libraries and ps/2 setups for AVR chips, so it shouldn't be difficult to make what is effectively an i2c keyboard.

Wavicle
Posts: 277
Joined: Sun Feb 21, 2021 2:40 am

PS/2 Direction for the Commander X16

Post by Wavicle »



On 1/7/2022 at 2:17 AM, paulscottrobson said:




Well .... this board seems to have more microcontrollers than Digikey these days.



Hmm, off the top of my head, I can only think of the ATTiny and what looks like an STM32 on VERA. The ATTiny handles the ATX power sequencing and potentially the PS/2 keyboard and mouse. I'm not certain about the STM32 on VERA, but I think it is used for programming the FPGA's SPI flash so it isn't strictly necessary. Is there anything else?

BruceMcF
Posts: 1336
Joined: Fri Jul 03, 2020 4:27 am

PS/2 Direction for the Commander X16

Post by BruceMcF »



On 1/7/2022 at 12:45 PM, Wavicle said:




Hmm, off the top of my head, I can only think of the ATTiny and what looks like an STM32 on VERA. The ATTiny handles the ATX power sequencing and potentially the PS/2 keyboard and mouse. I'm not certain about the STM32 on VERA, but I think it is used for programming the FPGA's SPI flash so it isn't strictly necessary. Is there anything else?



Which of the chips do you reckon is an STM32?

X16v3.jpg.795b9c4100e43f24c2a2dc51579ef494.jpg

Wavicle
Posts: 277
Joined: Sun Feb 21, 2021 2:40 am

PS/2 Direction for the Commander X16

Post by Wavicle »



On 1/7/2022 at 3:16 PM, BruceMcF said:




Which of the chips do you reckon is an STM32?



 



Best guesses update below.

Wavicle
Posts: 277
Joined: Sun Feb 21, 2021 2:40 am

PS/2 Direction for the Commander X16

Post by Wavicle »


.

Wavicle
Posts: 277
Joined: Sun Feb 21, 2021 2:40 am

PS/2 Direction for the Commander X16

Post by Wavicle »


Grabbed a better still and updated my best guesses for VERA components:

image.thumb.png.07fdb5476ab85e7659c3779dd090663f.png

ZeroByte
Posts: 714
Joined: Wed Feb 10, 2021 2:40 pm

PS/2 Direction for the Commander X16

Post by ZeroByte »



On 1/6/2022 at 11:29 AM, Stefan said:




My guess is that the community is not interested in the keyboard solution per se. We just want it to become functional so that we can get on with what really interests us, eventually owning and using a X16.



I agree that the team should choose a proven design that is easy to implement.



@Wavicle, do you see any problem supporting both keyboard and mouse with the ATTINY + I2C solution?



More or less true for me, with the one exception being that I'd like the ability to send messages to the mouse so that Intellimouse mode support is possible, even if not via the Kernal.

User avatar
Cyber
Posts: 482
Joined: Mon Apr 27, 2020 7:36 am

PS/2 Direction for the Commander X16

Post by Cyber »


In Facebook group Lorin Milsap posted some info. Lorin is part of the extended X16 team but not in the core development team. In Facebook group Lorin has badges of Admin, Group expert and Founding member.


In Facebook group Lorin Milsap said:




Consider this as a semi official response.



As stated by others earlier yes there are 2 hurdles. The first is parts availability. This is highly affected by Covid and global supply chain issues. I won’t cover specifics, but many of the parts in short supply are the common logic chips.



The second issue is the PS/2 keyboard code. There is an updated routine which supposedly works, but none of the design team who has real hardware has had an opportunity to test the new code. Keep in mind by real hardware I mean complete machines that meet the current design criteria, not past revision boards. This actually circles back to the supply chain issues (yes it’s that bad). To my knowledge only 2 fully functional current boards exist, possibly a third, and no I do not even have one.



Quoted from here: https://www.facebook.com/groups/CommanderX16/posts/1087788681972225/

Post Reply