Root/target/linux/brcm63xx/image/README.images-bcm63xx

1The image neede to flash onto a Broadcom 63xx-series board depends on the
2board, method you are using to flash, and, for web-based flash, on the version
3of the Broadcom code your router uses.
4
5There are two major revisions of the Broadcom code as far as imagetags are
6concerned, before 3.08 and after 3.08, however there are some variations
7within in that, either due to vendor differences or due to changes at
8Broadcom (it's not clear yet which is the case). In addtion Pirelli modified
9the Broadcom code, so Alice Gate models use a different imagetag than any
10other vendor.
11
12The imagetag format for flashing via CFE is the same for almost all the
13boards, and is the same for all images generated by the imagetag utility.
14Images flashable using cfe are labelled openwrt-<board>-<filesystem>-cfe.bin
15
16The imagetags for tftp/ftp flashing is based on Broadcom 3.00-3.04 imagetags
17and is known to be correct as the source code GPL and is available for reading.
18
19Broadcom code 2.21 is based on the BT Voyager firmware image I looked at. It
20may in fact be BT Voyager-specific. 2.21 is actually more difficult to deal
21with the imagetag from 3.00 as it has three different CRC calculations in
22addtition to the header CRC.
23
24Broadcom 3.00-3.02 flashing has been tested on Comtrend CT-5261, CT-536 and
25Tecom GW6000, and is the version of the flashing that was present before the
26imagetags were split by broadcom code version (early June 2009)
27
283.04 is guessed to be the same as 3.00-3.02 based on available information
29
30Broadom 3.06 is thought to be the same as 3.00-3.02, however the only 3.06
31this author (Daniel Dickinson) has seen is the Alice Gate (Pirelli) firmware
32which is known to be different due to vendor (Pirelli) modifications to the
33Broadcom code.
34
35Broadcom 3.10 uses an imagetag that is believed to apply to all 3.10 and 3.12
36versions, and has been tested on the Tecom GW6200. This version introdec changes to
37the imagetag to deal with TR69 (a remote rouer management system developed by the
38DSL forum). There is a field for vendor-specific information, that at least in some
39cases is not optional. It is based on the hexedit of a neufbox4 firmware image, the
40information in https://dev.openwrt.org/ticket/4987, and the hexedit of a Tecom
41GW6200 image.
42
43Some boards share the same tag format, but require vendor-specific fields in
44the board. In that case the tagid is shared, but the filename of the generated
45image reflects the router for which the image was created.
46
47router |method | codever |filename
48+-------------+-------------+---------+---------------------------------------
49|any |cfe+most web | any |openwrt-<board>-<fs>-cfe.bin
50|AGVoIP2+WiFi |cfe |alice3.06|openwrt-AGV2+W-cfe-<fs>-cfe.bin
51|AGVoIP2+WiFi |web |alice3.06|openwrt-AGV2+W-cfe-<fs>-cfe.bin
52|CT536 |web |3.02 |openwrt-CT536_CT5621-<fs>-cfe.bin
53|CT5621 |web |3.02 |openwrt-CT536_CT5621-<fs>-cfe.bin
54|DG834GT |web |3.02 |openwrt-DG834GT_DG834PN-<fs>-cfe.bin
55|DG834PN |web |3.02 |openwrt-DG834GT_DG834PN-<fs>-cfe.bin
56|DSL-2640B |web |3.10 |openwrt-DSL2640B-<fs>-cfe.bin
57|DSL-2740B |web |3.10 |openwrt-DSL2670B-<fs>-cfe.bin
58|F5D7633 |web |3.10 |openwrt-F5D7633-<fs>-cfe.bin
59|F@ST2404 |web |3.0X? |openwrt-F@ST2404-cfe-<fs>-cfe.bin
60|F@ST2404 |web |3.1X? |openwrt-F@ST2404-<fs>-cfe.bin
61|GW6000 |web |3.00 |openwrt-GW6000-<fs>-cfe.bin
62|GW6200 |web |3.10 |openwrt-GW6200-<fs>-cfe.bin
63|Neufbox4 |web |3.12 |openwrt-NEUFBOX4-<fs>-cfe.bin
64|TD8810A |web |3.06 |openwrt-TD8810-<fs>-cfe.bin
65|TD8810B |web |3.06 |openwrt-TD8810-<fs>-cfe.bin
66|TD8811A |web |3.06 |openwrt-TD8811-<fs>-cfe.bin
67|TD8811B |web |3.06 |openwrt-TD881-<fs>-cfe.bin
68|TD8900GB |web |3.06 |openwrt-TD8900DB<fs>-cfe.bin
69|USR9108 |web |3.0X? |openwrt-USR9108-<fs>-cfe.bin
70|V2091_BTR |web |2.21 |openwrt-V2091_BTR-<fs>-cfe.bin
71|V2091_ROI |web |2.21 |openwrt-V2091-<fs>-cfe.bin
72|V2091_WB |web |2.21 |openwrt-V2091-<fs>-cfe.bin
73|V210_BTR |web |2.21 |openwrt-V210_BTR-<fs>-cfe.bin
74|V210_ROI |web |2.21 |openwrt-V210-ROI_WB<fs>-cfe.bin
75|V210_WB |web |2.21 |openwrt-V210-ROI_WB<fs>-cfe.bin
76|V2110 |web |2.21 |openwrt-V2110-<fs>-cfe.bin
77|V2110_AA |web |2.21 |openwrt-V2110-<fs>-cfe.bin
78|V2110_ROI |web |2.21 |openwrt-V2110-<fs>-cfe.bin
79|V2500V |web |2.21 |openwrt-V2500V<fs>-cfe.bin
80|V2500V_AA |web |2.21 |openwrt-V2500V-<fs>-cfe.bin
81|V2500V_SIP_CLUB |web |2.21 |openwrt-V2500V-<fs>-cfe.bin
82
83Old imagetag routers
84--------------------
85Davolink DV201AMR
86
87Redboot routers
88---------------
89Inventel Livebox
90
91Known router->code versions
92---------------------------
93
94Vendor |Model |Code Ver
95---------------------------+------------------------------------------+--------
96Belkin |F5D7633 |3.10
97British Telecom (BT) |Voyager V2091_BTR |2.21
98British Telecom (BT) |Voyager V2091_ROI |2.21
99British Telecom (BT) |Voyager V2091_WB |2.21
100British Telecom (BT) |Voyager V210_BTR |2.21
101British Telecom (BT) |Voyager V210_ROI |2.21
102British Telecom (BT) |Voyager V210_WB |2.21
103British Telecom (BT) |Voyager V2110 |2.21
104British Telecom (BT) |Voyager V2110_AA |2.21
105British Telecom (BT) |Voyager V2110_ROI |2.21
106British Telecom (BT) |Voyager V220V |2.21
107British Telecom (BT) |Voyager V2500V |2.21
108British Telecom (BT) |Voyager V2500V_AA |2.21
109British Telecom (BT) |Voyager V2500V_SIP_CLUB |2.21
110Comtrend |CT-5261 |3.02
111Comtrend |CT-536 |3.02
112D-Link |DSL-2640B |3.10
113D-Link |DSL-2670B |3.10
114NetGear |DG834GT |3.02
115NetGear |DG834PN |3.02
116Neuf Cegetel |Neufbox 4 |3.12
117Pirelli |Alice Gate Wi-Fi (+VoIP models?) |ag 3.06
118Sagem |F@ST2404 |?
119TP-Link |TD-8810A |3.06
120TP-Link |TD-8810B |3.06
121TP-Link |TD-8811A |3.06
122TP-Link |TD-8811B |3.06
123TP-Link |TD-W8900GB |3.06
124Tecom |GW6000 |3.00
125Tecom |GW6200 |3.10
126USR |9108 |?
127
128

Archive Download this file



interactive