[SOLVED]Flashing openwrt to Aruba AP-303H issue

I am following https://openwrt.org/toh/aruba/ap-303h

I have got the serial console working for Aruba AP-303H. I am powering AP-303H from POE Switch using E0 port (back side of AP)

  • I assigned IP address 192.168.1.75 to Windows computer NIC.
  • Downloaded openwrt firmware and renamed to ipq40xx.ari
  • Downloaded tftpd64 and ran it by choosing source directory as where I kept pq40xx.ari file and chose server interface as 192.168.1.75
  • Connected the serial console using putty
  • Connected ethernet of PC to E0/PT port (under down side) of AP-303H
  • Connected another ethernet cable from POE switch to AP-303H E0 port (back side of AP).
  • AP started booting (serial console showed messages) immediately pressed enter to overide autoboot.
  • Ran below commands,
$ setenv bootargs_openwrt "setenv bootargs console=ttyMSM0,9600n8"
$ setenv nandboot_openwrt "run bootargs_openwrt; ubi part aos1; ubi read 0x85000000 kernel; set fdt_high 0x87000000; bootm 0x85000000"
$ 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
$ run ramboot_openwrt

But I am stuck at Retry count exceeded; starting again Full log below.
What am I doing wrong?
I noticed that, ethernet jack of PC is not powered when connecting it to E0/PT port (under down side) of AP-303H.

Hit <Enter> to stop autoboot:  0
apboot> setenv bootargs_openwrt "setenv bootargs console=ttyMSM0,9600n8"
apboot> setenv nandboot_openwrt "run bootargs_openwrt; ubi part aos1; ubi read 0x85000000 kernel; set fdt_high 0x87000000; bootm 0x85000000"
apboot> setenv ramboot_openwrt "run bootargs_openwrt; setenv ipaddr 192.168.1.105; setenv serverip 192.168.1.75; netget; set fdt_high 0x87000000; bootm"
apboot> setenv bootcmd "run nandboot_openwrt"
apboot> saveenv
Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done
apboot> run ramboot_openwrt
eth0 up: 1 Gb/s full duplex
Using eth0 device
TFTP from server 192.168.1.75; our IP address is 192.168.1.105
Filename 'ipq40xx.ari'.
Load address: 0x84000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
Using eth0 device
TFTP from server 192.168.1.75; our IP address is 192.168.1.105
Filename 'ipq40xx.ari'.
Load address: 0x84000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
Using eth0 device
TFTP from server 192.168.1.75; our IP address is 192.168.1.105
Filename 'ipq40xx.ari'.
Load address: 0x84000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
Using eth0 device
TFTP from server 192.168.1.75; our IP address is 192.168.1.105
Filename 'ipq40xx.ari'.
Load address: 0x84000000
Loading: T T
Abort
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Firewall on the TFTP host ?
Wrong interface selected in TFTP, it'll also auto switch to 127.0.0.1 if the signal dips on the AP side.

S

So I figured the tftp part (tftp server had to be reachable via E0 poe port itself) and now AP found my TFTP server and it flashed openwrt and I plugged in another cable at E1 port of AP and I was able reach opewrt page via browser using 192.168.1.1.

However there is instruction 7,

  1. After OpenWrt booted, transfer the OpenWrt sysupgrade image to the /tmp folder on the device. You will need to plug into E1-E3 ports of the access point to reach OpenWrt, as E0 is the WAN port of the device.

I am not able to understand how to transfer the OpenWrt sysupgrade image to /tmp directory.

Also without doing above, I rebooted and now console logs shows as below,

APBoot 2.4.0.8 (build 64221)
Built: 2018-03-28 at 20:30:14

Model: AP-303H
DRAM:  512 MiB
Flash: Detected MX25L3205D: total 4 MiB
NAND:  Detected MX35LFxGE4AB: total 128 MiB
Power: 802.3at POE
Net:   eth0
Radio: ipq4029#0, ipq4029#1
Reset: cold
FIPS:  passed

Hit <Enter> to stop autoboot:  0
Volume kernel not found!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
apboot>

That was very stupid of me to ask!
I took an SCP session and did rest of the steps.
Now all good.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.