#StackBounty: #keyboard #serial-port PS/2 Keyboard via serial port

Bounty: 50

I’m trying to connect a PS/2 keyboard to a SuperMicro X7DBT-INF via its serial port and an adapter. I’ve tried using the
inputattach package, but this is really my first time working with serial and I haven’t been able to make any headway, and their man page doesn’t offer much for the uninitiated.

I’ve tried inputattach --daemon -ps2ser /dev/ttyS0 to no success. I’ve also tried manually setting the baud rate input attach --daemon --baud 115200 -ps2ser /dev/ttyS0 but it returns an invalid baud rate error (this is the base_baud I get from dmesg | grep tty)

Any suggestions of what to try? Or is it time to return those adapters and leave my home lab console with one keyboard for USB and another for PS/2?


Get this bounty!!!

#StackBounty: #ssh #serial-port SSH into Ubuntu over Serial port

Bounty: 50

I have connected to my Ubuntu box using its serial port on windows.

According to the question https://serverfault.com/questions/892892/how-to-use-ssh-over-serial-without-using-pppd-or-how-to-transfer-tcp-over-ser,
it appears I should be able to SSH into the machine over a serial port.

What packages are needed or alternatively how do I set this up?

http://patrickst.blogspot.com/2011/11/tcpip-over-slip-on-gnulinux-ubuntu.html


Get this bounty!!!

#StackBounty: #serial-port #citrix Serial port returning random errors on Wyse client

Bounty: 50

We are testing a newer Wyse client (Z90D7 model) that has a serial port connection to a PC. We have an external customer that uses a dedicated piece of equipment, however the PC is what we use for testing. We run a C# application on the clients via Citrix. When we run the application that we are using on our old Wyse equipment, everything runs fine with no errors. However, on the new equipment, the serial port works about once every 10 attempts. All of the other times, it will give me either an Overrun error, a Parity error, or an RXOver error.

I have verified through logging that the port does open and several commands execute after it opens. However, the random errors happen before any actual data can even be transmitted. I’ve read in numerous places that this could be a buffer issue, however I have not seen any posts mentioning errors happening before data is received so I’m not entirely sure.

I have also tried to use handshaking and larger read/write buffers with no luck. I have tried a new cable and the 2nd COM port on this device, no luck either. Our default settings are:

9600 baud, even parity, 8 data bits, 1 stop bit

Given that this is running on Citrix, we also have to run the net use commands shown here before anything is done. Not doing so will result in the serial connection always saying it’s connected and not receiving any data (this happens on the old equipment as well). The exact command we’re executing (with the app name changed, of course) is:

net use com1 /DELETE
net use com2 /DELETE
net use com1: \clientcom1:
net use com2: \clientcom2:
start /d "D:myapp" MyApplication.exe

Has anyone who has dealt with serial ports ever heard of these three errors alternating like this? Is there anything other than a faulty port (or two faulty ports, rather) that could cause this? I’m thinking that the hardware buffer size could be the issue, but can’t find any way to overcome this.


Get this bounty!!!

#StackBounty: #serial-port #protocols #reverse-engineering #i2c #spi Reverse-Engineering Protocol

Bounty: 50

I have a project I’m working on that involves the optical sensor from a mouse. I’ve got two communication pins (data and clock) isolated, but I don’t have datasheet and I’ve been bitbanging my head against a wall trying to figure this thing out. I finally got a decent capture of the protocol using my microcontroller – though it’s not perfectly in sync, the resolution should be high enough to identify what’s going on – each sample is taken, then followed by a ~4us delay

As I’m looking at this data plotted, I see the data line moving sometimes when the clock is not – and the data line appears to move much more consistently than the clock, leading me to believe that my assumptions about which is data and which is clock may have been backward. However, I also see the clock line moving when the data is not – which wouldn’t make any sense with my conjecture.

What I’m expecting to see in here – though I’m decreasingly confident that the protocol is set up this way – is some request for information on a specific registered, followed by a return of that information. Perhaps there’s a pairing or initialization at the very beginning of the communication as well (which is where this capture starts).

I would really appreciate some help figuring out what is happening here, because I’m fairly new to this – and entirely lost.

Data is found in CSV format here: https://pastebin.com/h9Hx1dyw

The first 50 lines are just raw pasted here because the website won’t let me ask my question without some code:

Time Index,Data,Clock
0,0,1
1,1,1
2,1,1
3,1,1
4,1,1
5,1,1
6,1,1
7,1,1
8,1,1
9,1,1
10,1,1
11,1,1
12,1,1
13,1,1
14,1,1
15,1,1
16,1,1
17,1,1
18,1,1
19,1,1
20,1,1
21,1,1
22,1,1
23,1,1
24,1,1
25,1,1
26,1,1
27,1,1
28,1,1
29,1,1
30,1,1
31,1,1
32,1,1
33,1,1
34,1,1
35,1,1
36,1,1
37,1,1
38,1,1
39,1,1
40,1,1
41,1,1
42,1,1
43,1,1
44,1,1
45,1,1
46,1,1
47,1,1
48,1,1
49,1,1
50,1,1


Get this bounty!!!