I know I initially struggled getting the right tools amd initially getting connected, so I thought I would share. Here is the equipment I have and the basic steps of getting connected.
1. Cable matters USB to serial:
2. Cisco compatible console cable:
3. Download the serial USB adapter drivers from: http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
4. Download Putty from: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
5. Once your drivers are installed for the USB console cable, note the Com port (listed in windows device manager). Mine was com8, from Putty select serial and enter COM8, IMPORTANT: enter 115200 as the speed/baud rate. Now press connect.
6. Press enter to see output or power cycle the device to view the boot sequence.
This post was updated on .
I've bought this Cisco Console cable to USB :
To use the console cable:
1) find on which COM port the console cable is installed.
2) in Putty select the serial mode, enter the COMx port and use baudrate 115200
3) hit load and start Shield. You should now be able to see what is happening during boot.
Using Shield Pro v1, Chaos Calmer, FW 1.51 SP1, Bridge Mode
2nd Shield as Sandbox, Chaos Calmer, FW 1.51 SP1 + hotfixes
And for those of us who purchase lots of stuff off eBay and picked up a console cable there...
Note that FTDI recently included a bullet in a firmware update that was distributed via the Windows Update channel. That bullet seeks and kills unlicensed FTDI UART chips that are oftentimes included in the cheap knock-off devices like USB Console cables.
If yours is working now, be very cautious about accepting that Windows Update to your FTDI device. If it is a fake chip, once the bullet hits it, it will never work again.
Shield Pro v1, Chaos Calmer, FW 1.51 SP1, v8.3.2, Bridge Mode
|Free forum by Nabble - Resume Templates||Edit this page|