OpenWrt Forum Archive

Topic: Aruba AP support

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

Has anyone tried to install on the Aruba (managed) access points? The AP-61 I have runs on an Atheros AR2313 processor with 4MB flash and 32MB RAM, with one ethernet port (and SoE/PoE), one radio and diversity antenna. The AP-70 runs on an IDT RC32434 with 4MB flash and 32MB RAM, two ethernet ports, two Atheros 5212's with four antennae (2xB/G and 2xA). They both run linux already.

Boot output of the AP-61:

APBoot 1.5.5 (build taylor@harpua-ENG.0000)de devices: hda                         
Po
Built: 2006-02-24 18:29:36 (with gcc 3.3.1)                                           

CPU:   AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache                                                             
Board: Merlot, Local Bus at 90 MHz                                 
DRAM:  32 MB           
POST:  passed             
FLASH: 4 MB           

Hit <Enter> to stop autoboot:  0
Loading FLASH image @ 0xbfc40000... not present
Loading FLASH image @ 0xbfc80000...
Verifying checksum...
Booting image...
ARUBA MERLOT

Aruba Networks Model 6x
ArubaOS Version 3.1.1.0 (build 15717 / label #15717)
Built by p4build@antigua on 2007-07-26 at 19:45:52 PDT (gcc version 3.4.1)
Calibrating delay loop... 179.20 BogoMIPS
Memory: 25380k/32768k available (1550k kernel code, 7388k reserved, 2516k data,
188k init, 0k highmem)
Initializing Cryptographic API
physmap flash device: 400000 at 1fc00000
Macronix Flash MX29LV320A (Top) (User Locked)
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
NET4: Ethernet Bridge 008 for NET4.0
bond0: Atheros AR2313: 00:0b:86:xx:xx:xx, irq 4
Getting an IP address...

Boot output of the AP-70:

APBoot 1.5.5 (build taylor@harpua-ENG.0000)
Built: 2006-02-24 18:33:47 (with gcc 3.3.1)

CPU:   RC32434 MIPS-32 at 266 MHz: 8 kB I-Cache 8 kB D-Cache
Board: Muscat, Local Bus at 133 MHz
DRAM:  32 MB
POST:  passed
FLASH: 4 MB
PCI:   scanning bus0 ...
       dev fn venID devID class  rev MBAR0    MBAR1    MBAR2    MBAR3
[deleted]
Net:   en0 en1 br0 lo0
Bridg: en0 en1

Hit <Enter> to stop autoboot:  1
................................                               

Aruba Networks             
ArubaOS Version 3.3.1.6 (build 18012 / label #18012)                                                   
Built by p4build@bermuda on 2008-03-26 at 19:07:05 PDT (gcc version 3.4.3)                                                                         
BOARD - Muscat             
CPU frequency 266.00 MHz                       
Using 133.000 MHz high precision timer. cycles_per_jiffy=266000                                                               
Memory: 26192k/32768k available (1832k kernel code, 6560k reserved, 404k data, 2                                                                               
852k init, 0k highmem)                     
available.           
PCI: Initializing PCI                     
irq fixup: slot 10, pin 1, irq 145                                 
irq fixup: slot 11, pin 1, irq 146                                 
irq fixup: slot 11, pin 2, irq                             
irq fixup: slot 11, pin 3, irq 146zone for this machine [yes/no/quit
irq fixup: slot 12, pin 1, irq 147                                 
irq fixup: slot 13, pin 1, irq 148ation so that time zone rules ca 
wdt: registered with refresh                     
Pleas
physmap flash device: 400000 at 1fc00000                       
1) Africa     
AMD Flash AM29LV320D (Top) (Unknown locking)             
4) Arctic Ocean             
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank) Australia             
8) Europe         
9) Indian Oc
Amd/Fujitsu Extended Query Table at 0x0040         
11) none - I want to specify the
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.1 (AR5212, AR5312, RF5111, RF5112, RF2413, RF5413)
ath_rate_atheros: Version 2.0.1
Copyright (c) 2001-2004 Atheros Communications, Inc, All Rights Reserved
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
wifi0: Base BSSID 00:0b:86:xx:xx:xx, 16 available BSSID(s)
edev->dev_addr=00:0b:86:xx:xx:xx
wifi0: AP type AP-70, radio 0, max_bssids 16
wifi0: Atheros 5212: mem=0x50010000, irq=147
wifi1: Base BSSID 00:0b:86:xx:xx:xx, 16 available BSSID(s)
edev->dev_addr=00:0b:86:xx:xx:xx
wifi1: AP type AP-70, radio 1, max_bssids 16
wifi1: Atheros 5212: mem=0x50020000, irq=148
Ethernet port 1 mode: active-standby
Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: enslaving eth0 as an active interface with an up link.
bonding: bond0: enslaving eth1 as a backup interface with a down link.
Getting an IP address...
bonding: bond0: link status definitely down for interface eth0, disabling it
bonding: bond0: now running without any active interface !

I am trying to use the atheros platform under kamikaze. Both with the pre-built images, and building my own for the risc (atheros) target, I get the same checksum error:

APBoot 1.5.5 (build taylor@harpua-ENG.0000)
Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

CPU:   AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
Board: Merlot, Local Bus at 90 MHz
DRAM:  32 MB
POST:  passed
FLASH: 4 MB
Net:   en0 lo0

Hit <Enter> to stop autoboot:  0
apboot> tftpboot
Loading elf file: 192.168.4.23:mips.ari
Loading: ################################################################
         ################################################################
         ################################################################
         ############################
Verifying checksum... failed
tftpboot failed, retrying in one second       
[...]

I notice that there used to be an aruba-2.6 target with some code for the Merlot board I'm using, but it's now removed (presumably the new HAL should cover this). Any developers want to comment?

BatonRing wrote:

I am trying to use the atheros platform under kamikaze. Both with the pre-built images, and building my own for the risc (atheros) target, I get the same checksum error:

APBoot 1.5.5 (build taylor@harpua-ENG.0000)
Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

CPU:   AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
Board: Merlot, Local Bus at 90 MHz
DRAM:  32 MB
POST:  passed
FLASH: 4 MB
Net:   en0 lo0

Hit <Enter> to stop autoboot:  0
apboot> tftpboot
Loading elf file: 192.168.4.23:mips.ari
Loading: ################################################################
         ################################################################
         ################################################################
         ############################
Verifying checksum... failed
tftpboot failed, retrying in one second       
[...]

I notice that there used to be an aruba-2.6 target with some code for the Merlot board I'm using, but it's now removed (presumably the new HAL should cover this). Any developers want to comment?

Hi,

I got a few AP61 and no serial cable for them. Is that RS 232?
I have a manual that says that pairs 5&4 and 7&8 are used for console connection.
From your output I understand that you have interrupted the boot sequence and tried to load a custom firmware file.
Is it possible to change the loader from APBOOT> prompt?
Were you able to load a custom FW? If not, do you have any suggestions or ideas?
Is there a JTAG interface?

Thanks,


Anton

(Last edited by antonvp on 16 Oct 2008, 21:00)

The serial connector is Serial over Ethernet. You connect the serial cable in series with the ethernet connection. You could get a connector from Aruba (like I did), or it should be pretty easy to build your own if you have an RJ45 crimper and a female DB-9 housing.

I did get the OpenWRT image to boot on an AP-61, but it needs to run off of ramdisk if it's to be booted with a remote image. I didn't quite figure out how to flash the image onto the device to use a native filesystem. At that point I sort of lost interest in the project, given that I had a couple of other OpenWRT-capable devices.

I'll probably pick it up soon, as we're tearing down one wireless network and I'll have a significant number of purpose-less AP-71's lying around.

I am also trying to use some AP61's.

I have been able to erase/write to the flash (using an Aruba image), but have not been able to get an image of my own to pass the verification test.  Wanna trade?  smile

Nobody can help us, sad
The Ap-60  hmm

(Last edited by lei0101 on 23 Feb 2009, 01:38)

The discussion might have continued from here.