I have a problem with my KVM switch MASTER VIEW CS-104. Actually even when i turn it off (the power switch in front), the mouse port (for input to KVM) is still active - optical mouse red LED stil glows. When i connect HIDman to the KVM without a mouse input, everything seems normal and it works (of course with no mouse). When i connect the mouse - input from KVM, it stucks on boot. It passes the RAM check, but does not detect drives. Even the keyboard does not react to num lock switch (the led does not change the state).
Is that normal, that mouse input on KVM is always active? Another evidence of active mouse port is also that the HIDman stays turned on, when i turn off the KVM. It seems also, that the power of the PS/2 mouse port loops back through HIDman to the KB input port? Also this old school KVM does not work without 9V power supply.
Do you guys have any idea, if maybe this KVM is kinda faulty (it still works normal with regular ps/2 kb and mouse)??
Also i tried another KVM with HIDman (which is passive and does not have power supply input) - its an ATEN MASTER VIEW CS-14. It powers through the PS/2 ports, and than also powers on the HIDman and i t works good.
Okay, I tried another converter from dekuNukem - USB4VC and it works fine connected to my MASTER VIEW CS-104 KVM switch.
There must be something in conflict between Hidman and my KVM, that stucks at boot, when PS/2 mouse cable is connected. After RAM counter, it does not start detecting IDE drives - it freezes.
Okay, I tried another converter from dekuNukem - USB4VC and it works fine connected to my MASTER VIEW CS-104 KVM switch.
There must be something in conflict between Hidman and my KVM, that stucks at boot, when PS/2 mouse cable is connected. After RAM counter, it does not start detecting IDE drives - it freezes.
Can you send me some HID logs? Start the HID log, then plug in your KVM and watch the output. Then send me the resultant text
I have some news. As I said the problem occurs when HIDMAN is connected to KVM input (one PS/2 cable for KB and another for mouse). Also if only the keyboard PS/2 line is connected.
This is not USB KVM. It is old type of KVM (VGA, PS/2 mouse and keyboard, DIN 5 KB and RS232 serial mouse port). My PC is connected to the first output port (of four available) of the KVM.
When booting after the RAM counter, it does not start detecting IDE drives - it freezes. Actually I have just found out, if I press any key on KB a few times quickly, it continues to boot. Then it works and it detects KB and mouse in MS-DOS.
The keyboard I use is plain old normal Logitech USB from 2011 for 20 euros.
Okay, I tried another converter from dekuNukem - USB4VC and it works fine connected to my MASTER VIEW CS-104 KVM switch.
There must be something in conflict between Hidman and my KVM, that stucks at boot, when PS/2 mouse cable is connected. After RAM counter, it does not start detecting IDE drives - it freezes.
Can you send me some HID logs? Start the HID log, then plug in your KVM and watch the output. Then send me the resultant text
The problem is, that i can not record log. When i start logging data in text editor, and if i turn off KVM and turn it on again, I lose connection with HIDMAN, because HIDMAN is powered by KVM (HIDMAN is connected to KVM as input source of PS/2 keyboard and mouse). Well anyway i started HID log, but instead i disconnected and reconnected USB keyboard connected to hidman. I don't think if that helps... I got this:
yugokoralwrote on 2025-01-26, 00:00:I have some news. As I said the problem occurs when HIDMAN is connected to KVM input (one PS/2 cable for KB and another for mous […] Show full quote
I have some news. As I said the problem occurs when HIDMAN is connected to KVM input (one PS/2 cable for KB and another for mouse). Also if only the keyboard PS/2 line is connected.
This is not USB KVM. It is old type of KVM (VGA, PS/2 mouse and keyboard, DIN 5 KB and RS232 serial mouse port). My PC is connected to the first output port (of four available) of the KVM.
When booting after the RAM counter, it does not start detecting IDE drives - it freezes. Actually I have just found out, if I press any key on KB a few times quickly, it continues to boot. Then it works and it detects KB and mouse in MS-DOS.
The keyboard I use is plain old normal Logitech USB from 2011 for 20 euros.
Okay, I tried another converter from dekuNukem - USB4VC and it works fine connected to my MASTER VIEW CS-104 KVM switch.
There must be something in conflict between Hidman and my KVM, that stucks at boot, when PS/2 mouse cable is connected. After RAM counter, it does not start detecting IDE drives - it freezes.
Can you send me some HID logs? Start the HID log, then plug in your KVM and watch the output. Then send me the resultant text
The problem is, that i can not record log. When i start logging data in text editor, and if i turn off KVM and turn it on again, I lose connection with HIDMAN, because HIDMAN is powered by KVM (HIDMAN is connected to KVM as input source of PS/2 keyboard and mouse). Well anyway i started HID log, but instead i disconnected and reconnected USB keyboard connected to hidman. I don't think if that helps... I got this:
yugokoralwrote on 2025-01-26, 00:00:I have some news. As I said the problem occurs when HIDMAN is connected to KVM input (one PS/2 cable for KB and another for mous […] Show full quote
I have some news. As I said the problem occurs when HIDMAN is connected to KVM input (one PS/2 cable for KB and another for mouse). Also if only the keyboard PS/2 line is connected.
This is not USB KVM. It is old type of KVM (VGA, PS/2 mouse and keyboard, DIN 5 KB and RS232 serial mouse port). My PC is connected to the first output port (of four available) of the KVM.
When booting after the RAM counter, it does not start detecting IDE drives - it freezes. Actually I have just found out, if I press any key on KB a few times quickly, it continues to boot. Then it works and it detects KB and mouse in MS-DOS.
The keyboard I use is plain old normal Logitech USB from 2011 for 20 euros.
Can you send me some HID logs? Start the HID log, then plug in your KVM and watch the output. Then send me the resultant text
The problem is, that i can not record log. When i start logging data in text editor, and if i turn off KVM and turn it on again, I lose connection with HIDMAN, because HIDMAN is powered by KVM (HIDMAN is connected to KVM as input source of PS/2 keyboard and mouse). Well anyway i started HID log, but instead i disconnected and reconnected USB keyboard connected to hidman. I don't think if that helps... I got this:
Turn off keyboard error in bios. See if behaviour changes.
Guessing it's trying to detect, and sort of working.
I tried that and doesn't work. It works when it is connected directly to the PC. When it is connected through the KVM switch, something just breaks, and i have to press any key a few times. Maybe to detect keyboard again? Idk really.
I left it sitting and i started timer. The PC redetected keyboard after 5min and about 35 seconds, when i heard my floppy rumble and loaded all four (primary and secondary IDE) drives. Maybe that time means something?
I tried that and doesn't work. It works when it is connected directly to the PC. When it is connected through the KVM switch, something just breaks, and i have to press any key a few times. Maybe to detect keyboard again? Idk really.
I left it sitting and i started timer. The PC redetected keyboard after 5min and about 35 seconds, when i heard my floppy rumble and loaded all four (primary and secondary IDE) drives. Maybe that time means something?
OK I've decided to make a new rule. If you have a device that doesn't work with hidman, lend it to me for a week and I'll try my best to get it working.
You pay to ship it to me but I'll pay return shipping
I tried that and doesn't work. It works when it is connected directly to the PC. When it is connected through the KVM switch, something just breaks, and i have to press any key a few times. Maybe to detect keyboard again? Idk really.
I left it sitting and i started timer. The PC redetected keyboard after 5min and about 35 seconds, when i heard my floppy rumble and loaded all four (primary and secondary IDE) drives. Maybe that time means something?
OK I've decided to make a new rule. If you have a device that doesn't work with hidman, lend it to me for a week and I'll try my best to get it working.
You pay to ship it to me but I'll pay return shipping
I already had a plan to buy another one, if maybe my KVM is at fault (but probably that's not the case)... So I just found exactly the same one on ebay which is in UK. You live in UK, right? I will order it for you, but i will need your address. Maybe u can send me a PM? 😁
I already had a plan to buy another one, if maybe my KVM is at fault (but probably that's not the case)... So I just found exactly the same one on ebay which is in UK. You live in UK, right? I will order it for you, but i will need your address. Maybe u can send me a PM? 😁
I'm seeing the same issue as you, PC won't boot if it is selected while hidman is connected
you can workaround by making sure the PC isn't selected while it boots, but I'll hook a logic analyzer up and try to figure out what's going on
I already had a plan to buy another one, if maybe my KVM is at fault (but probably that's not the case)... So I just found exactly the same one on ebay which is in UK. You live in UK, right? I will order it for you, but i will need your address. Maybe u can send me a PM? 😁
OK what seems to be happening is hidman responds to the reset command far too quickly. Most keyboards send the BAT code (0xAA) after 300ms or so, hidman sends it immediately.
The attachment Screenshot 2025-02-05 154438.png is no longer available
I've added a delay of 500ms. This appears to make it boot on my computers.
The attachment Screenshot 2025-02-05 154353.png is no longer available
rasteriwrote on 2025-02-05, 15:39:OK what seems to be happening is hidman responds to the reset command far too quickly. Most keyboards send the BAT code (0xAA) a […] Show full quote
I already had a plan to buy another one, if maybe my KVM is at fault (but probably that's not the case)... So I just found exactly the same one on ebay which is in UK. You live in UK, right? I will order it for you, but i will need your address. Maybe u can send me a PM? 😁
OK what seems to be happening is hidman responds to the reset command far too quickly. Most keyboards send the BAT code (0xAA) after 300ms or so, hidman sends it immediately.
The attachment Screenshot 2025-02-05 154438.png is no longer available
I've added a delay of 500ms. This appears to make it boot on my computers.
The attachment Screenshot 2025-02-05 154353.png is no longer available
See if this firmware works for you :
Damn, it works! As you said. No issues! You're genius.
BTW. What type of analyzer do you use? Did you just cut one cable and put scope in between?
And, does this KVM you got, also has +5V present on mouse PS/2 input even if the switch is turned off? I was just thinking of putting diode on both ports on hidman, but i am affraid that the voltage drop of the diode (5V - 0,7V = 4,3V) will affect the hidman.
BTW. What type of analyzer do you use? Did you just cut one cable and put scope in between?
Cheap Saleae clone. Works great for low speed buses like PS/2. And yeah I have a wide variety of PS/2 debugging adapters I've built over the course of this project 😀
And, does this KVM you got, also has +5V present on mouse PS/2 input even if the switch is turned off? I was just thinking of putting diode on both ports on hidman, but i am affraid that the voltage drop of the diode (5V - 0,7V = 4,3V) will affect the hidman.
No, if I turn the power switch off then hidman turns off too. Does yours not do this?
What are you trying to do here? You really shouldn't connect HIDman directly to more than one PC
rasteriwrote on 2025-02-10, 14:47:Cheap Saleae clone. Works great for low speed buses like PS/2. And yeah I have a wide variety of PS/2 debugging adapters I've bu […] Show full quote
BTW. What type of analyzer do you use? Did you just cut one cable and put scope in between?
Cheap Saleae clone. Works great for low speed buses like PS/2. And yeah I have a wide variety of PS/2 debugging adapters I've built over the course of this project 😀
And, does this KVM you got, also has +5V present on mouse PS/2 input even if the switch is turned off? I was just thinking of putting diode on both ports on hidman, but i am affraid that the voltage drop of the diode (5V - 0,7V = 4,3V) will affect the hidman.
No, if I turn the power switch off then hidman turns off too. Does yours not do this?
What are you trying to do here? You really shouldn't connect HIDman directly to more than one PC
No no, let's make it clear - I am not connecting HIDman to two PCs. I Have my HIDman connected to my KVM - same as your. One ps2 cable for mouse and another ps2 cable for keyboard input. The problem is, that when i turn off the switch of my KVM, the HIDman is still ON - the blue LED is still on - so i realized, that the power comes from mouse "input" port from the back of the KVM. If i unplug that ps2 cable from KVM or from HIDman, the HIDman turns off. Maybe my KVM has some component damaged inside, maybe some diode? In case that your KVM completely cuts the power from PS2 ports, than I have a small problem. I will have to open my KVM and check.
When you decide to send me KVM back, I will pay you back for shipping, because I am happy that you solved my problem. If you need it for some more testing, it's not a problem.
Also i have one more issue, but it is firmware compiling related.
Last year i was trying to compile your source code on windows - no success.
Now i was trying to compile it in GIT - also no success.
Than i tried WSL on windows and on this WSL i have SDCC version 4.2.0 build #13081 and GNU MAKE version 4.3 installed. I somehow managed to get your source code compile and i got .bin and i got .hex file. I saw that my .hex file is approximately 1600 bytes less in size than your compiled .hex file. Also while in process of compiling I got bunch of strange warnings. Maybe this is related to final file size? How to get rid of this warnings? What is your process of compiling the code? Did i miss something?
The problem is, that when i turn off the switch of my KVM, the HIDman is still ON - the blue LED is still on - so i realized, that the power comes from mouse "input" port from the back of the KVM.
I'm sorry, I made a mistake - the keyboard PS/2 doesn't supply power when the power switch is on, but the MOUSE PS/2 port does. Weird!
Also i have one more issue, but it is firmware compiling related.
The warnings are unavoidable because of the way I'm using macros. Just ignore them.
I'm using SDCC 4.4.0, that probably explains the other differences.
I see SDCC 4.5.0 is out now, I should give that a shot
I'm sorry, I made a mistake - the keyboard PS/2 doesn't supply power when the power switch is on, but the MOUSE PS/2 port does. Weird!
Wow, that's unfortunate. In my case:
*KVM switch ON:*
- keyboard PS/2 power is on
- mouse PS/2 power is on
* KVM switch OFF:*
- keyboard PS/2 power is off
- mouse PS/2 power is STILL ON - what is unusuall >>
So i am getting backloop of power from mouse PS/2 through HIDman back to the keyboard PS/2 and the KVM still appears to be ON. I don't think that should be a big problem for hidman, but is really anoying.
The warnings are unavoidable because of the way I'm using macros. Just ignore them.
I'm using SDCC 4.4.0, that probably explains the other differences.
I see SDCC 4.5.0 is out now, I should give that a shot
Happy about warnings thing...
Are you using WSL (windows subsystem for linux), or are you using virtual machine? Or do you compile your firmware in bare windows CMD?
Because i was trying to install SDCC 4.5.0 in my WSL, and it still appeared as 4.2.0. I am a bit confused.
When I try to compile it in windows CMD or visual studio code terminal, I got bunch of errors 🙁
Are you using WSL (windows subsystem for linux), or are you using virtual machine? Or do you compile your firmware in bare windows CMD?
Because i was trying to install SDCC 4.5.0 in my WSL, and it still appeared as 4.2.0. I am a bit confused.
When I try to compile it in windows CMD or visual studio code terminal, I got bunch of errors 🙁
I normally compile in windows directly. I have some variety of GNU make installed in Windows, I forget exactly how I set it up.
I would keep trying WSL to be honest, probably you need to uninstall 4.2.0 or set the makefile to point at sdcc 4.5.0
