Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#8810 closed defect (fixed)

brcm63xx V2110 broken in trunk

Reported by: jmccrohan@… Owned by: florian
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: V2119, Voyager 2110 Cc:


I downloaded the latest openwrt-BTV2110-squashfs-cfe.bin image from trunk and installed it via CFE on my BT Voyager V2110.

It does not boot, with board_bcm963xx claiming an unknown board.

CFE version 1.0.37-6.8.5 for BCM96348 (32bit,SP,BE)
Build Date: Tue Jan  2 19:44:45 CST 2007 (michaelc)

Boot Address 0xbfc00000

Flash Config: CS0(1fc00009,1f),Base(bfc00000),Size(4MB)
Ethernet Switch Mode 00000000
found@block 8

Board IP address                  :
Host IP address                   :
Gateway IP address                :
Run from flash/host (f/h)         : f
Default host run file name        : vmlinux
Default host flash file name      : bcmModelName_fs_kernel
Boot delay (0-9 seconds)          : 5
Board Id Name                     : V2110
Psi size in KB                    : 24
Number of MAC Addresses (1-32)    : 2
Ethernet MAC Address              : 00:16:e3:00:00:00
Serial Number                     :
WEP 128bit Key                    : 0000000000000
Memory size in MB                 : 16
CMT Thread Number                 : 0

==== Press space key to stop auto run (5 seconds) ====
Auto run second count down(before hit space key): 0
Code Address: 0x80010000, Entry Address: 0x80010000
Decompression OK!
Entry at 0x80010000
Closing network.
Starting program at 0x80010000
Linux version ( (gcc version 4.3.3 (GCC) ) #1
Sun Feb 6 04:06:36 CET 2011
Detected Broadcom 0x6348 CPU revision b0
CPU frequency is 240 MHz
16MB of RAM installed
registering 37 GPIOs
board_bcm963xx: CFE version: 1.0.37-6.8
board_bcm963xx: unknown bcm963xx board: V2110
bootconsole [early0] enabled
CPU revision is: 00029107 (Broadcom BCM6348)
Kernel panic - not syncing: unable to detect bcm963xx board

Attachments (1)

boardparms.c (119.3 KB) - added by jmccrohan@… 7 years ago.
Original V2110 Buildchain /target/boardparms.c

Download all attachments as: .zip

Change History (6)

comment:1 Changed 7 years ago by florian

  • Owner changed from developers to florian
  • Status changed from new to accepted

This is expected because there is no support for such a board yet.

Changed 7 years ago by jmccrohan@…

Original V2110 Buildchain /target/boardparms.c

comment:2 Changed 7 years ago by jmccrohan@…

I just found the original V2110 buildchain that I requested from BT years ago.

You can see from boardparms.c that the V2110 board is identical to the RTA1025W_16 board.

I do not have access to the board at the moment, but I will make and test it when I get a chance.

I can upload the full source if it is of use to anyone.

comment:3 Changed 7 years ago by roger@…

I have added a patch for OpenWRT to support the BT Voyager 2500V which has been accepted.

Take a look at this patch in Trac Issue 9070

You need to do 2 things to get OpenWRT working.
1) arch/mips/bcm63xx/boards/board_bcm963xx.c needs to have a definition of your board and also to have the board added to the list
Note -in board_bcm963xx you can ignore all the changes to do with the 8 Meg flash which is specific to the Voyager 2500V as I can tell from the CFE boot logs that your device only has 4 Meg of flash.

The proper way for this is a patch file in target/linux/brcm63xx/patches-2.6.xx
But for now I just edit the file in the build_dir folder and remake OpenWRT.

You will get OpenWRT to load and get a command prompt. At this point OpenWRT will work, but it will fail when you reboot.

2) I expect that your board will use the same CRC checksum logic used by Voyager 2500 which means that once the image has been flashed, and OpenWRT has booted, the checksum on the firmware will get changed as OpenWRT creates a writable file system.
So on reboot CFE will report a checksum error.

To fix this, edit this file


and add in the board name.

You should then have a working V2110.
However there is no ADSL support in OpenWRT as Broadcom only did binary drivers for older kernels.

Drop me a line on the OpenWRT-dev mailing list if you want.

comment:4 Changed 7 years ago by florian

  • Resolution set to fixed
  • Status changed from accepted to closed

Applied in r26959, thanks!

comment:5 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.