User Tools

Site Tools


toh:huawei:hg655d

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
toh:huawei:hg655d [2014/08/04 21:55]
danitool
toh:huawei:hg655d [2015/02/04 08:20] (current)
evfool Removed duplicate info
Line 1: Line 1:
 ====== Huawei HG655a/​b/​d/​m ====== ====== Huawei HG655a/​b/​d/​m ======
-The HG655b is an adsl/vdsl wifi router distributed by Romtelecom Romania to their customers. It appears to have very similar features to the HG655d.+The **HG655b** is an adsl/vdsl wifi router distributed by [[wp>Romtelecom]] Romania to their customers. It appears to have very similar features to the HG655d.
  
-The HG655d is an adsl/vdsl wifi router distributed by Online/​T-Mobile Netherlands to their customers. It has 64Mb of RAM, 8Mb of Flash, 2.4Ghz 11n Wifi and a USB port.+The **HG655d** is an adsl/vdsl wifi router distributed by [[wp>T-Online]]/[[wp>T-Mobile]] Netherlands to their customers. It has 64Mb of RAM, 8Mb of Flash, 2.4Ghz 11n Wifi and a USB port.
  
-The HG655m is a reduced cost adsl/vdsl router common in Asia, and which replaced the HG655a. There is a particularly cheap edition (US$40) available on eBay at the moment which is a Telekom Malaysia unit for their Unifi fibre broadband service. Aliexpress has the same model going for US$30. It has 32Mb of RAM, 16Mb of dual boot Flash, no Wifi and no USB port.+The **HG655m** is a reduced cost adsl/vdsl router common in Asia, and which replaced the HG655a. There is a particularly cheap edition (US$40) available on eBay at the moment which is a Telekom Malaysia unit for their Unifi fibre broadband service. Aliexpress has the same model going for US$30. It has 32Mb of RAM, 16Mb of dual boot Flash, no Wifi and no USB port.
  
 ==== Extra notes on the HG655m ==== ==== Extra notes on the HG655m ====
Line 21: Line 21:
 ^ Router version ^ Board model ^ Supported ^ Notes ^ ^ Router version ^ Board model ^ Supported ^ Notes ^
 | HG655a | unknown ​                                    | not supported | not supported | | HG655a | unknown ​                                    | not supported | not supported |
-HG556b ​| HG655**<​color crimson>​B</​color>​**RZ VER.A   ​| ​ WIP  | <color crimson>​ADSL not supported</​color>​ | +HG655b ​| HG655**<​color crimson>​B</​color>​**RZ VER.A   ​| ​ WIP  | <color crimson>​ADSL not supported</​color>​ | 
-HG556d ​| HG655**<​color crimson>​D</​color>​**RZ VER.A   ​| ​ WIP  |  ::: |+HG655d ​| HG655**<​color crimson>​D</​color>​**RZ VER.A   ​| ​ WIP  |  ::: |
 | HG655m | AV1HG655MM VER.B                            | not supported | not supported | | HG655m | AV1HG655MM VER.B                            | not supported | not supported |
  
Line 32: Line 32:
 | HG655b/d | Broadcom 6368 | 64MiB | 8MiB  | 4 x 1| 2 | Yes | Yes     | Yes     | | HG655b/d | Broadcom 6368 | 64MiB | 8MiB  | 4 x 1| 2 | Yes | Yes     | Yes     |
 | HG655m ​  | Broadcom 6368 | 32MiB | 16MiB | 4 x 1| 2 | No  | Yes | unknown | | HG655m ​  | Broadcom 6368 | 32MiB | 16MiB | 4 x 1| 2 | No  | Yes | unknown |
- 
  
 ===== Installation ===== ===== Installation =====
Line 38: Line 37:
   - → [[doc:​howto:​generic.flashing|Install OpenWrt]]   - → [[doc:​howto:​generic.flashing|Install OpenWrt]]
   - → [[about/​latest|Latest OpenWrt release]]   - → [[about/​latest|Latest OpenWrt release]]
 +
 +**Available firmwares:​**
 +^ Version ^ firmware link ^ notes ^
 +| Barrier Braker 14.07 | [[https://​drive.google.com/​uc?​export=download&​id=0B-EMoBe-_OdBX21TYnRGNTI1SzA|openwrt-HG655x-squashfs-cfe-BB.zip]] | ADSL, VoIP/FXS not supported\\ HG655d might be unable to flash it |
  
 ==== Flash Layout ==== ==== Flash Layout ====
-Please check out the article [[doc:​techref:​Flash Layout]]. It contains an example and a couple of explanations.+Please check out the article [[doc:​techref:​Flash.Layout]]. It contains an example and a couple of explanations.
  
 For the HG655b version, with the vendor firmware, the flash chip is divided in several areas storing data for different purposes: For the HG655b version, with the vendor firmware, the flash chip is divided in several areas storing data for different purposes:
Line 51: Line 54:
 | 0x007a0000 | 65536 | ATP_LOG | | 0x007a0000 | 65536 | ATP_LOG |
 | 0x007b0000 | 65536 | Div tr069 conf? Env …. | | 0x007b0000 | 65536 | Div tr069 conf? Env …. |
-| 0x007c0000 | 65536 | [[#wifi.calibration.data|wifi calibration data]] |+| 0x007c0000 | 65536 | [[#wifi_calibration_data|wifi calibration data]] |
 | 0x007e0000 | 65536 | passwords? | | 0x007e0000 | 65536 | passwords? |
  
Line 71: Line 74:
 ->  [[doc:​howto:​generic.flashing.tftp]] ->  [[doc:​howto:​generic.flashing.tftp]]
  
-FIXME+For using tftp you first need serial console access to break into CFE bootloader, this allows to send commands to CFE to pick up the firmware from a tftp server in your computer. The command you need to send to CFE is something like this 
 +<​code>​f 192.168.1.35:​firmware.bin</​code>​ 
 + 
 +where 192.168.1.35 is the IP of your computer where a tftp server is running and serving the firmware.bin file.
  
 ==== Upgrading OpenWrt ==== ==== Upgrading OpenWrt ====
Line 189: Line 195:
   *To remove the cover do a/b/c   *To remove the cover do a/b/c
  
-===== HG655b ​=====+=== HG655b ===
 {{:​media:​toh:​huawei:​hg655b-board1.jpg?​400x300|}} {{:​media:​toh:​huawei:​hg655b-board1.jpg?​400x300|}}
 {{:​media:​toh:​huawei:​hg655b-board2.jpg?​400x300|}} {{:​media:​toh:​huawei:​hg655b-board2.jpg?​400x300|}}
  
-===== HG655m ​=====+=== HG655m ===
 {{:​media:​toh:​huawei:​hg655m_front.jpg?​400x400|}} {{:​media:​toh:​huawei:​hg655m_front.jpg?​400x400|}}
 {{:​media:​toh:​huawei:​hg655m_back.jpg?​400x400|}} {{:​media:​toh:​huawei:​hg655m_back.jpg?​400x400|}}
Line 289: Line 295:
  
 ==== 128MiB RAM Mod ==== ==== 128MiB RAM Mod ====
 +n/a
  
 ===== Bootlogs ===== ===== Bootlogs =====
 ==== HG655b OEM bootlog ==== ==== HG655b OEM bootlog ====
 <​HTML>​ <​HTML>​
-<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​10px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​+<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​12px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​
 <​code>​CFE version 1.0.37-102.6 for BCM96368 (32bit,​SP,​BE) <​code>​CFE version 1.0.37-102.6 for BCM96368 (32bit,​SP,​BE)
 Build Date: Wed Mar 23 22:59:09 CST 2011 (lihua@IBM_x3500) Build Date: Wed Mar 23 22:59:09 CST 2011 (lihua@IBM_x3500)
Line 1927: Line 1934:
 </p> </p>
 </​HTML>​ </​HTML>​
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
  
 ==== HG655m OEM bootlog ==== ==== HG655m OEM bootlog ====
 +
 Note that the following bootlog is for the HG655b Romtelecom firmware flashed onto HG655m hardware. As a result, there are errors about the missing Wifi unit, but otherwise the unit appears entirely functional. After this bootlog I also place a bootlog for the HG655d firmware flashed onto HG655m hardware for reference. Note that the following bootlog is for the HG655b Romtelecom firmware flashed onto HG655m hardware. As a result, there are errors about the missing Wifi unit, but otherwise the unit appears entirely functional. After this bootlog I also place a bootlog for the HG655d firmware flashed onto HG655m hardware for reference.
  
 You will surely note that the CFE bootloader thinks that the board is a 96368MVWG, not a HG65x. You will surely note that the CFE bootloader thinks that the board is a 96368MVWG, not a HG65x.
 <​HTML>​ <​HTML>​
-<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​10px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​+<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​12px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​
 <​code>​ <​code>​
 CFE version 1.0.37-102.6 for BCM96368 (32bit,​SP,​BE) CFE version 1.0.37-102.6 for BCM96368 (32bit,​SP,​BE)
Line 3884: Line 3913:
 </p> </p>
 </​HTML>​ </​HTML>​
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
  
 ==== OpenWrt bootlog ==== ==== OpenWrt bootlog ====
 +
 <​HTML>​ <​HTML>​
-<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​10px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​+<p style="​padding:​ 10px;​border:​1px solid grey;​height:​600px;​font:​12px/14px Georgia, Garamond, Serif;​overflow:​Auto;​background-color:#​FFFFFF">​
 <​code>​[ ​   0.000000] Linux version 3.10.34 (dani@tool) (gcc version 4.8.3 (OpenWrt/​Linaro GCC 4.8-2014.01 r40396) ) #18 SMP Wed Apr 30 19:58:28 CEST 2014 <​code>​[ ​   0.000000] Linux version 3.10.34 (dani@tool) (gcc version 4.8.3 (OpenWrt/​Linaro GCC 4.8-2014.01 r40396) ) #18 SMP Wed Apr 30 19:58:28 CEST 2014
 [    0.000000] Detected Broadcom 0x6368 CPU revision b2 [    0.000000] Detected Broadcom 0x6368 CPU revision b2
Line 4104: Line 4151:
  
 Datasheet [[http://​huaweiservis.net/​dosya/​HUAWEI-HG655d-datasheet.pdf]] ​ Datasheet [[http://​huaweiservis.net/​dosya/​HUAWEI-HG655d-datasheet.pdf]] ​
 +
  
 ==== BCM tag ==== ==== BCM tag ====
Line 4128: Line 4176:
  
 ==== Wifi calibration data ==== ==== Wifi calibration data ====
 +In theory each wifi chip (it doesn'​t matter if they are exactly the same model) has its own wifi calibration data. In this router the data is stored in an area of the flash chip. This area is the cal_data partiton in OpenWrt firmwares. It's a good idea to backup this partition. Just use these simple commands
 +  * First identify the cal_data partition<​code>​root@OpenWrt:​~#​ cat /proc/mtd
 +dev:    size   ​erasesize ​ name
 +mtd0: 00020000 00010000 "​CFE"​
 +mtd1: 0010ff00 00010000 "​kernel"​
 +mtd2: 00690000 00010000 "​rootfs"​
 +mtd3: 00350000 00010000 "​rootfs_data"​
 +mtd4: 00010000 00010000 "​cal_data"​
 +mtd5: 00010000 00010000 "​nvram"​
 +mtd6: 007a0000 00010000 "​linux"</​code>​
 +  * now backup the mtd that matches to the cal_data partition<​code>​dd if=/​dev/​mtd4 of=/​tmp/​eeprom.bin</​code>​ and transfer the eeprom.bin backup file to your computer.
 +
 +The content of the cal_data partition is something like this (taken from a full backup of the flash chip):
 <​code>​007C:​0000 | 62 30 01 00  72 D1 5E 0D  AD 6C 62 30  14 18 01 80 | b0..rÑ^.­lb0.... <​code>​007C:​0000 | 62 30 01 00  72 D1 5E 0D  AD 6C 62 30  14 18 01 80 | b0..rÑ^.­lb0....
 007C:0010 | 00 00 62 30  14 18 00 00  01 00 6A FF  0C 00 FF FF | ..b0......jÿ..ÿÿ 007C:0010 | 00 00 62 30  14 18 00 00  01 00 6A FF  0C 00 FF FF | ..b0......jÿ..ÿÿ
Line 4161: Line 4222:
 007C:01F0 | FF FF FF FF  FF FF FF FF  FF FF FF FF  FF 06 86 93 | ÿÿÿÿÿÿÿÿÿÿÿÿÿ... 007C:01F0 | FF FF FF FF  FF FF FF FF  FF FF FF FF  FF 06 86 93 | ÿÿÿÿÿÿÿÿÿÿÿÿÿ...
 </​code>​ </​code>​
 +
 +If you accidentally erased your cal_data partition and you you didn't make your own bakcup, you can use the above data to fill the erased partition (note the MAC address is specific for each calibration data). Try this:
 +  * Generete a bin file with the cal_data. You don't need to do this step if already have your own backup. Make it at your PC with a linux distro:<​code>​echo '​6230010072D15E0DAD6C623014180180000062301418000001006AFF0C00FFFFFFFFFFFFB092FFFFFFFFFFFFFFFFFFFFFFFFFFFF22082400FFFF1601FFFFD9FACC88FFFF0DFF0000030000000000FFFFFFFF0E0F0F0F10101010100F0F0F0F0F0C0C0C0C0C0C0C0C0C0B0B0B0B0BFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF555588887777666666666666666666666666FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF068693'​ | xxd -r -p > eeprom.bin</​code>​
 +  * Now transfer the **eeprom.bin** file into your router and flash the **cal_data** partition<​code>​mtd write eeprom.bin cal_data</​code>​
 +  * **Restart** Openwrt and check if wifi works.
 +
  
 ===== Tags ===== ===== Tags =====
toh/huawei/hg655d.1407182130.txt.bz2 · Last modified: 2014/08/04 21:55 by danitool