How to use Hasu's PS2 TMK on PS/2 with a pro micro?

[Wingklip]

Hey there Hasu controller fanboys and girls, as a fellow ancient junk collector I'm here asking if there is a way to flash Hasu's firmware onto a pro micro instead of Soarer's. From what I have seen, the Soarer's firmware does not work with a lot of keyboards but Hasu's on he other hand does.

I wired it the same way as one would wire up soarer's with 2 pullup resistors on data and clock at 1kR

Am I doing anything wrong? It does not work for me. Perhaps I need to pray for Hasu's presence within the converter

[pansku]

Mine actually doesn't work either. The locklights flash when I connect it and a keyboard appears in windows device manager, but then nothing happens. Maybe my omnikey draws way too much power? I measured VCC and GND and when it's connected its around 4.235v so waaay below 5v.

[Halvar]

TMK firmware is not a drop-in replacement for Soarer's converter!

Also, so far I haven't heard of any PS/2 keyboards where Soarer's converter does not work, but the TMK converter does.

@Wingklip: way too few information. What keyboard are you trying to convert, how did you configure the TMK software, how did you try to flash the Pro Micro? With TMK, you have to configure the pins that you are using before compiling.

@pansku: too much power consumption or a defect in the keyboard would be possible. Also, have you checked that the wiring fits the configuration of the software?

[pansku]

@Halvar

I double checked that Data is on PD0 and Clk is on PD1, tried changing pullups from 1k to 10k. The keyboard works perfectly fine when connected to the PS/2 port in my computer through my passive adapter. The solder joints for the headers don't have bridges either.

However the 2 big caps near the regulator are different in color and markings but both have the sequence 106 and the silksceen is a different shade too compared to my other pro micro I bought from the same brick and mortar store about a month earlier. Despite that the voltage when not connected to anything differs by less than 10mv between the 2 units so I don't think that would be the cause either.

Maybe I should try to add some decoupling caps to the breadboard?

The software is downloaded from the tmk-kbd site and it is rev1 for 32u4 like it's supposed to. I went with connections mentioned in this thread: https://geekhack.org/index.php?PHPSESSI ... ic=14618.0 and added the pullups mentioned in the github readme. As a sidenote the LED in the pro micro doesn't turn green like it does in my 4704 converter. Could it could be the software then?

[Wingklip]

Hasu's 4704 works perfectly for all intents and purposes, even though the first time I had a faulty pro micro. His ADB converter works perfectly too, but this ps2 converter in the same wiring as soarer's, does not work at all, even on ye olde model m

[jim121049]

If you're using a Pro Micro, make sure that J1 (in the upper left corner near the micro USB connector) is jumpered for 5V operation.

[hasu]

If you guys download firmware for rev.1 from tmk keymap editor it won't work with PD0/PD1 pin configuration.
http://www.tmk-kbd.com/tmk_keyboard/edi ... 2_usb_rev1
PS/2 converter rev.1(ATmega32u4) uses PD2/PD5 pins with USART engine, different configuration from rev.2. Refer to these files.
https://github.com/tmk/tmk_keyboard/blo ... .h#L65-L73
https://github.com/tmk/tmk_keyboard/blo ... e.rev1#L13

Meanwhile, rev.2(ATmega32u2) uses PD0/PD1 pins with interrupt method.

You will have to edit Makefile and config.h for your board and pin configuration to build your firmware.

[Wingklip]

If you guys download firmware for rev.1 from tmk keymap editor it won't work with PD0/PD1 pin configuration.
http://www.tmk-kbd.com/tmk_keyboard/edi ... 2_usb_rev1
PS/2 converter rev.1(ATmega32u4) uses PD2/PD5 pins with USART engine, different configuration from rev.2. Refer to these files.
https://github.com/tmk/tmk_keyboard/blo ... .h#L65-L73
https://github.com/tmk/tmk_keyboard/blo ... e.rev1#L13

Meanwhile, rev.2(ATmega32u2) uses PD0/PD1 pins with interrupt method.

You will have to edit Makefile and config.h for your board and pin configuration to build your firmware.

Thanks for clearing things up! I'll be sure to wire them properly this time. Also, does it have NKRO?

PS: Any plans on standardising the pins for the 32u4? You've already got the 4704 and the ADB pins in the same place :p

[hasu]

see this for NKRO.
https://github.com/tmk/tmk_keyboard/wik ... oesnt-work

No plan. At least until I decide to stop supporting exiistent rev.1 converter users.

[brentward]

Sorry to resurrect a dead thread but I am having the exact same issue: using a pro micro the lock lights flash then the keyboard dies. I tried switching to a Teensy 2.0 and had the same issue. I'm using rev2 but i specified the 34u4 as the MCU and I have data on PD0 and clock on PD1. Both have 1k pull ups on them. I'm trying to power a Model M. Both the Teensy 2.0 and the Pro Micro work perfectly fine as an ABD converter on an AEK II, so I don't think it is an issue with the controllers.

I'm currently using the Teensy 2.0 and interestingly I discovered that if I plug the Teensy into the computer without the keyboard attached and wait more than 3 second but less than 8 seconds and then plug in the PS2 to the Teensy it will power up fully and works perfectly... When I plug it in with the keyboard attached I periodically get messages that the USB device is using too much power and has been shut off (I'm on a Mac). I've also tried increasing the requested mA in the tmk-core/protocol/lufa/descriptor.c all the way up to 500 mA and that hasn't helped.

Why would it be doing this? It seems to have some kind of a surge of power usage while it is booting. Is there any way to put a delay of 5 seconds or so in the VCC giving power to the keyboard so the Teensy can boot before the keyboard tries to power up? I tried putting a sleep(5) in the main function in main.cpp before the keyboard_init() is called but that didn't help.

Any ideas?

[Wingklip]

Sorry to resurrect a dead thread but I am having the exact same issue: using a pro micro the lock lights flash then the keyboard dies. I tried switching to a Teensy 2.0 and had the same issue. I'm using rev2 but i specified the 34u4 as the MCU and I have data on PD0 and clock on PD1. Both have 1k pull ups on them. I'm trying to power a Model M. Both the Teensy 2.0 and the Pro Micro work perfectly fine as an ABD converter on an AEK II, so I don't think it is an issue with the controllers.

I'm currently using the Teensy 2.0 and interestingly I discovered that if I plug the Teensy into the computer without the keyboard attached and wait more than 3 second but less than 8 seconds and then plug in the PS2 to the Teensy it will power up fully and works perfectly... When I plug it in with the keyboard attached I periodically get messages that the USB device is using too much power and has been shut off (I'm on a Mac). I've also tried increasing the requested mA in the tmk-core/protocol/lufa/descriptor.c all the way up to 500 mA and that hasn't helped.

Why would it be doing this? It seems to have some kind of a surge of power usage while it is booting. Is there any way to put a delay of 5 seconds or so in the VCC giving power to the keyboard so the Teensy can boot before the keyboard tries to power up? I tried putting a sleep(5) in the main function in main.cpp before the keyboard_init() is called but that didn't help.

Any ideas?

I'm thinking you can use an inductor to prevent the bootup power surge from tripping the boot process on the pro micro.

I need to convert an IBM 5576 Keyboard with these pro micros for the IBM protocol, so it seems like there is no V1 variant in any of this.