Modify

Opened 4 years ago

Last modified 4 years ago

#14063 new defect

seems the build in trunk for hg556a can not bootup

Reported by: bbsoo7@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: Cc:

Description

CFE>
CFE> f 192.168.1.55:openwrt-HW556-squashfs-cfe.bin
Loading 192.168.1.55:openwrt-HW556-squashfs-cfe.bin ...
Finished loading 2883588 bytes

Flashing root file system and kernel at 0xbe020000:

~Flag: 3

baseAddr 0xbe000000
kernelAddr 0xbe020100
rootfsAddr 0xbe020100
tagFs 0x80800000
............................................

.

Backup flag .

~Flag: 1

.
* Image flash done * !
Resetting board...

CFE version cfe.d081.5003 for BCM96358 (32bit,SP,BE)
Build Date: Wed Nov 11 10:36:35 CST 2009 (Lihua_68693)
Copyright (C) 2006 Huawei Technologies Co. Ltd.

Boot Address 0xbe000000

Initializing Arena.
Initializing Devices.

@w45260: Flash Manufacture id :c2

@w45260Flash Device id :227a

@w45260flipCFIGeometry:0
Parallel flash device: name MX29LV128DB, id 0x227a, size 16384KB
* GetHG556aBoardVersion = <0> *

CPU type 0x2A010: 300MHz, Bus: 133MHz, Ref: 64MHz
Total memory: 67108864 bytes (64MB)

Total memory used by CFE: 0x80401000 - 0x8052A510 (1217808)
Initialized Data: 0x8041F3C0 - 0x80421B60 (10144)
BSS Area: 0x80421B60 - 0x80428510 (27056)
Local Heap: 0x80428510 - 0x80528510 (1048576)
Stack Area: 0x80528510 - 0x8052A510 (8192)
Text (code) segment: 0x80401000 - 0x8041F3B4 (123828)
Boot area (physical): 0x0052B000 - 0x0056B000
Relocation Factor: I:00000000 - D:00000000

* GetHG556aBoardVersion = <0> *

Board IP address : 192.168.1.1
Host IP address : 192.168.1.100
Gateway IP address :
Run from flash/host (f/h) : f
Default host run file name : vmlinux
Default host flash file name : bcm963xx_fs_kernel
Boot delay (0-9 seconds) : 3
Board Id Name : HW556
Psi size in KB : 64
Number of MAC Addresses (1-32) : 14
Base MAC Address : 00:e0:fc:00:00:00
Ethernet PHY Type : Internal
Memory size in MB : 64
CMT Thread Number : 1

* Press any key to stop auto run (3 seconds) *
Auto run second count down: 0
boot kernel from be020100
Code Address: 0x80010000, Entry Address: 0x80010000
Decompression OK!
Entry at 0x80010000
Closing network.
Starting program at 0x80010000
[ 0.000000] Linux version 3.9.11 (qubo@…) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2012.12 r37814) ) #2 Wed Aug 21 21:58:18 CST 2013
[ 0.000000] Detected Broadcom 0x6358 CPU revision a1
[ 0.000000] CPU frequency is 300 MHz
[ 0.000000] 64MB of RAM installed
[ 0.000000] registering 40 GPIOs
[ 0.000000] board_bcm963xx: Boot address 0xbe000000
[ 0.000000] board_bcm963xx: CFE version: d081.5003
[ 0.000000] bcm63xx_nvram: nvram checksum failed, contents may be invalid (expected 30303030, got 58fd7042)
[ 0.000000] board_bcm963xx: unknown bcm963xx board: HW556_BW_B
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0002a010 (Broadcom BMIPS4350)
[ 0.000000] Kernel panic - not syncing: unable to detect bcm963xx board

Attachments (0)

Change History (2)

comment:1 Changed 4 years ago by bbsoo7@…

after clear nvram at CFE.
the output from serial changed to this.
* Press any key to stop auto run (3 seconds) *
Auto run second count down: 0
boot kernel from be020100
Code Address: 0x80010000, Entry Address: 0x80010000
Decompression OK!
Entry at 0x80010000
Closing network.
Starting program at 0x80010000
[ 0.000000] Linux version 3.9.11 (qubo@…) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2012.12 r37814) ) #3 Wed Aug 21 23:17:04 CST 2013
[ 0.000000] Detected Broadcom 0x6358 CPU revision a1
[ 0.000000] CPU frequency is 300 MHz
[ 0.000000] 64MB of RAM installed
[ 0.000000] registering 40 GPIOs
[ 0.000000] board_bcm963xx: Boot address 0xbe000000
[ 0.000000] board_bcm963xx: CFE version: d081.5003
[ 0.000000] bcm63xx_nvram: nvram checksum failed, contents may be invalid (expected 30303030, got 79ce9963)
[ 0.000000] board_bcm963xx: unknown bcm963xx board: HW556_Bÿÿÿÿÿÿÿÿÿ <<<< here
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0002a010 (Broadcom BMIPS4350)
[ 0.000000] Kernel panic - not syncing: unable to detect bcm963xx board

comment:2 Changed 4 years ago by bbsoo7@…

haha, finally I got it work for me. I hope this can help others

after plug/unplug power cable several times. I found this in CFE output

if
[ 0.000000] board_bcm963xx: unknown bcm963xx board: HW556_B2 <<< it will add an extra 2 here so the kernel can not read it as HW556_B thus it failed to boot up.
so I just changed the board-id to "96358GW". then reboot.

output from CFE like this:

* GetHG556aBoardVersion = <0> *

Board IP address : 192.168.1.1
Host IP address : 192.168.1.55
Gateway IP address :
Run from flash/host (f/h) : f
Default host run file name : vmlinux
Default host flash file name : bcm963xx_fs_kernel
Boot delay (0-9 seconds) : 3
Board Id Name : 96358GW <<<< here.
Psi size in KB : 64
Number of MAC Addresses (1-32) : 10
Base MAC Address : 00:25:68:ed:df:d1
Ethernet PHY Type : Internal
Memory size in MB : 64
CMT Thread Number : 1

but the box can not boot up. then I changed board-id to "HW556" again. after reboot.the kernel reads board-id correctly.

1 23:17:04 CST 2013
[ 0.000000] Detected Broadcom 0x6358 CPU revision a1
[ 0.000000] CPU frequency is 300 MHz
[ 0.000000] 64MB of RAM installed
[ 0.000000] registering 40 GPIOs
[ 0.000000] board_bcm963xx: Boot address 0xbe000000
[ 0.000000] board_bcm963xx: CFE version: d081.5003
[ 0.000000] bcm63xx_nvram: nvram checksum failed, contents may be invalid (expected 30303030, got df2bee62)
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0002a010 (Broadcom BMIPS4350)
[ 0.000000] board_bcm963xx: board name: HW556_B <<<< here.
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 04000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x03ffffff]

then the Hg556a with MX29LV128DB flash chip boots up.

sorry about my poor English.

Add Comment

Modify Ticket

Action
as new .
Author


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

 
Note: See TracTickets for help on using tickets.