You are on page 1of 6

How to Recover MyPBX U300/U200/U100/TE100

Using Console Port


Version: V1.0
Date: March, 2013

Yeastar Information Technology Co. Ltd

How to Recover MyPBX U300/U200/U100/TE100 using Console port

This manual can be used on MyPBX U300/U200/U100/TE100.


In this file, we will try to recover MyPBX U300.
For this procedure you will need the following:
1) A console cable (RJ45 to RS232).

Figure 1
2) A serial port on your PC.
3) A serial console client (e.g. putty for windows or minicom for Linux).
4) A TFTP Server (e.g. Tftpd32 for Windows).
Step1 Connect the network cable to MyPBX U300.
Step2 Connect the console cable RJ45 side to Console port, connect the console
cable RS232 side to your PC.
Step3 Power on MyPBX.
Step4 Download the firmware and place it in your TFTIP Servers repository.
Step5 Using putty.exe to connect via Serial Connector.
Download
the
putty.exe
from
http://www.yeastar.com/download/tools/putty.exe
Note: Please check the Communications port detail under Device Manager
Window:

2/6

How to Recover MyPBX U300/U200/U100/TE100 using Console port

Figure 2
Select Serial after you execute putty.exe, change the Speed to 57600

Figure 3
Click Open, you should see the picture below

3/6

How to Recover MyPBX U300/U200/U100/TE100 using Console port

Figure 4
Connection is ready.
Step6 Get ready of TFTP server and uImage.ext2 (the file we send you may in
this format with version number: 12.17.0.30.ext2, please replace uImage.ext2
to 12.17.0.30.ext2).

Figure 5
Step7 Erase incorrect configuration/firmware before we do anything.

4/6

How to Recover MyPBX U300/U200/U100/TE100 using Console port


U300>run erasepersistent
SW ECC selected
NAND erase: device 0 offset 0x8400000, size 0x17c00000
Skipping bad block at 0x09580000
Skipping bad block at 0x095c0000
Skipping bad block at 0x09600000
Skipping bad block at 0x096c0000
Skipping bad block at 0x15820000
Skipping bad block at 0x158a0000
Skipping bad block at 0x192c0000
Skipping bad block at 0x1afc0000
Skipping bad block at 0x1e180000
Erasing at 0x1ffe0000 -- 100% complete.
OK

Step8 Change the default TFTP server (assume your TFTP server ip is
192.168.5.35) and default IP address(get one available ip for uboot ,take
192.168.5.148 for example) of Uboot, you can use printenv to check the server
ip and ipaddr of uboot.
U300>set serverip 192.168.5.35
U300>set ipaddr 192.168.5.148
U300>set gatewayip 192.168.5.1
U300>save
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x260000 -- 100% complete.
Writing to Nand... done

Step9 Change linuxname to the firmware which you want to recover. In this
example, we will recover U300 with the firmware 12.17.0.30.ext2.
U300>set linuxname 12.17.0.30.ext2
U300>save
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x260000 -- 100% complete.
Writing to Nand... done

Step10 Upgrade the firmware. In this step, Uboot will try to download firmware
from server and write the firmware to flash.
U300>run updata-linux

5/6

How to Recover MyPBX U300/U200/U100/TE100 using Console port


SW ECC selected
dm9000 i/o: 0x2c000000, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: f4:b5:49:03:03:06
operating at 100M full duplex mode
Using dm9000 device
TFTP from server 192.168.5.35; our IP address is 192.168.5.148
Filename '12.17.0.30.ext2'.
Load address: 0x82000000
Loading:
########################################################
#######
########################################################
#######
########################################################
#####################################################
done
Bytes transferred = 24852108 (17b368c hex)
NAND erase: device 0 offset 0x400000, size 0x4000000
Erasing at 0x43e0000 -- 100% complete.
OK
NAND write: device 0 offset 0x400000, size 0x17b368c
24852480 bytes written: OK

Step11 Reset the device and then you can login MyPBX U300 using the default
IP 192.168.5.150.
U300>re
resetting ...
[Finish]

6/6