Hmm, interesting. If @hasu's converter works with it, I guess it might be that the K-430 requires XT reset which is apparently required for old Type-1 IBM XTs and clones (just a guess, since Soarer's converter did not work at all)
There was a lot of info on the TMK, except where to buy one. I do obviously have Soarer's XT/AT converter, and could potentially flash new fw, but it would be nice to get one directly so as to not eff-up the one that I have. And I cannot seem to find specific info on how to flash it under Linux, which also would be required.
+1 on the arrow keys – wish they were the inverted T-shape. Also miss the delete-key. But the board is quite interesting in that I can ignore certain elements of it.
btw. is it common to have to captcha every message posted, even for registered users? I am getting the same unreadable characters on everything I attempt to post, be it PMs or messages (and the three questions)
Soarer's firmware also works with the XT reset line wired up, supposing that the protocol isn't too weird regardless. My DC-2014 requires it and I have run nothing but Soarer's firmware on a Pro Micro I glued into the case. Those prebuilt converters on Ebay usually don't have the reset line wired because very few keyboards actually need it.I got mine from TinkerBoy at eBay. I assume the XT reset line is wired, although I don't know for sure.
This should help (https://deskthority.net/viewtopic.php?f=7&t=8448) with both Linux terminal commands for flashing and wiring of your own Soarer's converter. That guide helped me a lot my first time around. Flashing instructions that work for Soarer's firmware should also apply to TMK, and vice versa. You could also be lazy and buy a DC-2014-specific Soarer's converter on Ebay and rewire it for your board. We still don't know whether or not either firmware will work though without some wizardry from hasu, unless you wanted to dive into TMK yourself. I know I haven't.Appreciate the link - definitely useful. Buying an existing converter would be my choice, but I am not sure if I have time to also rewire anything or dig too deep in order to get it working. I'll probably sell off the board instead and get something which works with an existing converter. (I have 4 other boards that I am refurbishing, which work with Soarer's AT/XT & PS/2 converters)
I think that either firmware could be remapped, so you could maybe make right shift an up arrow key on another layer or something, and change the existing up arrow to FN. It does have the delete key on the number pad at least. I'm quite fond of the F keys being on the left side of boards myself.The grouped F-keys on the left are a nice touch, yes. The main thing I am missing on this board, apart from – erm ;) – *actual XT-compatibility* (wish someone would update the Deskthority page as it is a little misleading) is the inverted-T arrows and light LEDs directly on the CL, NL & SL keys (or at least the CL), I've always preferred those...
I think the captcha goes away once you've reached a certain number of posts. I forget the number.
Soarer's firmware also works with the XT reset line wired up, supposing that the protocol isn't too weird regardless. My DC-2014 requires it and I have run nothing but Soarer's firmware on a Pro Micro I glued into the case. Those prebuilt converters on Ebay usually don't have the reset line wired because very few keyboards actually need it.I got mine from TinkerBoy at eBay. I assume the XT reset line is wired, although I don't know for sure.
This should help (https://deskthority.net/viewtopic.php?f=7&t=8448) with both Linux terminal commands for flashing and wiring of your own Soarer's converter. That guide helped me a lot my first time around. Flashing instructions that work for Soarer's firmware should also apply to TMK, and vice versa. You could also be lazy and buy a DC-2014-specific Soarer's converter on Ebay and rewire it for your board. We still don't know whether or not either firmware will work though without some wizardry from hasu, unless you wanted to dive into TMK yourself. I know I haven't.Appreciate the link - definitely useful. Buying an existing converter would be my choice, but I am not sure if I have time to also rewire anything or dig too deep in order to get it working. I'll probably sell off the board instead and get something which works with an existing converter. (I have 4 other boards that I am refurbishing, which work with Soarer's AT/XT & PS/2 converters)
I think that either firmware could be remapped, so you could maybe make right shift an up arrow key on another layer or something, and change the existing up arrow to FN. It does have the delete key on the number pad at least. I'm quite fond of the F keys being on the left side of boards myself.The grouped F-keys on the left are a nice touch, yes. The main thing I am missing on this board, apart from – erm ;) – *actual XT-compatibility* (wish someone would update the Deskthority page as it is a little misleading) is the inverted-T arrows and light LEDs directly on the CL, NL & SL keys (or at least the CL), I've always preferred those...
I think the captcha goes away once you've reached a certain number of posts. I forget the number.
I see. Sounds like there might be a (remote) chance that it could make a difference if the K-430 did actually use it. But probably not.Soarer's firmware also works with the XT reset line wired up, supposing that the protocol isn't too weird regardless. My DC-2014 requires it and I have run nothing but Soarer's firmware on a Pro Micro I glued into the case. Those prebuilt converters on Ebay usually don't have the reset line wired because very few keyboards actually need it.I got mine from TinkerBoy at eBay. I assume the XT reset line is wired, although I don't know for sure.
The IBM XT itself did not use the reset line, so it is unlikely that converter has run it. I have only heard of maybe 3 or 4 boards that did and I don't own any prebuilt converters. ¯\_(ツ)_/¯ The Deskthority wiki just says it uses the XT interface and nothing more.
This should help (https://deskthority.net/viewtopic.php?f=7&t=8448) with both Linux terminal commands for flashing and wiring of your own Soarer's converter. That guide helped me a lot my first time around. Flashing instructions that work for Soarer's firmware should also apply to TMK, and vice versa. You could also be lazy and buy a DC-2014-specific Soarer's converter on Ebay and rewire it for your board. We still don't know whether or not either firmware will work though without some wizardry from hasu, unless you wanted to dive into TMK yourself. I know I haven't.Appreciate the link - definitely useful. Buying an existing converter would be my choice, but I am not sure if I have time to also rewire anything or dig too deep in order to get it working. I'll probably sell off the board instead and get something which works with an existing converter. (I have 4 other boards that I am refurbishing, which work with Soarer's AT/XT & PS/2 converters)
I couldn't say that I blame you. I hope whoever gets it doesn't just rip the SKCM blues out of it and trash the rest.
The grouped F-keys on the left are a nice touch, yes. The main thing I am missing on this board, apart from – erm ;) – *actual XT-compatibility* (wish someone would update the Deskthority page as it is a little misleading) is the inverted-T arrows and light LEDs directly on the CL, NL & SL keys (or at least the CL), I've always preferred those...
Matias' keyboards have what you seek. (https://www.matias.ca/tactilepro/)Show Image(http://matias.ca/tactilepro4/viewer/1.jpg)
Unfortunately, the caps aren't the best things in the world and they no longer sell their "tactile pro" (they're actually their clickies) keyboards with a Windows layout. I have found that, at least with the mini boards, this is easy to tweak with desoldering and soldering some resistors on the controller, which Matias kindly prints a diagram for right on it. I'm also a fan of LED windows in the caps.
I see. Sounds like there might be a (remote) chance that it could make a difference if the K-430 did actually use it. But probably not.Soarer's firmware also works with the XT reset line wired up, supposing that the protocol isn't too weird regardless. My DC-2014 requires it and I have run nothing but Soarer's firmware on a Pro Micro I glued into the case. Those prebuilt converters on Ebay usually don't have the reset line wired because very few keyboards actually need it.I got mine from TinkerBoy at eBay. I assume the XT reset line is wired, although I don't know for sure.
The IBM XT itself did not use the reset line, so it is unlikely that converter has run it. I have only heard of maybe 3 or 4 boards that did and I don't own any prebuilt converters. ¯\_(ツ)_/¯ The Deskthority wiki just says it uses the XT interface and nothing more.
This should help (https://deskthority.net/viewtopic.php?f=7&t=8448) with both Linux terminal commands for flashing and wiring of your own Soarer's converter. That guide helped me a lot my first time around. Flashing instructions that work for Soarer's firmware should also apply to TMK, and vice versa. You could also be lazy and buy a DC-2014-specific Soarer's converter on Ebay and rewire it for your board. We still don't know whether or not either firmware will work though without some wizardry from hasu, unless you wanted to dive into TMK yourself. I know I haven't.Appreciate the link - definitely useful. Buying an existing converter would be my choice, but I am not sure if I have time to also rewire anything or dig too deep in order to get it working. I'll probably sell off the board instead and get something which works with an existing converter. (I have 4 other boards that I am refurbishing, which work with Soarer's AT/XT & PS/2 converters)
I couldn't say that I blame you. I hope whoever gets it doesn't just rip the SKCM blues out of it and trash the rest.
It would be a shame for sure.
A large part of my reason to keep the board was based on the work by another member here, @MandrewDavis, done on his K-430. (In the “Keyboard of the Month” thread – https://geekhack.org/index.php?topic=96478.0 (https://geekhack.org/index.php?topic=96478.0))
The grouped F-keys on the left are a nice touch, yes. The main thing I am missing on this board, apart from – erm ;) – *actual XT-compatibility* (wish someone would update the Deskthority page as it is a little misleading) is the inverted-T arrows and light LEDs directly on the CL, NL & SL keys (or at least the CL), I've always preferred those...
Matias' keyboards have what you seek. (https://www.matias.ca/tactilepro/)Show Image(http://matias.ca/tactilepro4/viewer/1.jpg)
Unfortunately, the caps aren't the best things in the world and they no longer sell their "tactile pro" (they're actually their clickies) keyboards with a Windows layout. I have found that, at least with the mini boards, this is easy to tweak with desoldering and soldering some resistors on the controller, which Matias kindly prints a diagram for right on it. I'm also a fan of LED windows in the caps.
Their "Tactile Pro" board is one I actually had been looking at earlier; but not too big a fan of the caps on those either.
We'll see how this turns out.
Maybe if I'm stubborn I decide to do something about the Copam after all... (maybe not a drop-in replacement for a converter but something not as time-consuming)
I see. Sounds like there might be a (remote) chance that it could make a difference if the K-430 did actually use it. But probably not.
If you worked with hasu in his TMK thread, I'm sure he could get it working.
It would be a shame for sure.
A large part of my reason to keep the board was based on the work by another member here, @MandrewDavis, done on his K-430. (In the “Keyboard of the Month” thread – https://geekhack.org/index.php?topic=96478.0 (https://geekhack.org/index.php?topic=96478.0))
You could ask him if he's got a PCB file for it and see about having one made.
Their "Tactile Pro" board is one I actually had been looking at earlier; but not too big a fan of the caps on those either.
We'll see how this turns out.
Maybe if I'm stubborn I decide to do something about the Copam after all... (maybe not a drop-in replacement for a converter but something not as time-consuming)
Good luck. I hope you get it working.
All good suggestions. I'll see if I can get a TMK converter working with it first. Thanks for your input. :thumb:
(Seems it was impossible for the board to notify on new replies btw. I enabled "For topics and boards I've requested notification on, notify me: immediately", but still no notification is sent.)
Hi hasu –Since the XT reset line seems to normally not be wired up, I assume there are some adverse affects if it is wired?Yes, reset line is critical for some XT keyboards and they don't work without reset line.
If your keyboad has reset line you will need its support on converter probably.
EDIT: I didn't know meaning of the word "adverse" and I think I read it in wrong way.
Your are right. I believe reset line support doesn't affect because most of keyboards don't have it.
The rest of XT and all of AT keyobards don't have reset line virtually, as the first post says at "Reset pin".
https://geekhack.org/index.php?topic=103648.0
Also check this.
https://github.com/tmk/tmk_keyboard/wiki/IBM-PC-XT-Keyboard-Protocol#keyboard-hard-reset
I found your thread for the Copam keyboard and subscribe it. You can post further info/question there instead of this thread.Sure, no problem. Thanks for subscribing to it. :)
https://geekhack.org/index.php?topic=111510.0
Also tried my second Soarer converter with a PS/2 plug and an AT/XT to PS/2 adapter, same result.It makes sense totally.
Thanks for posting pics.Sounds quite plausible what you write.
I guess the keyboard needs reset line support anyway.
But pic of whole the pcb and part surrounded with red line would be helpful to make sure.
The debug output shows the converter recognizes nothing from the keyboard.
These are likely reasons I would suspect:
1) Microcontroller U2 can not start properly without reset line.
2) Failure in keyboard hardware or connection between keyboard and converter(cable?)
Also tried my second Soarer converter with a PS/2 plug and an AT/XT to PS/2 adapter, same result.
It makes sense totally.
PS/2 converter doesn't reset line support and most of AT-PS/2 adapter cable in the market doesn't use reset line as well.
I would think unstable state of the microcontroller may cause behaviour of LEDs like that.
How do I find out what hid_listeb is saying
That is interesting – now I am wishing I had an XT keyboard to test with as well before hooking up the K-430. :thumb:
id_listen
Waiting for device:...
Listening:
wEE
remaining: FFFC
Keyboard ID: 0000
Code Set: 1
Mode: PC/XT
Waiting for new device:......
Listening:
TMK:e473e8ce/LUFA
USB configured.
Keyboard start.
I764 wFF A1801
ERR:11 ISR:0000 X2302
sudo hid_listen
Waiting for device:..........................
Listening:
TMK:e473e8ce/LUFA
USB configured.
Keyboard start.
I174 wFF A1212
ERR:11 ISR:0000 X1713
Pushed button on adapter to put it into firmware update mode
============================================================
martin@ciraxis ~/tmk_keyboard> sudo dmesg -T|tail
[Tue May 11 14:54:12 2021] elogind-daemon[1341]: Watching system buttons on /dev/input/event17 (t.m.k. IBM PC keyboard converter)
[Tue May 11 14:54:12 2021] elogind-daemon[1341]: Watching system buttons on /dev/input/event7 (t.m.k. IBM PC keyboard converter)
[Tue May 11 14:54:12 2021] elogind-daemon[1341]: Watching system buttons on /dev/input/event16 (t.m.k. IBM PC keyboard converter Consumer Control)
[Tue May 11 15:02:37 2021] usb 3-1.1: USB disconnect, device number 114
[Tue May 11 15:02:45 2021] usb 3-1.1: new full-speed USB device number 115 using ehci-pci
[Tue May 11 15:02:45 2021] usb 3-1.1: New USB device found, idVendor=03eb, idProduct=2ff4, bcdDevice= 0.00
[Tue May 11 15:02:45 2021] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Tue May 11 15:02:45 2021] usb 3-1.1: Product: ATm32U4DFU
[Tue May 11 15:02:45 2021] usb 3-1.1: Manufacturer: ATMEL
[Tue May 11 15:02:45 2021] usb 3-1.1: SerialNumber: 1.0.0
martin@ciraxis ~/tmk_keyboard> sudo dfu-programmer atmega32u4 erase --force
Erasing flash... Success
Checking memory from 0x0 to 0x6FFF... Empty.
martin@ciraxis ~/tmk_keyboard> sudo dfu-programmer atmega32u4 flash xt_usb_unimap.hex
Checking memory from 0x0 to 0x68FF... Empty.
0% 100% Programming 0x6900 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] Success
0% 100% Reading 0x7000 bytes...
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] Success
Validating... Success
0x6900 bytes written into 0x7000 bytes memory (93.75%).
martin@ciraxis ~/tmk_keyboard> sudo dfu-programmer atmega32u4 reset
martin@ciraxis ~/tmk_keyboard> sudo dmesg -T|tail
[Tue May 11 15:03:58 2021] usb 3-1.1: USB disconnect, device number 115
[Tue May 11 15:03:58 2021] usb 3-1.1: new full-speed USB device number 116 using ehci-pci
[Tue May 11 15:03:58 2021] usb 3-1.1: New USB device found, idVendor=feed, idProduct=6512, bcdDevice= 0.01
[Tue May 11 15:03:58 2021] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Tue May 11 15:03:58 2021] usb 3-1.1: Product: XT keyboard converter
[Tue May 11 15:03:58 2021] usb 3-1.1: Manufacturer: t.m.k.
[Tue May 11 15:03:58 2021] input: t.m.k. XT keyboard converter as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.1/3-1.1:1.0/0003:FEED:6512.00B3/input/input260
[Tue May 11 15:03:58 2021] hid-generic 0003:FEED:6512.00B3: input,hidraw4: USB HID v1.11 Keyboard [t.m.k. XT keyboard converter] on usb-0000:00:1d.0-1.1/input0
[Tue May 11 15:03:58 2021] input: t.m.k. XT keyboard converter as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.1/3-1.1:1.1/0003:FEED:6512.00B4/input/input261
[Tue May 11 15:03:58 2021] hid-generic 0003:FEED:6512.00B4: input,hidraw5: USB HID v1.11 Mouse [t.m.k. XT keyboard converter] on usb-0000:00:1d.0-1.1/input1
[Tue May 11 15:03:58 2021] input: t.m.k. XT keyboard converter System Control as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.1/3-1.1:1.2/0003:FEED:6512.00B5/input/input262
[Tue May 11 15:03:58 2021] input: t.m.k. XT keyboard converter Consumer Control as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.1/3-1.1:1.2/0003:FEED:6512.00B5/input/input263
[Tue May 11 15:03:58 2021] hid-generic 0003:FEED:6512.00B5: input,hidraw6: USB HID v1.11 Device [t.m.k. XT keyboard converter] on usb-0000:00:1d.0-1.1/input2
[Tue May 11 15:03:58 2021] hid-generic 0003:FEED:6512.00B6: hiddev0,hidraw7: USB HID v1.11 Device [t.m.k. XT keyboard converter] on usb-0000:00:1d.0-1.1/input3
[Tue May 11 15:03:58 2021] input: t.m.k. XT keyboard converter as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.1/3-1.1:1.4/0003:FEED:6512.00B7/input/input264
[Tue May 11 15:03:59 2021] hid-generic 0003:FEED:6512.00B7: input,hidraw8: USB HID v1.11 Keyboard [t.m.k. XT keyboard converter] on usb-0000:00:1d.0-1.1/input4
martin@meraxes ~ $ sudo hid_listen
Waiting for device:...................................
Listening:
Keyboard init.
[C]Keyboard start.
FF FF FF FF FF
Device disconnected.
Waiting for new device:..
Listening:
Keyboard init.
[C]Keyboard start.
FF FF FF FF
Device disconnected.
Waiting for new device:..
Listening:
Keyboard init.
[C]Keyboard start.
FF
Device disconnected.
Waiting for new device:.
Listening:
Keyboard init.
[C]Keyboard start.
Device disconnected.
Waiting for new device:.
Listening:
Keyboard init.
[C]Keyboard start.
FF
There was not much information to be obtained by hid_listen though. (Man, is this the world's weirdest keyboard or what?)
I repeatedly disconnected and reconnected it to the adapter, pressed all the keys, and reconnected the adapter to USB a couple of times as well.
btw. – is this the right firmware to put the adapter back into IBM AT/XT mode: https://github.com/tmk/tmk_keyboard/blob/master/converter/ibmpc_usb/binary/ibmpc_usb_atmega32u4.hexYes.
I ended up selling mine, but It was crazy that mine was doing something on hid_listen, but nobody else's was.
Waiting for device:
Listening:
60195 ERR:20 ISR:C000 e20
60723 ERR:20 ISR:C000 e20
Device disconnected.
Waiting for new device:......
Listening:
TMK:2a0471fd/LUFA
USB configured.
Keyboard start.
I739 A3741 wFF R R R R R R R R R R
4133 ERR:11 ISR:0000 X4634
Device disconnected.
Waiting for new device:...
Listening:
TMK:2a0471fd/LUFA
USB configured.
Keyboard start.
I427 A3428 wFF R R R R R R R R R R
3820 ERR:11 ISR:0000 X4321
Device disconnected.
Waiting for new device:...................................................................⏎
Thanks for supplying a newer firmware @hasu. I flashed the adapter now and notice it did provide a little more output.
The first entry is from connecting the keyboard to the adapter while the USB is already connected to the computer. The subsequent two are from disconnecting and reconnecting the USB adapter with the keyboard already hooked up.
Notice that the two are different.
One change is that now only Caps Lock can be toggled. (Before the Num Lock was available to be toggled as well.)
One change is that now only Caps Lock can be toggled. (Before the Num Lock was available to be toggled as well.)
what does this mean actually?
You can press CapsLock key on the keyboard and toggle its indicator?
Or just blink LED on startup and the key doesn't anything?
r58 wED rFA w04 rFA rF0 r58
The keyboard doesn't like startup command sequece of the firmware and stops working, perhaps. This is plain PS/2 converter firmware which doesn't issue any command at startup, this may show difference.
sudo hid_listen
Waiting for device:...........................................................................
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
Device disconnected.
Waiting for new device:....
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
Device disconnected.
Try this also. This is IBMPC converer firmware with 30sec wait before issueing commands. This shows something if the keyboard sends something. BAT code 'AA' is usually expected. Also try pressing some keys.
Connect keyboard with converter first and then plug into USB port when doing these tests.
Waiting for device:
Listening:
Device disconnected.
Waiting for new device:..................
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I449 A30451 wFF R R R R R R R R R R
30843 ERR:11 ISR:0000 X31344
Device disconnected.
Waiting for new device:....
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I589 A30590 wFF R R R R R R R R R R
30982 ERR:11 ISR:0000 X31483
Device disconnected.
Waiting for new device:...
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I613 A30615 wFF R R R R R R R R R R
31007 ERR:11 ISR:0000 X31509
Device disconnected.
Waiting for new device:........
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I544 A30545 wFF R R R R R R R R R R
30937 ERR:11 ISR:0000 X31439
Device disconnected.
Waiting for new device:.....................
[OVR]
36090 ERR:F0 ISR:FFC0 !FF! rFF
[OVR]
[OVR]
36090 ERR:F0 ISR:FFC0 !FF! rFF
[OVR]
43926 ERR:20 ISR:C000 [RST] I43927
43927 PRT:22 ISR:0000 e20
44025 ERR:20 ISR:C000 e20
44851 ERR:20 ISR:C000
44852 PRT:21 ISR:0000 rAA A44853 wFF rAA
44856 PRT:22 ISR:AAC0 X45358 rAA W45362 wF2 R R R R R R R R R R R46255
ID:FFFF(XT)
46255 ERR:11 ISR:AAC0 S46256 L46256 r1E r9E r1E r9E r1E r9E r1E r9E r10 r90 r10 r90 r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r11 r91 r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r03 r83 r03 r83 r04 r84 r04 r84 r05 r85 r05 r85 r05 r85 r06 r86 r06 r86 r06 r86 r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r0E r8E r0E r8E r0E r8E r0E r0E
142 PRT:23 ISR:0EE0 r0E
223 PRT:22 ISR:0EC0 r0E r0E r0E r0E r0E
704 ERR:20 ISR:0E80 [RST] I705
706 PRT:22 ISR:0000 e20
785 ERR:20 ISR:0E80 e20
865 ERR:20 ISR:0E80 e20
946 ERR:20 ISR:0E80 e20
1059 ERR:20 ISR:1D00 e20
1130 ERR:20 ISR:0F00 e20
1214 ERR:20 ISR:8E80 e20
1288 ERR:20 ISR:0E80 e20
1455 ERR:20 ISR:8E80 e20
1555 ERR:20 ISR:0E80 e20
2278 ERR:20 ISR:8E80 e20
2369 ERR:20 ISR:0E80 e20
2460 ERR:20 ISR:8E80 e20
2554 ERR:20 ISR:0E80 e20
2738 ERR:20 ISR:8E80 e20
2888 ERR:20 ISR:1E80 e20
2960 ERR:20 ISR:9E80 e20
3051 ERR:20 ISR:1E80 e20
3112 ERR:20 ISR:9E80 e20
3212 ERR:20 ISR:1E80 e20
3386 ERR:20 ISR:9E80 e20
3527 ERR:20 ISR:1180 e20
4162 ERR:20 ISR:9180 e20
4266 ERR:20 ISR:1180 e20
4338 ERR:20 ISR:9180 e20
4428 ERR:20 ISR:1180 e20
4765 ERR:20 ISR:9180 e20
4867 ERR:20 ISR:2080 e20
4959 ERR:20 ISR:A080 e20
5059 ERR:20 ISR:2080 e20
5110 ERR:20 ISR:A080 e20
5220 ERR:20 ISR:2080 e20
5739 ERR:20 ISR:A080 e20
5830 ERR:20 ISR:2480 e20
5921 ERR:20 ISR:A480 e20
5992 ERR:20 ISR:2480 e20
6098 ERR:20 ISR:A480 e20
6108 ERR:20 ISR:2480 e20
6188 ERR:20 ISR:1F80 e20 A30706 wFF R R R R R R R R R R
31098 ERR:11 ISR:0000 X31600
aaaaqqq33444555
r0E +2A d2A
r8E -2A u2A
r0E +2A d2A r8E -2A u2A
r0E +2A d2A
r8E -2A u2A
R05
r86
rC6
r86
rC6
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
R06 R06 R05
R06 R06 R05
r89
rC9
r89
rC9
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r82
rC2
r82
rC2
r87
rC7
r87
rC7
R06 R06 R06 R05
R06 R06 R06 R05
r88
rC8
r88
rC8
r88
rC8
R06 R05
R06 R05
R06 R05
R06 R05
r89
rC9
r89
rC9
r89
rC9
r89
rC9
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r8A
rCA
r8A
rCA
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r8B
rCB
r8B
rCB R06 R06 R06 R05
R06 R06 R05
r8B
rCB
r8B
rCB
r8B
rCB
r8B
rCB
r8E
rCE
r8E
rCE
r8E
rCE
R06 R05
R06 R05
R06 R05
R06 R05
r8F
rCF
r8F
rCF
r8F
rCF R06 R05
R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R05
R06 R06 R06 R05 R06 R05
r90
rD0 R06 R05
R06 R05
r91
rD1 R06 R05
R06 R05
R06 R05
R06 R05
r91
rD1
r91
rD1
r91
rD1
r91
rD1
R06 R05
r91 R06 R05
R06 R05 rD1
r91
R06 R05
rD1
R06 R05 r91
rD1 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r92
rD2 R06 R05
R06 R05
r92
rD2 R06 R05
R06 R05 R06 R05
R06 R05
R06 R05
R06 R05
r93
rD3
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05 r97
rD7 r96
r97 rD6
rD7
R06 R05
R06 R05 R06 R06 R06 R05
R06 R05 R06 R06 R05
R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
r97
rD7
R06 R06 R06 R05
R06 R06 R06 R05
r98
rD8
r98 rD8 r98
rD8
R06 R05
R06 R05 r9A
rDA r99
rD9 R06 R06 R05
R06 R06 R05
r9A R06 R06 R05
rDA R06 R06 R05 r9A R06 R06 R05
rDA R06 R06 R05
rA1
rE1
rA1
rE1
R06 R06 R05
R06 R06 R05
R06 R05
R06 R06 R05
rA0
rE0
rA0
rE0
R06 R05
R06 R05
R06 R05
R06 R05
r9F
rDF
r9F
rDF
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
r9E
rDE
r9E
rDE
R06 R05
R06 R05
R06 R05
R06 R05
r9D
rDD
r9D
rDD
r9D
rDD
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R05
r94
rD4
r94
rD4
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r81
rC1
r81
rC1
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r82
rC2
r82
rC2
r82
rC2
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r83
rC3
r83
rC3
r83
rC3
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r84
rC4
r84
rC4
r84
rC4
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r85
rC5
r85
rC5
r85
rC5
r85
rC5
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r86
rC6
r86
rC6
r86
rC6
r95
rD5
r95
rD5
r95
rD5
r95
rD5
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
rA3
rE3
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
rA3
rE3
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
rA4
rE4
rA4
rE4
rA4
rE4
rA4
rE4
r9B
rDB
r9B
rDB
r9B
rDB
r9B
rDB
rA5
rE5
rA5
rE5
rA5
rE5
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA6
rE6
rA6
rE6
rA6
rE6
rA6
rE6
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
rA7
rE7
rA7
rE7
rA7
rE7
rA7
rE7
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
rA8
rE8
rA8
rE8
rA8
rE8
rA8
rE8
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
rA9
rE9
rA9
rE9
rA9
rE9
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05 rA6
rE6
rA6
rE6
rA5
rE5
rA5
rE5
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r8D
rCD
r8D
rCD
r8D
rCD
r95
rD5
r95
rD5
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R05
r92
rD2
r92
rD2
r92
rD2
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA1
rE1
rA1
rE1
rA1
rE1
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA0
rE0
rA0
rE0
rA0
rE0
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r9F
rDF
r9F
rDF
r9F
rDF
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
R06 R06 R06 R06 R05
r9E
rDE
r9E
rDE
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r9D
rDD
r9D
rDD
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r94
rD4
r94
rD4
r94
rD4
R06 R05
R06 R05
R06 R05
R06 R05
r81
rC1
r81
rC1
r81
rC1
r81
rC1
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r82
rC2
r82
rC2
r82
rC2
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r83
rC3
r83
rC3
r83
rC3
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
r84
rC4
r84
rC4
r84
rC4
r84
rC4
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r85
rC5
r85
rC5
r85
rC5
r85
rC5
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R05
R06 R06 R05
r86
rC6
r86
rC6
r86
rC6
r95
rD5
r95
rD5
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r80
rC0
r80
rC0
r80
rC0
r80
rC0
r80
rC0
rA2
rE2
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA2
rE2
R06 R05
R06 R05
R06 R05
R06 R05
rA2
rE2 rA4
rE4
rA4
rE4
R06 R05
R06 R05
R06 R05
R06 R05
rA4
rE4
rA4
rE4
rA4
rE4
rA4
rE4
rA4
rE4
rA4
rE4
rA3
rE3
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
rA4
rE4
rA4
rE4
rA3
rE3
rA3
rE3
r9B
rDB
r9B
rDB
r9B
rDB
r9B
rDB
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
rA6
rE6
rA6
rE6
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA5
rE5
rA5
rE5
rA5
rE5
rA7
rE7
rA7
rE7
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
rA8 rE8
rA8
rE8
rA8
rE8
rA8
rE8
rA8
rE8
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
rA9
rE9
rA9
rE9
rA9
rE9
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05 rA6
rE6
rA6
rE6
rA5
rE5
rA5
rE5
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R06 R06 R05
R06 R05 R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
r9A
rDA
r9A
rDA
R06 R06 R05
R06 R06 R05
r9C
rDC
r9C
rDC
r9C
rDC
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
rA1
rE1
rA1
rE1
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
r9C
rDC
r9C
rDC
r9C
rDC
r9C
rDC
r90
rD0
R06 R06 R05
R06 R06 R05
R06 R06 R05
R06 R06 R05
> ¡Update! < ;D
I finally got myself another XT keyboard (actually, one that is AT/XT switchable and which I set to XT-mode, dubbed "8088" on the keyboard (the AT mode is identified as "80286" (not accurate, but the switching works.)
In any case, the results were extremely interesting (at least to me). I first tried @hasu's TMK adapter, with the most recent IBM PC firmware.
I connected the _other_ keyboard first (set to XT-mode), then plugged in the USB. Pressed a few keys, and disconnected. The disconnect is logged as:Code: [Select][OVR]
36090 ERR:F0 ISR:FFC0 !FF! rFF
[OVR]
in hid_listen.
I subsequently unplugged the DIN-connector (*leaving the USB-side connected*) and connected the Copam K-430.
Lo and behold – it not only produced codes with hid_listen, but *actual keys registered*. At least for a while, until I apparently hit too many keys, or the keyboard went into a reset state. (I thought it was the Scroll-Lock key that did this, but I am not sure.)
Code: [Select]I43927
43927 PRT:22 ISR:0000 e20
44025 ERR:20 ISR:C000 e20
44851 ERR:20 ISR:C000
44852 PRT:21 ISR:0000 rAA A44853 wFF rAA
44856 PRT:22 ISR:AAC0 X45358 rAA W45362 wF2 R R R R R R R R R R R46255
ID:FFFF(XT)
46255 ERR:11 ISR:AAC0 S46256 L46256 r1E r9E r1E r9E r1E r9E r1E r9E r10 r90 r10 r90 r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r11 r91 r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r03 r83 r03 r83 r04 r84 r04 r84 r05 r85 r05 r85 r05 r85 r06 r86 r06 r86 r06 r86 r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r0E r8E r0E r8E r0E r8E r0E r0E
142 PRT:23 ISR:0EE0 r0E
223 PRT:22 ISR:0EC0 r0E r0E r0E r0E r0E
704 ERR:20 ISR:0E80 [RST] I705
706 PRT:22 ISR:0000 e20
785 ERR:20 ISR:0E80 e20
The keys that registered (in my terminal) were:Code: [Select]aaaaqqq33444555
I also pressed some function keys and arrow keys.
[/code]
aaaaqqqqqwww<tab><tab><tab><tab><tab><tab><tab>qqqww2233444555<Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Backspace><Backspace><Backspace><Backspace>...
After the last error messages, the Copam stopped responding. I unplugged the TMK and re-tried with my Soarer.
With the Soarer I was able to test every key on the board multiple times – they _all_ register but curiously *do not* produce key events to the OS (i.e, no actual output as was seen – although briefly – with the TMK earlier!)
Output when using the Soarer adapter follows:
=============================Code: [Select]r0E +2A d2A
r8E -2A u2A
r0E +2A d2A r8E -2A u2A
r0E +2A d2A
r8E -2A u2A
R05
r86
rC6
r86
rC6
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
R06 R06 R05
R06 R06 R05
r89
rC9
r89
rC9
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
Again, this is me pressing every key from left-to-right about three times each, then repeating the cycle.
Hi @hasu - thanks for your reply!> ¡Update! < ;D
I finally got myself another XT keyboard (actually, one that is AT/XT switchable and which I set to XT-mode, dubbed "8088" on the keyboard (the AT mode is identified as "80286" (not accurate, but the switching works.)
I just want to confirm:
- Does the another XT keyboard work well with both Soarer's and TMK converter?
- What's model number and manufacturer of the keyboard?
In any case, the results were extremely interesting (at least to me). I first tried @hasu's TMK adapter, with the most recent IBM PC firmware.
I connected the _other_ keyboard first (set to XT-mode), then plugged in the USB. Pressed a few keys, and disconnected. The disconnect is logged as:Code: [Select][OVR]
36090 ERR:F0 ISR:FFC0 !FF! rFF
[OVR]
in hid_listen.
I subsequently unplugged the DIN-connector (*leaving the USB-side connected*) and connected the Copam K-430.
Lo and behold – it not only produced codes with hid_listen, but *actual keys registered*. At least for a while, until I apparently hit too many keys, or the keyboard went into a reset state. (I thought it was the Scroll-Lock key that did this, but I am not sure.)
I can't know why plugging and unplugging the antoher XT keyboard makes different result, because TMK converter just starts new keyboard-initializing process again when a keyobard is removed and new one is plugged.
Doesn't the converter work without the another XT keyboard? Posting debug log would be helpful.
Code: [Select]I43927
43927 PRT:22 ISR:0000 e20
44025 ERR:20 ISR:C000 e20
44851 ERR:20 ISR:C000
44852 PRT:21 ISR:0000 rAA A44853 wFF rAA
44856 PRT:22 ISR:AAC0 X45358 rAA W45362 wF2 R R R R R R R R R R R46255
ID:FFFF(XT)
46255 ERR:11 ISR:AAC0 S46256 L46256 r1E r9E r1E r9E r1E r9E r1E r9E r10 r90 r10 r90 r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r11 r91 r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r0F r8F r10 r90 r10 r90 r10 r90 r11 r91 r11 r91 r03 r83 r03 r83 r04 r84 r04 r84 r05 r85 r05 r85 r05 r85 r06 r86 r06 r86 r06 r86 r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4B rCB r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r4C rCC r0E r8E r0E r8E r0E r8E r0E r0E
142 PRT:23 ISR:0EE0 r0E
223 PRT:22 ISR:0EC0 r0E r0E r0E r0E r0E
704 ERR:20 ISR:0E80 [RST] I705
706 PRT:22 ISR:0000 e20
785 ERR:20 ISR:0E80 e20
The keys that registered (in my terminal) were:Code: [Select]aaaaqqq33444555
I also pressed some function keys and arrow keys.
Pressed keys in the log were recognized by the converter like below.Code: [Select]aaaaqqqqqwww<tab><tab><tab><tab><tab><tab><tab>qqqww2233444555<Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-4><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Keypad-5><Backspace><Backspace><Backspace><Backspace>...
And it seems the covnerter missed one of signals of Backspace and kept out of sync after that.
After the last error messages, the Copam stopped responding. I unplugged the TMK and re-tried with my Soarer.
With the Soarer I was able to test every key on the board multiple times – they _all_ register but curiously *do not* produce key events to the OS (i.e, no actual output as was seen – although briefly – with the TMK earlier!)
Output when using the Soarer adapter follows:
=============================Code: [Select]r0E +2A d2A
r8E -2A u2A
r0E +2A d2A r8E -2A u2A
r0E +2A d2A
r8E -2A u2A
R05
r86
rC6
r86
rC6
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
r8D
rCD
R06 R06 R05
R06 R06 R05
r89
rC9
r89
rC9
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R05
R06 R06 R05
Again, this is me pressing every key from left-to-right about three times each, then repeating the cycle.
It seems Soarer's converter received a few Backspace and lost sync after that as well as TMK.
R05 and R06 indicates timeout and start bit error respectively.
https://github.com/tmk/tmk_keyboard/wiki/Soarer's-Converter#error-codes
Do you remember what keys you pressed actually at very beginnig of the log?
The Copam does not work (so far) without the other keyboard having been connected first.
Which debug log do you mean btw.? – I posted pretty much all information I had. :)
hid_listen -h
Waiting for device:.⏎
hid_listen --help
Waiting for device:.⏎
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
Waiting for device:
Listening:
r56 'rD6 r36 r36 r56 *rD6 rB6
r29 <rA9 r36 r29 >rA9 rB6
./hid_listen.mac
Waiting for device:.......
Listening:
A6423 wFF R R R R R R R R R R
6815 ERR:11 ISR:0000 X7316
35259 ERR:20 ISR:C000
35259 PRT:22 ISR:0000 rFF W35260 w
Waiting for device:......
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
I175 A3176 wFF R R R R R R R R R R
3568 ERR:11 ISR:0000 X4069
17914 ERR:20 ISR:7000
34732 ERR:20 ISR:AA80
34870 ERR:20 ISR:1080
35802 ERR:20 ISR:9080
35929 ERR:20 ISR:1180
36659 ERR:20 ISR:9180
36786 ERR:20 ISR:1280
41529 ERR:20 ISR:9280
49596 ERR:20 ISR:E000
Tried the copam_44ee4f3f.hex firmware, but there was no change from before.
I haven't been able to reproduce the behaviour I saw yesterday.
The only thing I've noticed (with the working Nan-Tan keyboard) is that the TMK firmware appears to re-map the "<" key (to the right of the Left shift) as ' (tick). This only occurs when the keyboard is in XT mode. If it's in AT mode the mapping is correct.
btw. (and this is probably not useful), I believe when the Copam Keyboard actually output something I was able to toggle Scroll Lock. Now it does not register (only NumLock and CapsLock)
Not much luck today. Test B-Code: [Select]Waiting for device:......
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
I175 A3176 wFF R R R R R R R R R R
3568 ERR:11 ISR:0000 X4069
17914 ERR:20 ISR:7000
34732 ERR:20 ISR:AA80
34870 ERR:20 ISR:1080
35802 ERR:20 ISR:9080
35929 ERR:20 ISR:1180
36659 ERR:20 ISR:9180
36786 ERR:20 ISR:1280
41529 ERR:20 ISR:9280
49596 ERR:20 ISR:E000
The space in the output is when the NanTan was unplugged, and the Copam re-plugged. Nothing is printed, and nothing except the Caps Lock + Num Lock keys register.
It seems hid_listen on OSX is less verbose than Linux. I'd disregard the output from it. (It was just more convenient to use, as it's where I am typing from)
I re-flashed earlier firmware from June 10th, but the behaviour is the same.
Device disconnected.
Waiting for new device:.........
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I525 A30527 wFF R R R R R R R R R R
30919 ERR:11 ISR:0000 X31420
Waiting for device:.....
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
I525 A3526 wFF R R R R R R R R R R
3918 ERR:11 ISR:0000 X4419
Waiting for device:.........
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
500 PRT:22 ISR:AAC0 I501
501 PRT:22 ISR:0000 rAA A502 wFF R R R R R R R R R R
894 ERR:11 ISR:0000 X1395 rAA W1396 wF2 R R R R R R R R R R R2288
ID:FFFF(XT)
2289 ERR:11 ISR:AAC0 S2289 L2289 r10 r90 r11 r91 r12 r92
15703 ERR:20 ISR:C000 [RST] I15703
15704 PRT:22 ISR:0000 e20
15725 ERR:20 ISR:C000 e20 A
Waiting for new device:..........
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
I556
18294 ERR:20 ISR:C000 e20
18301 ERR:20 ISR:FF00 e20
18304 ERR:20 ISR:FC00 e20
18307 ERR:20 ISR:FF00 e20
18310 ERR:20 ISR:FE00 e20
18313 ERR:20 ISR:FE00 e20
18316 ERR:20 ISR:FF00 e20
18319 ERR:20 ISR:FC00 e20
18322 ERR:20 ISR:FC00 e20
18326 ERR:20 ISR:FE00 e20
18337 ERR:20 ISR:F800 e20
18341 ERR:20 ISR:F800 e20
18344 ERR:F0 ISR:FFC0
18345 PRT:22 ISR:0000 !FF! rFF A18346 wFF isr:FF00
18350 ERR:12 ISR:FF00 X18851
18852 PRT:10 ISR:EA90 rAA W18852 wF2 rFA rAB r83 R19358
ID:AB83(AT) S19358 wED rFA w00 rFA L19364 r15 rF0 r15 r1D rF0 r1D r24 rF0 r24
Waiting for device:.....
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
I525 A3526 wFF R R R R R R R R R R
3918 ERR:11 ISR:0000 X4419
Device disconnected.
Waiting for new device:........
Listening:
TMK:44ee4f/LUFA:d6a7df
USB configured.
Loop start.
I304 A3305 wFF R R R R R R R R R R
3697 ERR:11 ISR:0000 X4198
11993 ERR:20 ISR:E000
12123 ERR:20 ISR:F000
12124 PRT:23 ISR:0000 rFF W12124 wF2 rFA rAB r83 R12629
ID:AB83(AT)
12629 PRT:10 ISR:A0D0 S12630 wED rFA w00 rFA L12636 r15 rF0 r15 r1D rF0 r1D r24 rF0 r24
Waiting for device:...........
Listening:
TMK:f03668da+/LUFA
USB configured.
Keyboard start.
531 PRT:22 ISR:AAC0 I532
532 PRT:22 ISR:0000 rAA A533 wFF R R R R R R R R R R
925 ERR:11 ISR:0000 X1426 rAA W1427 wF2 R R R R R R R R R R R2319
ID:FFFF(XT)
2320 ERR:11 ISR:AAC0 S2320 L2320
(Sorry about the OSX output, it was only for the last two tests. I'm not going to use it again, and the machine which actually captured the output from the Copam was one of my Linux systems.)
In any case; I ran a multitude of tests (around 20) today hoping that I could again re-create the behaviour. Long story short, I could not. I am including the output again, as it was incomplete last time for the "A" & "B" tests.
After this I did the same tests with the Soarer, as well as two PS/2 to USB mouse+keyboard adapter dongles I had (one of which was reported to work by another member with the Copam). The one which worked best was my Aten branded one (it handled the "<" + ">" key correctly, which the generic adapter did not.https://geekhack.org/index.php?topic=111510.msg3074824#msg3074824
TMK:147575/LUFA:d6a7df
USB configured.
Loop start.
I558
620 PRT:10 ISR:AA90 rAA
624 PRT:22 ISR:AAC0 rAA A3559 wFF R R R R R R R R R R
3951 ERR:11 ISR:0000 X4452 rAA W4456 wF2 R R R R R R R R R R R5349
ID:FFFF(XT)
5349 ERR:11 ISR:AAC0 S5350 L5350 r1F r9F r20 rA0 r20 rA0 r20 rA0 r20 r1F rA0 r20 r9F rA0 r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r46 rC6 r46 rC6 r46 rC6 r46 rC6 r46 rC6 r46 rC6 r3A rBA r3A rBA r46 rC6 r3A rBA r46 rC6 r3A rBA
The key for PrintScrn is actually to the right of "9" on the NumPad (presumably activated via Shift+*). However, it only produces ⋅ (hid_listen: 36 r36 r37 ⋅rB7 rB6)
The "correct way" also does not work on the other adapters.
Interesting. Confirmed that Copam K-430 is AT/XT auto-switching finally.
First, the keyboard sends 'AA' intentionally with parity error on AT protocol and expects behaviour like below:
- AT host including normal PS/2 converters reply with 'FE' and the keyboard continues communication on AT protocol, I guess.
- XT host can recognize it as 'AA' ignoring preceding two redundant 0 pulses.
https://github.com/tmk/tmk_keyboard/wiki/IBM-PC-Keyboard-Converter#aa-with-prity-error
TMK converter doesn't detect the parity error and the keyboard switches to XT protocol immediately.
As for SysReq key it was introduced in IBM AT 84-key keyboard and didn't exists on IBM XT keyboard. The keyboard doesn't support the key in XT protocol unfortunately.
Maybe I'll fix my firmware for the parity error to support AT/XT auto-swithching keyboards later.
As for the Keypad* key, it is true on IBM PC/XT computer. PrintScreen function is handled by host when Shift and Keypad* are pressed. PrintSreen key doesn't exits in original IBM XT keyboard. Later, some of clone XT keyboards introduced PrintScreen key but Copam K-430 didn't. TMK converter doesn't handle the Shift and Keypad* combination because it is not good for key remap.
Microsoft documented about how PrintScreen key should behave on XT protocol(Scan Code Set 1), see Note 4 if you are interested.
https://web.archive.org/web/20201112031338/download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/scancode.doc
Can you try attached firmware and show me its debug log?Tried the updated firmware, but the keyboard behaves the same way unfortunately. I notice it does send a reset, which it didn't do before. I still comes up as an XT keyboard.
(Attachment Link)
I updated firmware and the converter detects parity error and tries recovery by sending a command now.
Copam K-430 will communicate with the converter on AT protocol now, instead of XT.
Waiting for new device:.......................
Listening:
TMK:86482d/LUFA:d6a7df
USB configured.
Loop start.
I717
718 ERR:01 ISR:AA90 [RST] I719
723 PRT:22 ISR:AAC0 rAA A3720 wFF R R R R R R R R R R
4201 ERR:11 ISR:0000 X4703 rAA W4707 wF2 R R R R R R R R R R R5689
ID:FFFF(XT)
5690 ERR:11 ISR:AAC0 S5690 L5690 r1E r9E r1E r9E r1F r9F r0E r8E r0E r8E r0E r8E r46 rC6 r46 rC6 r46 rC6 r46 rC6 r45 rC5 r45 rC5 r46 rC6 r46 rC6 r46 rC6 r46 rC6 r46 rC6 r46 rC6 r2A r2A r2A r2A r2A r2A r2A r37 rB7 rAA r2A r37 rB7 r37 rB7 r37 rB7 r37 rB7 rAA
Timing of sending command seems to be too late for the keyboard.Great, I'll try it and report back.
I fixed how to send 'reset' command.
(Attachment Link)
As for PrintScreen original IBM XT keyboard doesn't have 'dedicated' PrintScreen key while some enhanced XT keyboards has. The MS document explains about the 'dedicated' PrintSreen key. Copam doesn't have the 'dedicated' key and so you have to use Shift+Keypad* combo on XT computer. Note that the converter doesn't recognize the combo by design.Ok–I was a little unsure whether the converter should recognize Shift+* as PrintScrn in XT-mode, since it is apparently the only way to send PrintScrn via the keyboard when running in this mode.
The Copam K-430 through the converter works just as a modern USB keyboard. You will need AltGr, that is Right Alt for the char.(but I'm not sure, it depends on you keyboard layout on your OS.) You can remap a key for AltGr once firmware support the Copam keyboard.Yes, I guess I should clarify: I was wondering how this functionality was originally intended for this keyboard, being that many of the important keys are sub-legends normally activated via AltGr (which it, as we both noticed, does not have)
Waiting for new device:.
Listening:
TMK:56eb79/LUFA:d6a7df
USB configured.
Loop start.
I611
612 ERR:01 ISR:AA90 [RST] E612 A613 wFF rAA
616 PRT:22 ISR:AAC0 X1117 rAA W1121 wF2 R R R R R R R R R R R2103
ID:FFFF(XT)
2103 ERR:11 ISR:AAC0 S2104 L2104
r20 rA0 r20 rA0 r1F r9F r12 r92 r12 r92 r12 r92 r13 r93 r0E r8E r01 r81 r0E r0E r0E r0E r0E r8E r1C r9C r1C r9C r1C r9C r46 rC6 r46 rC6 r46 rC6 r46 rC6 r45 rC5 r45 rC5 r2A r37 rB7 r37 rB7 r37 rB7 r37 rB7 r37 rB7 r37 rB7 rAA r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r38 r2A r02 r82 r03 r83 r03 r83 r04 r84 r04 r84 r04 r84 r03 r83 rB8 rAA r3A r03 r83 r03 r83 r04 r84 rBA r3A r3A r3A r3A r3A r3A r3A r3A r2A r03 r83 r03 r83 r02 r82 r02 r82 r03 r83 r03 r83 rAA r2A rAA r04 r84 r38 r04 r84 r03 r83 rB8 rBA r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E r0E r8E
Waiting for new device:.....................................................................................
Listening:
TMK:111e8c/LUFA:d6a7df
USB configured.
Loop start.
I776
777 ERR:02 ISR:AA90 P778 wFE rAA r00AA e00 iEA90 E781 I781 A3782 wFF rFA
3785 PRT:10 ISR:FE90 rAA W4168 wF2 rFA R5171
ID:0000(AT_AT84) S5171 wED rFA w00 rFA L5178 r84 rF0 r84 r0E rF0 r0E r0E rF0 r0E r4A r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r4A r0E rF0 r0E r4A r0E rF0 r0E r0E rF0 r0E rF0 r4A r4A rF0 r4A r59 r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r59 r59 r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r59 r66 rF0 r66 r66 rF0 r66 r66 r66 r66 r66 r66 r66 r66 rF0 r66 r66 rF0 r66 r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r77 wED rFA w02 rFA rF0 r77 r77 rF0 r77 wED rFA w00 rFA r77 wED rFA w02 rFA rF0 r77 r77 rF0 r77 wED rFA w00 rFA r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E
Waiting for new device:.....................................................................................
Listening:
TMK:111e8c/LUFA:d6a7df
USB configured.
Loop start.
I776
777 ERR:02 ISR:AA90 P778 wFE rAA r00AA e00 iEA90 E781 I781 A3782 wFF rFA
3785 PRT:10 ISR:FE90 rAA W4168 wF2 rFA R5171
ID:0000(AT_AT84) S5171 wED rFA w00 rFA L5178 r84 rF0 r84 r0E rF0 r0E r0E rF0 r0E r4A r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r4A r0E rF0 r0E r4A r0E rF0 r0E r0E rF0 r0E rF0 r4A r4A rF0 r4A r59 r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r59 r59 r0E rF0 r0E r0E rF0 r0E r0E rF0 r0E rF0 r59 r66 rF0 r66 r66 rF0 r66 r66 r66 r66 r66 r66 r66 r66 rF0 r66 r66 rF0 r66 r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r77 wED rFA w02 rFA rF0 r77 r77 rF0 r77 wED rFA w00 rFA r77 wED rFA w02 rFA rF0 r77 r77 rF0 r77 wED rFA w00 rFA r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E r7E rF0 r7E
Hi @hasu,
Sorry for the late reply. I tested your updated firmware just now, and can report ––
that the Copam now speaks AT to your adapter. ;D
See debug output below. Also tested the SysRq key, which now behaves as PrintScrn (similar to the passive PS2-USB adapters). Also notice the Scroll Lock behavior is different – it does not come on (the LED), although the key is registered (also identical to the other AT adapters)
I guess one option is to sacrifice the right Shift key (and make the arrow-nav into an inverse T-nav and the leftmost arrow into AltGr, but it's not the prettiest, as there is neither an actual AltGr keycap, and since the stabilizer mounts for the R-Shift would be visible if the Up_arrow was placed there...)
Question: Is it possible to perhaps use the comination of L_Shift + Alt to function as an AltGr? Or does it need to be a dedicated key? (not sure how/if the firmware would allow this)
Just to clarify regarding the Scroll Lock, I mentioned it as it was different to running the keyboard in XT-mode with the TMK adapter on the same host. In XT-mode it lights up and can be toggled.Ah, OK. Yes, LED indcators are controlled by the keyboard In XT mode while by computer/OS in AT mode.
I'll keep thinking about what to do with the sub-legends (@, £, $, etc.) It seems peculiar, as there has to have been a way to type these on the keyboard “back in the day”, as several layouts have this issue.I think you can find something in vast documents hosted in bitsavers.org. Let us know if you find.
That being said, is there a guide on how to remap the keys – as in an editor for the .hex file which is programmed to the adapter? (hopefully something which works on Linux)