OpenWrt Forum Archive

Topic: ASMAX AR1004g

The content of this topic has been archived on 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello. According to wiki to this asmax AR1004g can upload open wrt. I have problem because when firmware has been upgraded and router restarting, nothing happens. All commands are not working  (ssh, telnet). I don't know wheter i choose wrong image.

Please for help.

(Last edited by Kitan on 31 Jul 2011, 14:13)

My router is not bricked. Original firware work, but when i upload Open Wrt it does not work.

(Last edited by Kitan on 30 Jul 2011, 13:05)

Kitan wrote:

All command not work (ssh, telnet).

Thats commonly regarded as brick (imho). You better provide more usable information so people understand your problem.

According to http://wiki.openwrt.org/toh/asmax/ar_1004g .

Description upload firmware:

Press and hold RESET button
Turn on router, after 10-15 sec release RESET
Web browser ? 192.168.1.1 and upload firmware

I behave according to description. After instaling Open WRT, router bricks. After second reset and orginal firmware upload everything works. Do i have to use Serial Port and flash it by TFTP?

(Last edited by Kitan on 31 Jul 2011, 14:11)

Please provide the url of the openwrt-image you flashed. Besides that, ping the router (also using different ethernet ports) to see if low level network is working. If that doesn't help, getting serial console up and running will help to find out what's going wrong. Make sure you read the wiki first.

Relocation Factor:         I:00000000 - D:00000000

Board IP address                  : 192.168.1.1:ffffff00
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)          : 1
Board Id (0-8)                    : 96348GW-10
Number of MAC Addresses (1-32)    : 11
Base MAC Address                  : 0c:0a:0a:0a:0a:0a
PSI Size (1-64) KBytes            : 24
Flash Block Size (1-128) in KBytes: 0
Auxillary File System Size Percent: 0

udp_send finished
No answer .auto boot ...
*** Press any key to stop auto run (1 seconds) ***
Auto run second count down: 0
Booting from only image (0xbfc10000) ...
Code Address: 0x80010000, Entry Address: 0x80010000
Decompression OK!
Entry at 0x80010000
Closing network.
Starting program at 0x80010000
Linux version 2.6.32.27 (jow@nd-build-02.linux-appliance.net) (gcc version 4.3.3 (GCC) ) #8 Fri Jul 15 05:02:16 CEST 2011
Detected Broadcom 0x6348 CPU revision b0
CPU frequency is 256 MHz
16MB of RAM installed
registering 37 GPIOs
board_bcm963xx: CFE version: 1.0.37-10.3
board_bcm963xx: invalid nvram checksum
bootconsole [early0] enabled
CPU revision is: 00029107 (Broadcom BCM6348)
Kernel panic - not syncing: unable to detect bcm963xx board

With Serial...

Kitan wrote:

Kernel panic - not syncing: unable to detect bcm963xx board

Seems like you need to try another image. Please post the url of the image you used so far.

That image should work. I saw there is a wiki entry for a v2 of that device (not yet containing valid information), so checking which version you've got might get into the right direction.
Besides,

Kitan wrote:

board_bcm963xx: CFE version: 1.0.37-10.3
board_bcm963xx: invalid nvram checksum

is something that now caught my attention. So either your nvram got corrupted, or it is newer than the board specific module. In that case it would be a good idea to dump it and check with the used algorithm. Or maybe there is a way to restore default values of nvram.
One other thing to test would be a trunk image, which is more up to date. This is the url: http://downloads.openwrt.org/snapshots/ … fs-cfe.bin

board_bcm963xx: Boot address 0xbfca0rd_bcm963xx: CFE version: 1.0.37-10.3
board_bcm963xx: invalid nvram checksum
bootconsole [early0] enabled
CPU revision is: 00029107 (Broadcom BMIPS3300)
Kernel panic - not syncing: unable to detect bcm963xx board

The discussion might have continued from here.