Hello
I have an ultra 10 that I can connect to using HyperTerminal using a null modem cable and a db9 to db25 connector, this works well.
However when I use the same HyperTerminal settings and cable to connect to an e450 serial A. I dont get any output. There are no warning lights and the e450 sounds normal
Any suggestions? Thanks
I have seen similar on an 420, where the serial port can get hung up and you basically have no control / no output until the machine is rebooted.
If you've been connected to the serial port and done
echo "hello" >/dev/console
or
echo "hello" > /dev/sysmsg
And not see anything popping up on screen, it's worth a reboot to see if your console returns to you. If not, it's *possible* you've blown the serial port, it's just not likely as there are so few moving parts. - jeff
The E450 had a weird serial port that combined both serial ports into one DB25. The pinouts for port A were the same as MOST of the standard DB25 RS232 pinouts. I don't have a reference anymore to the exact pinouts anymore.
At any rate, try disabling hardware flow control and try a simple 3-wire connection, using the standard RS232 pinouts.
Port A on the 450 should be identical to any standard 25-pin DCD serial port. It is RS423 by default, but I've never seen that cause a problem with a computer serial port. (I did see it once fail to talk to a green-bar dot-matrix printer that was probably made in 1980 until the jumper was flipped).
Here's a page with pinout information.
http://www.sunhelp.org/unix-serial-port-resources/serial-pinouts/
--
Darren
If it is certain that the console pin out is correct and that the cable is correct and working and the jumpers are correct. Can you think of anything else that could cause the problem other than a blown console port?
By the way there is no OS on this machine all disks have been wiped and I have never even got to obp. thanks
I have seen damaged serial ports, but that is pretty rare (maybe 2 all time for me).
Also rare but possible is that the console could be redirected to serial port b. You'd need to either try that port or reset the nvram (need a sun keyboard for that). It's rare because most admins never bother to modify the console settings.
The other 99.9% of the time, it's some combination of cable or terminal emulation that's wrong.
--
Darren