He doesn't mention it's a RS485 I/O card meant to fit into an CEC expansion box in a Z14 mainframe. Might be helpful terms to search if you're looking to find very similar parts...since there might be run on this one specifically. Found part number 98Y6848 looking this way, which seems like an updated (or maybe just renumbered) version of this.
RS-485 is pretty much the standard to communicate with SDLC to another device. Think of this board as a serial port for a mainframe. Looks like the same card is intended for use in IBM POWER hardware too, running OS/400 or AIX (or Linux).
Of course, an open question is who on earth is still using SDLC over RS-485 these days, but then again I still see new Dell servers fitted with RS-232 ports.
RS-232/422/485 are better than surprise USB-C port that require outdated specific Rust compilers and random 32bit ARM binary and an archive.org copy of random repository along cryptic code comments in it to make it work. Obsoleting RS-* ports could very well trigger that event.
The problem though is that while serial is indeed much more commonplace than you might think (look at any device in your household, chances are high that it contains at least one internal serial port that was used for development), it’s all 3.3V or less with no negative voltages now. We don’t really use the RS-232 physical interface much anymore, it’s very unwieldy. (We also seldomly connect anything but the tx and rx lines, which is a bit of a shame for flow control, but often sufficient for what the ports are actually used for.)
So if you interface with those “modern” incarnations of serial ports today, your built in RS-232 COM port is useless most of the time anyway, and you already resort to a small, cheap USB serial adapter board that does the same thing at nowadays non-insane signal levels.
My favourite is connecting to some piece of embedded hardware’s USB service port and finding it’s a bog standard FTDI chipset… complete with the vendor’s drivers being a repackaged version of ftdibus.sys
And for even more fun, multiple vendors with multiple, incompatible versions of the FTDI drivers required.
We've been using RS232 since 1960. I have 100% confidence that in a thousand years there will still be engineering terminals in starships emulating a VT100
There will at least - in 75 years be something internally, a minimum layer of abstraction that looks a whole lot like VT100 escape codes in a character stream. It's probably one of the stickiest API's that I can think of.
PCIleech was originally a framework developed for general pentesting and redteaming. Under certain circumstances pcie devices have read and write access to the entirety of the RAM without any special software running on the connected PC. The pcie device can simply send packets requesting the contents of addresses and the bus happily responds.
This enables all kinds of interesting things. Unfortunately games also store the position of enemy players in memory, so people use it to read those values from memory.
But at least we got cheap fpga devices from that situation.
Is that still the case? IOMMUs have been a thing for a very long time, and nowadays you don’t trust random devices anymore. Certainly a Thunderbolt port (which is PCIe-via-string) does not want to expose memory unrestricted, and while you might be tempted to think that a built-in PCIe card could be under more lax policy because it’s considered “physical access”, you don’t actually want the driver code for that card to be a wide open attack surface for the rest of the system.
It’s not that hard to reverse engineer anything you know about. You know, there is FPGA, there is PCIe, FPGA model is also known. All externals interfaces are also known. High probability, that the board is not broken.
Imagine obscure motherboard, produced 25-30 years ago. No current colleague has seen it before. Half designed internally, other half circuits licensed. All the ICs met very aggressive thermal glue and their names are gone. The client is to ready to pay anything for the repair. They sent you crate full of broken boards. That’s where real reverse engineering starts.
Or imagine a Drake R8A receiver, described as "guaranteed NOT to work" that a friend picked up. It can be tricked into working, but it gives a "PWRLOS" display most of the time, and there is no discernable cause. Thanks to the obscure NEC uPD78213 cpu actually being available and documented, and having no internal rom... it's time to write a disassembler[1] (or later find out that MAME has one[2] thats pretty good), look at all the schematics, and figure out how the firmware works.
*Still working on the disassembler, because I can eventually make mine interactive, add labels, comments, etc.
"No internal ROM" might mean that it relies on a bunch of custom PLA chips which would not be an improvement. With a ROM there is at least a chance you can dump it and run a disassembler on the contents to figure out what it is trying to do.
Nope, I've got complete schematics, and a dump of the EPROM. It's going to take a while to figure out how the heck why it's hallucinating a power failure (the signals going into the CPU are appropriate).
Oh, it has a ROM, just on an external chip. I misunderstood your original post. I thought they had somehow programmed the device without using ROM at all, which made it either very old school or very custom.
Doesn't a PLA just boil down to a truth table that you can dump the same way? Or am I thinking of the other kind of programmable logic chip used for this purpose? GAL, I think?
If it’s only combinatorial logic, without any flip-flops or anything else you can consider “state”, it depends on how many inputs it has.
16 inputs is 65536 combinations. Even at a very low clock it takes you no time to just try all of them. 32 inputs is 4 billion. Now you’re getting somewhere, but even then, at somewhat reasonable clock speeds it should take you a day at the very most…
The more interesting parts of maths lie where one can reach (apparently) strong results from (apparently) weak premises: yield to the desire to start with too strong of an antecedent, and your poor technique kills your own sword/[proper frame hom into 2]: ex falso quodlibet.
(look into your sword, Y. Gradstudent Sagiri: have you detached that head clause by cutting into a principal prime ideal and a completely prime filter?)
What’s your expectation from CCD drive circuit? Understand enough and repair it? Make a similar device? Make a micrometer exact clone?
In that case with old crap we used X-ray pcb inspection machine. Made enough pictures to recreate all the copper traces on paper. Was enough to understand how it works and repair.
reply