Manual testing can be performed with basic peripherals: You can do a lot of manual testing on Amigas using basic peripherals - however, specialist hardware and software can be extremely useful for thorough testing. This was the case for my Commodore Amiga computers (i.e. For a lot of mainstream kit (such as the Commodore 64), diagnostic hardware and software is quite readily available to buy - however, this is not the case for all machines, so often it's necessary to make your own. However, this can often be both difficult to do (due to requiring proprietary or obsolete hardware or software) and difficult to document/prove for posterity or to a potential buyer (usually through pictures and videos).Īs such, I'm always on the lookout for methods of making this process easier and more effective, for all of the systems that I work on. it boots), that doesn't necessarily mean that it works properly. Is there anything that could be blocking their receive that I haven't tried? Once again, I'm assuming something is configured differently since the first port has expected behavior (other than the auto loopback I didn't expect), but I haven't found any rules applied to any of the ports.I like to test all of the vintage computers that I restore as thoroughly as possible, because thorough testing is necessary to verify correct operation - electronic devices are complex systems with lots of functionality and components, so just because something looks like it works (i.e. I'm not sure why that would happen.Īfter testing the other ports that were showing 0 on transmit and receive, I noticed that I actually am seeing the transmit value increase, but they are unable to receive. So, I can cat that file any time before I run the python script, as many times as I want, but immediately after I run that Python, I can't cat the file, it just immediately returns with nothing. There's a few more serial ports, but they all have 0 tx and rx, and on port 03F8, the tx and tx increase when I send to the serial port ttyS0Īnother problem/symptom that could be related is that after I run the python script, I'm no longer able to cat /dev/ttys0 There is no change to this output when the echo command to the port is running with or without the cable connected.Ĭheck that the transmit and receive numbers change Output: /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4ĬTS and similar pins change when signal applied If I run without sudo I get a blank line returned Output: Error I will have to copy in later. Output: crw-rw-, 1 user group 4, Date /dev/ttyS0 Like I said, I get the expected output from both tests, but I get the same output whether the cable is connected or not.Ĭhecking if interface is really a character device The same thing happens when I use the much shorter and simple serial test shown below Ser = serial.Serial(COM_PORT, BAUD_RATE, timeout=1, parity=serial.PARITY_NONE, rtscts=False, dsrdtr=False) In case it's useful information I'm using pySerial shown below (I had to type some of it from memory so I apologize if there are errors, but my question isn't about the code as much as it is how these ports actually work) import serial Is there some kind of software loopback that already exists for ports in Linux? I have something in python that tests the port, but I've found that the program returns the expected values even when my loopback isn't attached. I'm new to using serial ports, and I have a loopback cable for serial on a Centos 7 machine.
0 Comments
Leave a Reply. |