Author Topic: Copam K-430 converter compatibility  (Read 3967 times)

0 Members and 1 Guest are viewing this topic.

Offline hasu

  • Posts: 3248
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: Copam K-430 converter compatibility
« Reply #50 on: Sun, 09 May 2021, 21:57:31 »
I believe the converters is not picky and just need a decent USB cable.
The cables will work for the converters if they can be used for the phone or other devices normally.
I guess the cause is not only the cables perhaps, USB  port, power supply, OS ...

The debug log indicates the K-430 doesn't send anything unfortunately.
With replugging the keyboard several times at various speed you can emulate the latemodel24's procedure somehow, perhaps.
I guess specific power cycles timing may casues something, but I can't find reasonable factor there so far.

Also, try this old firmware for XT support only, it may show different info on hid_listen.
https://github.com/tmk/tmk_keyboard/blob/6b71d88150f143b767b6ede7bd9008332d8ae181/converter/xt_usb/binary/xt_usb_unimap.hex


TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #51 on: Tue, 11 May 2021, 10:05:03 »
Flashed the adapter successfully from the IBM PC firmware to the XT –

Code: [Select]
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

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.

Code: [Select]
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

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.hex

Offline hasu

  • Posts: 3248
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: Copam K-430 converter compatibility
« Reply #52 on: Tue, 11 May 2021, 10:53:04 »
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.

The converter receives FF, it is not normal at all.
It seems to place pulse on clock line at least, but there is nothing on data line.

The keyboard is not completely dead but has hardware failure or something? I don't have idea.


Quote
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.hex
Yes.

TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #53 on: Tue, 11 May 2021, 11:01:25 »
It appeared to have received the FF signals when the plug was disconnected + reconnected to the adapter a couple of times. Tried this in order to “trick” it into XT-mode to minic what @latmodel24 saw with his board.

btw.- still haven't gotten a reply from @MandrewDavis (the third person I know who has this board, and who was quite technically proficient). He hasn't been on the board for quite a while, but would probably have some pointers as to how this thing works.

Hoping I won't have to introduce the board to my sledgehammer, but it seems more and more tempting as time goes by...! ;)

Spent quite some time restoring it (case and keys) as well...

Offline latemodel24

  • Posts: 17
Re: Copam K-430 converter compatibility
« Reply #54 on: Tue, 11 May 2021, 22:50:47 »
deleted
« Last Edit: Tue, 11 May 2021, 22:52:32 by latemodel24 »

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #55 on: Wed, 12 May 2021, 06:30:13 »
I ended up selling mine, but It was crazy that mine was doing something on hid_listen, but nobody else's was.

That I certainly can understand. Obviously one cannot rule out a malfunction with the board, but seeing that myself and the member who had a K-430 NOS (@MandrewDavis) saw identical behavior, it did at least seem weird.

I'm a little reluctant to put in on eBay but will reassess the options here. Maybe a kind soul with several Zenith boards wants to have it in his or her collection as a rarity item. ;-)

Offline svaya

  • Posts: 3
Re: Copam K-430 converter compatibility
« Reply #56 on: Fri, 14 May 2021, 07:00:28 »
I have the same keyboard and for me it works with an passive AT to ps2 connected to an active PS2 to USB converter.

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #57 on: Fri, 14 May 2021, 07:20:10 »
Interesting – which active PS/2 to USB converter are you using, @svaya?

Offline svaya

  • Posts: 3
Re: Copam K-430 converter compatibility
« Reply #58 on: Thu, 03 June 2021, 09:57:07 »
I tried it both with an active XT converter and a AT adapter, it only works with the AT adapter and active PS/2 converter.
I am using this generic ps2 converter
https://www.emag.ro/cablu-adaptor-usb-tata-la-2-conectori-ps2-lungime-31cm-caips2/pd/DFVGCGBBM/


Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #59 on: Sat, 05 June 2021, 13:47:00 »
Thanks for the extra info @svaya. Curious that it works with a combined mouse + keyboard adapter, and not the XT.

Do you remember how the keyboard behaved when using the active XT converter and AT adapter? (On mine I could only toggle the Caps Lock & Num Lock leds, and no info on hid_listen). My K-430 could obviously have some kind of defect though, but it seems it would be useful to try to connect it with a similar adapter as yours. Perhaps I can find one in my stash of old cables/converters.

Since an active XT adapter (do you know the type, btw.?) is more advanced – it certainly appears mighty strange that an *AT-to-PS/2 passive adapter* + a *PS/2-keyboard-and-mouse-to-USB-combo* adapter works better. But then again, things are not always logical... :)

Offline svaya

  • Posts: 3
Re: Copam K-430 converter compatibility
« Reply #60 on: Mon, 07 June 2021, 15:37:26 »
I used a PC/XT 5DIN keyboard to USB Soarer's Keyboard Converter, it flashed a bit the lights at the beginning and I could toggle Caps and Num, but couldn't type anything. I think there is a chance that your keyboard isn't dead. The ps2 to USB was a 1.5$ dollar cheap I think the transport was more than the cost of it. The fact that it has also the mouse usually tells that is active and not passive.

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #61 on: Mon, 07 June 2021, 16:49:28 »
That is pretty much the exact behaviour I am seeing also with my K-430 using both the Soarer XT/AT adapter and also @hasu's TMK IBMPC adapter; I'll try to get hold of an identical PS/2+mouse to USB combo converter as yours to test – probably off of eBay.

Thanks for the valuable input. :thumb:

Offline hasu

  • Posts: 3248
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: Copam K-430 converter compatibility
« Reply #62 on: Wed, 09 June 2021, 09:24:58 »
Drag0nFly,
I updated IBMPC converter firmware with some changes recently, this may show something helpful on debug output, perhaps. Try the latest firmware.
https://geekhack.org/index.php?topic=103648.msg3055384#msg3055384
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #63 on: Wed, 09 June 2021, 17:25:22 »
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.

Code: [Select]
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:...................................................................⏎

One change is that now only Caps Lock can be toggled. (Before the Num Lock was available to be toggled as well.)

Offline hasu

  • Posts: 3248
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: Copam K-430 converter compatibility
« Reply #64 on: Wed, 09 June 2021, 17:58:46 »
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.

No helpful info unfortunately. The keyboard doesn't seem to work in terms of converter.


Quote
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?

TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #65 on: Wed, 09 June 2021, 18:52:00 »

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?

I can press the CapsLock key on the keyboard and toggle its indicator. On prior firmware, and with the Soarer, I could toggle both the CapsLock and NumLock LED.

Offline hasu

  • Posts: 3248
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: Copam K-430 converter compatibility
« Reply #66 on: Wed, 09 June 2021, 19:35:55 »
Interesting.
That doesn't show anything on hid_listen? If not, the keyobard itself controls the indicator internally for some reason.

Indicators on normal AT or PS/2 keyboards are controled by command(wED) from host and hid_listen shows debug output like below.
Code: [Select]
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.
* ps2_usb_32u4.hex (63.76 kB - downloaded 5 times.)


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.
* ibmpc_usb_atmega32u4.hex (58.8 kB - downloaded 6 times.)

Connect keyboard with converter first and then plug into USB port when doing these tests.
« Last Edit: Wed, 09 June 2021, 19:38:36 by hasu »
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline Drag0nFly

  • Thread Starter
  • Posts: 35
Re: Copam K-430 converter compatibility
« Reply #67 on: Thu, 10 June 2021, 12:17:39 »

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.

Did not get anything from the ps/2 firmware unfortunately.
Code: [Select]
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.

Output from the IBMPC firmware with the added 30sec delay:

Code: [Select]
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:.....................

btw.-I can toggle all three LEDs. They seem to be affected by which state the keyboard is in. That is, I had to powercycle it a couple of times, and they behave consistently. Especially the NumLock can get "out-of-sync". Once the proper state is restored, all can be toggled.

Curiously, if one of the LEDs were not able to be toggled before the power-cycle, they also do not light up during initialization.

And again, no output from pressing other keys, and small variations in the output after each power cycle (each with a wFF, which seems to be hid_listen's way of saying "WTF") ;)
« Last Edit: Thu, 10 June 2021, 12:20:03 by Drag0nFly »