Reply

Re: Netgear WNDAP 360 - failed connection to WC9500 Controller

LewisT1
Aspirant

Netgear WNDAP 360 - failed connection to WC9500 Controller

Hi,

 

I have 3 x WNDAP360 Access Points that now have thesame issue - essentially the firmware image is corrupt.

2 of these corruption have occured during a reboot of the access point after an upgrade of the firmware on the WC9500 controllers. The third occured after the Access Point was successfully reset to default, followed by addition to the WC9500 controller. After successful installation of the controller firmware on the Access Point and and switching it off for installation in situ, it was found to be non-operational on power up

No amount of trying to reset the access points will fix the issue.

 

We have another 119 fully functional WNDAP360s and WAC720s so the issue is limited. There are 2 WC9500 controllers are on Firmware Version 6.5.5.24

 

If I serial on to each device it becomes clear what the issue is:

 

BAD CRC (see below)

 

U-Boot 1.1.4 dni-1.07 (Jul 7 2009 - 14:17:28)

AP94 (ar7100) U-boot 0.0.12
DRAM: b8050000: 0xc0140180
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 228k for U-Boot at: 87fc4000
Reserving 192k for malloc() at: 87f94000
Reserving 56 Bytes for Board Info at: 87f93fc8
Reserving 36 Bytes for Global Data at: 87f93fa4
Reserving 128k for boot params() at: 87f73fa4
Stack Pointer at: 87f73f88
Now running in RAM - U-Boot at: 87fc4000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash: 8 MB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: ag7100_enet_initialize...
: cfg1 0xf cfg2 0x7014
VSCXXX Found 0 unit 0:0 phy_addr: 1 id: 004dd04e
PHY: Atheros AR8021
eth0: 00:03:7f:e0:00:96
eth0 up
eth0
Manu data is valid!
### main_loop entered: bootdelay=4

### main_loop: bootcmd="bootm 0xbf050000"
Enter SPACE to drop into boot loader: 0
ar7100>

 

I have been following this guide:

 

https://community.netgear.com/t5/Business-Wireless/WNDAP360-Power-light-is-blinging/m-p/1694131/high...

which appears to describe my issue exactly and how to resolve.

I have attempted the following using both V3.7.11.4 and V2.1.12 firmware and in each case teh result is the same:

  1. Decompress the WNDAP360 firmware
  2. Should have 4 files inside, 2 files are kernel and OS, 2 files are md5 checksum
  3. Change PC IP address to 192.168.1.10, start TFTP server, locate the decompressed file in TFTP server
  4. Connect WNDAP360 LAN port
  5. Connect the console port to PC thru RS232 and start Putty
  6. Type in following command
  7. < >Erase 0xbf050000 +0x710000
  8. -> tftpboot 0x80060000 vmlinux.gz.ulmage
  9. > cp.b 0x80060000 0xbf050000 0x100000
  10. -> tftpboot 0x80060000 rootfs.squashfs
  11. -> cp.b 0x80060000 0xbf150000 0x610000
  12. -> bootm 0xbf050000

All of the above complete without issue. Onc ethe Access Points boot I get teh following errors:

 

U-Boot 1.1.4 dni-1.07 (Jul 7 2009 - 14:17:28)

AP94 (ar7100) U-boot 0.0.12
DRAM: b8050000: 0xc0140180
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 228k for U-Boot at: 87fc4000
Reserving 192k for malloc() at: 87f94000
Reserving 56 Bytes for Board Info at: 87f93fc8
Reserving 36 Bytes for Global Data at: 87f93fa4
Reserving 128k for boot params() at: 87f73fa4
Stack Pointer at: 87f73f88
Now running in RAM - U-Boot at: 87fc4000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash: 8 MB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: ag7100_enet_initialize...
: cfg1 0xf cfg2 0x7014
VSCXXX Found 0 unit 0:0 phy_addr: 1 id: 004dd04e
PHY: Atheros AR8021
eth0: 00:03:7f:e0:00:96
eth0 up
eth0
Manu data is valid!
### main_loop entered: bootdelay=4

### main_loop: bootcmd="bootm 0xbf050000"
Enter SPACE to drop into boot loader: 0
## Booting image at bf050000 ...
Image Name:
Created: 2020-06-15 10:51:58 UTC
Image Type: MIPS Linux Kernel Image (gzip compressed)
Data Size: 997694 Bytes = 974.3 kB
Load Address: 80020000
Entry Point: 80214000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80214000) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...
▒Linux version 2.6.23-gc3f1d801-dirty (netgear@BEC-ESX3-VM-04) (gcc version 3.4.4) #1 Mon Jun 15 16:06:42 IST 2020
flash_size passed from bootloader = 8
arg 1: console=ttyS0,9600
arg 2: root=31:03
arg 3: rootfstype=jffs2
arg 4: init=/sbin/init
arg 5: mtdparts=ar7100-nor0:256k(uboot),64k(env),1024k(kernel),6208k(rootfs),512k(var),64k(manu-data),64k(art-data)
CPU revision is: 00019374
Determined physical RAM map:
memory: 08000000 @ 00000000 (usable)
Built 1 zonelists in Zone order. Total pages: 32512
Kernel command line: console=ttyS0,9600 root=31:03 rootfstype=jffs2 init=/sbin/init mtdparts=ar7100-nor0:256k(uboot),64k(env),1024k(kernel),6208k(rootfs),512k(var),64k(manu-data),64k(art-data)
Primary instruction cache 64kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
Cache parity protection disabled
PID hash table entries: 512 (order: 9, 2048 bytes)
Using 340.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 127488k/131072k available (1633k kernel code, 3444k reserved, 362k data, 124k init, 0k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
registering PCI controller with io_map_base unset
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
AR7100 GPIOC major 0
squashfs: version 3.3 (2007/10/31) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing enabled
serial8250: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A
serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A
RAMDISK driver initialized: 1 RAM disks of 16384K size 1024 blocksize
7 cmdlinepart partitions found on MTD device ar7100-nor0
Creating 7 MTD partitions on "ar7100-nor0":
0x00000000-0x00040000 : "uboot"
0x00040000-0x00050000 : "env"
0x00050000-0x00150000 : "kernel"
0x00150000-0x00760000 : "rootfs"
0x00760000-0x007e0000 : "var"
0x007e0000-0x007f0000 : "manu-data"
0x007f0000-0x00800000 : "art-data"
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x7371 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0xbc44 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x6044 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0xa8ff instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0xa844 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0xa2ff instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c: 0x0003 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x1759 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x4001 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000028: 0xe752 instead
Further such events for this erase block will not be printed
Empty flash at 0x00000070 ends at 0x00000074
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010000: 0xdf4f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010004: 0x505e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010008: 0x013e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001000c: 0xafb2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010010: 0x266e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010014: 0xbc6f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010018: 0x1b45 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001001c: 0x54a1 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010020: 0x5be2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010024: 0x75ca instead
Further such events for this erase block will not be printed
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0x1fe0 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x956f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020008: 0x2d0f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0xe473 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020010: 0xd708 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0xa5bd instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020018: 0xa341 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002001c: 0xc352 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020020: 0xd14d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020024: 0x9934 instead
Further such events for this erase block will not be printed
Old JFFS2 bitmask found at 0x00025b94
You cannot use older JFFS2 filesystems with newer kernels
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00030000: 0xfa4d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00030004: 0xd903 instead
......
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510008: 0x2fa2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0051000c: 0x86f1 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510010: 0xfa4a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510014: 0xf6a4 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510018: 0xf99a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0051001c: 0xa90c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510020: 0x346e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00510024: 0xbcc6 instead
Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 15, bad_blocks 0, c->nr_blocks 97
VFS: Cannot open root device "31:03" or unknown-block(31,3)
Please append a correct "root=" boot option; here are the available partitions:
1f00 256 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 1024 mtdblock2 (driver?)
1f03 6208 mtdblock3 (driver?)
1f04 512 mtdblock4 (driver?)
1f05 64 mtdblock5 (driver?)
1f06 64 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)

 

My question is this, How do I overcome this issue and restore teh access points to factory image so I can reuse them? There doesn't seem to be anything else wrong with the device beyond teh fact that I am clearly not resetting these back to factory image correctly

 

Thanks in advance

 

Lewis


Rebooting in 3 seconds..

 

 

 

Model: WNDAP360|ProSafe Wireless-N Access Point
Message 1 of 3
JohnC_V
NETGEAR Moderator

Re: Netgear WNDAP 360 - failed connection to WC9500 Controller

@LewisT1,

 

Welcome to our community! Smiley Happy

 

It seems that you are having issues with your access point. You may need to access the secret IP of the AP in order for you to gain access again on its GUI. Try to use the standalone firmware first and just re-discover it from your wireless controller once it is up and running.

 

I'll send you a private message.

 

Regards,

 

John

NETGEAR Community Team

Message 2 of 3
LewisT1
Aspirant

Re: Netgear WNDAP 360 - failed connection to WC9500 Controller

Hi John,

 

Thanks for ther response. Unfortunately there is no web panel to access, I don't think there is enough of a viable image on teh access points to load up the web panel.

 

I cannot ping the IP listed, or any other IP for that matter. The only way I can communicate with the access point is via Serial and TFTP for firmware imaging.

 

I am all open to further suggestions

 

Thanks

 

Lewis

Model: WNDAP360|ProSafe Wireless-N Access Point
Message 3 of 3
Top Contributors
Discussion stats
  • 2 replies
  • 321 views
  • 0 kudos
  • 2 in conversation
Announcements