Cannot Load Php5ts Dll Fixer there. Contents • • • • • • • • • Most managed devices like switches, routers and others allow a direct connection via a serial Console connection. Requirements Console terminal serial port (COM port) A compatible Console terminal can be setup with a PC running Windows or Linux with at least one COM port connector (male type). If your system does not have a COM port you can get an USB – COM adapter to have at least one COM port connector. COM2 (DB25 male) and COM1 (DE9 male) ports USB – COM (DE9 male) adapter COM1 and COM2 (both DE9 male) ports Device Console port Usually Console port on device is DE9 or RJ45 (most Cisco devices) and on older devices can also show as DB25. In this case it can be easily converted to DE9 using an adapter.

Multiple configurations may be found. RJ45 Console port DB25 (male) to DE9 (female) adapter DB25 (female) Console port DE9 (male) Console port Serial cable Serial cables usually have 2 DE9 connectors (one male / female and other female) or a DE9 (female) and a RJ45 connector (this one is also known as a Cisco rollover cable). DE9 cable (male – female) cable DE9 cable (female – female) cable Cisco rollover cable On Windows you can use HyperTerminal or SecureCRT and on Linux you can use Minicom. You must configure connection so both sides expect same data speed and protocol.

A typical configuration to connect to a Cisco switch or router is 9600 8 N 1 (meaning 9600 baud, 8 data bits, no parity and 1 stop bit). Console terminal must be setup with these settings so communication to device is successful. Console terminal HyperTerminal HyperTerminal (from Windows XP) can be used as a Console terminal also on other Windows versions (tested under Windows 7). You just need to grab application files from a Windows XP. You will need the following files: - hypertrm.exe: main executable file - hypertrm.dll: library file - hticons.dll: icons file - hypertrm.hlp: help file - hypertrm.chm: help file HyperTerminal: File list And they will be in several places on Windows XP Install like c: windows, c: windows system32 and c: windows help.

Building a Serial Port for. So that I could access U-Boot and the OpenWRT console. The default minicom config file, changed the serial port to. I have openwrt linux box. How to get the text,which appears on serial console. I am using hyper-term/tera-term s/w for windows and minicom s/w for linux to.

You can pack and copy them all into a single folder and you are ready to go, just start hypertrm.exe. Windows XP HyperTerminal Now I will setup a connection to a Cisco 2651 router as example. I will be using an USB to Serial adapter to have at least one COM serial port and a typical Cisco rollover cable to connect to router Console port.

Connection diagram You should confirm your COM port number. If your computer as one or two ports they are usually ports 1 and 2. On this example I will be using COM8 given by an USB – COM adapter (port number can be seen on Windows 7 on “Device Manager” – “Ports (COM&LPT)”. COM port number shown on “Device Manager” – “Ports (COM&LPT)” Give connection a name (“Cisco serial Console”) and press OK. (You can choose any icon available.) After you connect using your available COM port (“COM8” for me) and press OK. HyperTerminal: New connection name HyperTerminal: Choose port to connect to device Console Now we must configure expected device settings on “Port Settings”. Those settings can be found sometimes printed on device chassis, device documentation and / or available from manufacturer website.

Most Cisco devices like 2651 router use 9600 baud (“Bits per Second”), 8 bits (“Data bits”), “No Parity” and 1 “Stop bit”. Flow control can be important, depending on your COM port hardware, if you wish to do a device recovery and need to send a “space” or other char while device is booting. For now I will leave this as is (flow control by hardware). Change “Bits per second” to 9600, from defaults, and press OK. HyperTerminal: Choose serial Console port settings Be sure that cable or cables are firmly connected and turn on your device. Connection should show now 9600 8-N-1 on status bar and output from device should start to be seen on HyperTerminal Console terminal also. When requested you can login into your device and start working (You may need to press Enter sometimes to see output.) HyperTerminal: Console terminal with a Cisco 2651 and login SecureCRT SecureCRT can be used for telnet, ssh connections but also as a serial Console terminal.

You can get it from with a 30-day evaluation license. Setup is same as other Windows applications. Configuration is also very similar to one made with HyperTerminal. First we create a new Session. Vandyke SecureCRT A wizard will start to helps us set all relevant options: a) Protocol: Serial, b) Settings: Port: COM8 (use your COM port number) and Baud rate: 9600, keep other settings on default: Data bits: 8, Parity: None and Stop bits: 1 and finally c) set Session name: “Cisco serial Console”. After all setup you can start your serial Console terminal pressing Connect.

A) SecureCRT: Choose Protocol b) SecureCRT: Choose Settings c) Secure CRT: New Session name SecureCRT: Connect will start a serial Console terminal Finally SecureCRT: Console terminal with a Cisco 2651 and login Comments Comments and suggestions to improve this entry are very welcome.

CuteCom Welcome to CuteCom CuteCom is a graphical serial terminal, like minicom (or Hyperterminal on Windows, but I don't want to compare CuteCom to it, since Hyperterminal is really one of the worst applications I know). Currently it runs on Linux, FreeBSD and Mac OS X.

It is aimed mainly at hardware developers or other people who need a terminal to talk to their devices. It is free software and distributed under the GNU General Public License Version 2, which can find in the file. It is written using the by Trolltech. Follow this link to visit the. CuteCom doesn't use the autotools (autoconf, automake, libtool, etc.) Instead 'configure' is simply a wrapper script which calls qmake. To uninstall CuteCom simply delete the file 'cutecom' and the file 'cutecom.desktop' and you're done. The config file is ~/.config/CuteCom/CuteCom.conf (was ~/.qt/cutecomrc in the Qt3-based versions).

Content Cleanup Required This article should be cleaned-up to follow the content standards in the Wiki Guide. This document presents (almost) the minimum amount of work required to enable a serial console login on an Ubuntu 6.06 and later versions. (Minor changes have been added to improve performance.) Both server and client settings are included.

This procedure was developed using the Remote Serial Console HOWTO (see 'External links' below), and adapted to apply specifically to Ubuntu. The reader is referred to this document for any issues arising from using this HOWTO. Assumptions • You have enabled the serial console in your BIOS. • The serial connection is being made at 115200 baud 8n1, on first serial port, called /dev/ttyS0 in linux (9600 8n1 is the default fall back if your hardware does not support 115200 baud) • You are comfortable editing critical system files such as /etc/inittab, /boot/grub/menu.lst • You are using a serial (null modem) cable. It is also possible to use a USB to Serial adaptor, but the tty* must be changed to reflect your hardware. • You have an available serial console on ttyS0. If your not getting any output, a real serial port or other device might be using ttyS0.

Try using ttyS1, ttyS2, etc. If you want to use a standard Ethernet/RJ-45 cable for serial connection you can buy a couple of Serial to Cat 5 adapters. Server Setup Configuring the console login process This section details how to configure the 'getty' process to enable a login via the console port. You need to configure either an Upstart system or the older inittab, depending on Ubuntu version you are using.

Configuring upstart (Karmic and newer) 1) Create a file called /etc/init/ttyS0.conf containing the following: # ttyS0 - getty # # This service maintains a getty on ttyS0 from the point the system is # started until it is shut down again. Start on stopped rc RUNLEVEL=[12345] stop on runlevel [!12345] respawn exec /sbin/getty -L 115200 ttyS0 vt102 2) Ask upstart to start the getty sudo start ttyS0 Configuring upstart (Edgy/Feisty/Jaunty) Create a file called /etc/event.d/ttyS0 containing the following: # ttyS0 - getty # # This service maintains a getty on ttyS0 from the point the system is # started until it is shut down again. Start on runlevel 1 start on runlevel 2 start on runlevel 3 start on runlevel 4 start on runlevel 5 stop on runlevel 0 stop on runlevel 6 respawn exec /sbin/getty 115200 ttyS0 Configuring inittab (only Dapper and older!) 1) Edit /etc/inittab sudo vi /etc/inittab 2) Change the following line: #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 to: T0:123:respawn:/sbin/getty -L ttyS0 115200 vt100 3) Restart init: sudo /sbin/telinit q At this point, a new login prompt should appear on the output of the serial console. Configuring grub This section details how to get grub talking via the serial port. This section is optional if the user does not want grub interaction via the serial console port. Configuring (Karmic and newer) 1) Edit /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg.