Aruba AP-303

The Aruba AP-303 is a 2×2 802.11ac Wave 2 access point. It is fairly powerful with a quad-core ARM processor and 512 MB of memory. The Aruba Instant On AP11 is a much cheaper version of this device and is based on the same platform, the OpenWrt firmware for Aruba AP-303 can also be flashed onto the Aruba Instant On AP11.

Generic Router

ModelVersionSoCCPU MHzFlash MBRAM MBWLAN HardwareWLAN2.4WLAN5.0100M portsGbit portsModemUSB
AP-303Qualcomm IPQ4029716128NAND512Qualcomm Atheros IPQ4019b/g/na/n/ac-1--

You will need a special console cable (see below in Section “Serial”) and an UART-Adapter:

  1. Get the OpenWrt initramfs image. Rename it to ipq40xx.ari and put it into the TFTP server root directory. Configure the TFTP server to be reachable at 192.168.1.75/24. Connect the machine running the TFTP server to the ethernet port of the access point. In case, you connect your server via DHCP like your internet provider router, the exact setting of the IP is optional. You just have to know it and change it in step 3 accordingly.
  2. Connect to the serial console. Interrupt autobooting by pressing Enter when prompted. In case, you connected the AP-303 to your DHCP-Router enter the following first into the serial console to get the AP-303 IP-address>:
       $ dhcp
  3. Configure the bootargs and bootcmd for OpenWrt
       $ setenv bootargs_openwrt "setenv bootargs console=ttyMSM1,9600n8"
       $ setenv nandboot_openwrt "run bootargs_openwrt; ubi part aos1; ubi read 0x85000000 kernel; set fdt_high 0x87000000; bootm 0x85000000"
       # Substitute the following IP-addresses as mentioned Step 1 and 2, in case, you are using DHCP.
       $ setenv ramboot_openwrt "run bootargs_openwrt; setenv ipaddr 192.168.1.105; setenv serverip 192.168.1.75; netget; set fdt_high 0x87000000; bootm" 
       $ setenv bootcmd "run nandboot_openwrt"
       $ saveenv
  4. Load OpenWrt into RAM
    $ run ramboot_openwrt

    (Note that after the TFTP transfer completes, there will be an error displayed: “Invalid image format version”. It can be ignored.)

  5. After OpenWrt booted, transfer the OpenWrt sysupgrade image to the /tmp folder on the device.
  6. Flash OpenWrt
    $ ubidetach -p /dev/mtd1
    $ ubiformat /dev/mtd1
    $ sysupgrade -n /tmp/openwrt-sysupgrade.bin

In case you are using DHCP, in the console of Openwrt change “option proto 'static'” to “option proto 'dhcp'” for the lan interface via

$ vi /etc/config/network
# Then reload and connect. 
$ service network reload

Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

The Aruba AP-303 has the following buttons:

BUTTON Event
Reset reset
General
Brand Aruba
Model AP-303
Versions
Device Type WiFi AP
Availability unknown 2019
Comments - general
OpenWrt Support
Supported Since Commit https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=102c8c55f217606cdbdc9a449667e034676b3e75
Supported Since Release 21.02.0
Supported Current Release 21.02.3
Unsupported
Hardware
Bootloader U-Boot
Target ipq40xx
System-On-Chip
CPU MHz 716
Flash MB 128NAND
RAM MB 512
Network
Ethernet 100M ports -
Ethernet Gbit ports 1
Switch -
Modem -
VLAN Yes
Comments - network ports
Wireless
WLAN 2.4GHz b/g/n
WLAN 5.0GHz a/n/ac
WLAN Hardware Qualcomm Atheros IPQ4019
Detachable Antennas -
Comments - WLAN
Interfaces
USB ports -
SATA ports -
Serial Yes
JTAG ¿
Comments - USB & SATA ports
Misc
LED count 2
Button count 1
Power supply 12 VDC, PoE 802.3af
Links
Forum Topic URL
WikiDevi URL
OEM device homepage URL https://www.arubanetworks.com/products/networking/access-points/303-series/
Firmware OEM Stock URL
Firmware OpenWrt Install URL https://downloads.openwrt.org/releases/21.02.3/targets/ipq40xx/generic/openwrt-21.02.3-ipq40xx-generic-aruba_ap-303-initramfs-fit-uImage.itb
Firmware OpenWrt Upgrade URL https://downloads.openwrt.org/releases/21.02.3/targets/ipq40xx/generic/openwrt-21.02.3-ipq40xx-generic-aruba_ap-303-squashfs-sysupgrade.bin
Edit the underlying data View/Edit data

Front:
Insert photo of front of the casing

Back:
Insert photo of back of the casing

Backside label:
Insert photo of backside label

Note: This will void your warranty!

Remove the 4 screwas on the back of the device. The metal casing can be lift up. The PCB is secured with a single screw in the middle of the PCB.

Main PCB:
Insert photo of PCB

port.serial general information about the serial port, serial port cable, etc.

To connect to the serial console, you can solder to the labled pads next to the USB port or use your Aruba supplied UART adapter.

Do NOT plug a standard USB cable into the Console labled USB-port! Aruba/HPE simply put UART on the micro-USB pins. You can solder (or luster clamp or bread-board) yourself an adapter cable by stripping an old Micro-USB-B-cable:

USB pin UART usage
VCC NC
D+ TX
D- RX
GND GND

The console setting in bootloader and OS is 9600 8N1. Voltage level is 3.3V. Cheap USB-UART Adapter have failed to work.

To enable a full list of commands in the U-Boot “help” command, execute the literal “diag” command.

None so far.

APBoot 2.5.0.2 (build 70487) Built: 2019-05-14 at 12:27:57 Model: AP11 DRAM: 512 MiB Flash: Detected MX25R3235F: with write protection total 4 MiB NAND: 128 MiB Power: DC Net: eth0 Radio: ipq4019#0, ipq4019#1 FIPS: passed Hit <Enter> to stop autoboot: 2 1 0 Checking image @ 0x0 Copying image from 0x84000000 Image is signed; verifying checksum... passed SHA2 Signature available Signer Cert OK Policy Cert OK RSA signature verified using SHA2. Uncompressing Kernel Image ... OK [ 0.000000] [ 0.000000] Instant On [ 0.000000] ArubaOS Version 1.4.1.0 (build 74478 / label #74478) [ 0.000000] Built by p4build@pr-hpn-build01 on 2020-02-27 at 23:01:18 AST (gcc version 5.3.0) [ 0.000000] [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d [ 0.016929] SMP: Total of 4 processors activated (384.00 BogoMIPS). [ 0.052360] i2c-gpio driver registered [ 2.464873] 3 ofpart partitions found on MTD device 7980000.qcom,nand [ 2.533728] Creating 3 MTD partitions on "7980000.qcom,nand": [ 2.602465] 0x000000000000-0x000002000000 : "aos0" [ 2.701779] 0x000002000000-0x000004000000 : "aos1" [ 2.788467] 0x000004000000-0x000008000000 : "ubifs" [ 2.922421] m25p80 spi0.0: found mx25r3235f, expected n25q128a11 [ 3.010854] Found AT97SC3203 on MSM-I2C-v2-adapter [ 3.066098] Key type dns_resolver registered [ 3.106833] Registering SWP/SWPB emulation handler [ 4.430268] Watchdog run with TZ supported gpio reset [ 4.512679] Starting Kernel SHA1 KAT ... [ 4.547147] Completed Kernel SHA1 KAT [ 4.594172] Starting Kernel HMAC-SHA1 KAT ... [ 4.644239] Starting Kernel DES KAT ...[ 4.689957] Completed Kernel DES KAT [ 4.733695] Starting Kernel AES KAT ... [ 4.777397] Completed Kernel AES KAT [ 4.777397] [ 4.840923] Starting Kernel AESGCM KAT ... [ 4.887747] Completed Kernel AESGCM KAT [ 4.937068] Completed Kernel HMAC-SHA1 KAT Thu Jan 1 00:00:00 PST 1970 Populate AP type info Domain Name: InstantOn.arubainstanton.com Current OEM Name : Instant On Disabling ipv6 for devices by default AP-type has_ble_support: ONBOARD. IPv6 capability is supported for devices No panic info available Writing /dev/ttyMSM1 into /tmp/ble_port Enabling ble_daemon and ble_relay via nanny apfcutil: sector CACHE: Cache uninitialized apfcutil: sector RAP: Cache uninitialized apfcutil: sector FAT: Cache uninitialized apfcutil: sector DRT: Cache uninitialized apfcutil: sector SCRATCH: Cache uninitialized Check backup ENV. apfcutil: sector MESH Prov: Cache uninitialized Installing glenmorangie ethernet driver [ 15.999045] edma module_init Enter non-FIPS mode Cfg len is 0 Configuration file is empty, turning on default services... Mesh is enabled by default on Instant-On The AP is in factory default status Starting watchdog process... Aruba watchdog daemon started [4 thread(s)] touching file /tmp/ip_mode_0 Enable IPv6 for the Master v6 discovery Enabling DHCPv6 ... ble_ready NOT present @init .... Checking country code. Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet Ethernet uplink not active yet No uplink active. Becoming Mesh Point killall: ble_daemon: no process killed Factory default ap without uplink, it will become a point. copy[ 51.902199] uol: module license 'Proprietary' taints kernel. [ 51.978267] Disabling lock debugging due to kernel taint ing bootuplog ... [ 52.042806] uol_init_driver:344 HW offload not applicable, AP will use cutting through path! allow PAPI set device anul0 mtu to 2000 notify asap_mod 3g no present... AP is not onboarded. SMB iap master unset. Enabling IPv6 for devices... IP mode is v4-only... apdot1x authentication is not enabled Starting DHCP Compressing all files in the /etc/httpd directory... Done. Starting Webserver bind: Transport endpoint is not connected bind: Transport endpoint is not connected bind: Transport endpoint is not connected Put ntpdate to the nannylist. AP rebooted caused by cold HW reset(power loss) shutting down watchdog process (nanny will restart it)... <<<<< Welcome to the Access Point >>>>> Power supply mode is DC, USB Modem is not present. Completed SW FIPS KAT test ble_ready NOT present @init ....


COPY HERE THE BOOTLOG ONCE OPENWRT IS INSTALLED AND RUNNING


Space for additional notes, links to forum threads or other resources.

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2022/05/03 15:39
  • by tmomas