OpenWrt support for Watchguard AP320 (aka Mojo C-75)

[diego-spw]

Hi i have a bunch of Watchguard AP320 that have expired license but non the less its a pretty capable AP, this model is exactly the same as mojo C75 so i try following this guide Git-Hub that converts them to OpenWRT but i cannot access the boot when connected with a console cable i see " Hit enter key to stop autoboot: 0 " but it starts at 0 so there is no way to access even pressing keys before, i got the same results with the internal serial and a FTDI cable. I have attached the complete log.
Any advice will be thankful.

U-Boot 1.1.4 (Jun 22 2014 - 15:02:11)

ap135 - Scorpion 1.0DRAM:
sri
Scorpion 1.0
ath_ddr_initial_config(200): (32bit) ddr2 init
tap = 0x00000003
Tap (low, high) = (0x3, 0x1d)
Tap values = (0x10, 0x10, 0x10, 0x10)
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 208k for U-Boot at: 87fc8000
Reserving 192k for malloc() at: 87f98000
Reserving 44 Bytes for Board Info at: 87f97fd4
Reserving 36 Bytes for Global Data at: 87f97fb0
Reserving 128k for boot params() at: 87f77fb0
Stack Pointer at: 87f77f98
Now running in RAM - U-Boot at: 87fc8000
Flash Manuf Id 0xc2, DeviceId0 0x20, DeviceId1 0x18
flash size 16MB, sector count = 256
Flash: 32 MB
*** Warning *** : PCIe WLAN Module not found !!!
In:    serial
Out:   serial
Err:   serial
Net:   ath_gmac_enet_initialize...
athrs_sgmii_res_cal: cal value = 0xe
Fetching MAC Address from 0x87feaa8c
Fetching MAC Address from 0x87feaa8c
ath_gmac_enet_initialize: reset mask:c02200
Scorpion  ----> S17 PHY *
Vlan config...
s17 phy0 register value 0x00004140
TEST: FINAL REG VAL after TX Calibration - 0x86000000
TEST: FINAL XMII VAL after RX Calibration - 0x96000000
TEST: FINAL ETH_CFG VAL after RX Calibration - 0x00000001
athrs17_reg_init: complete
: cfg1 0x80000000 cfg2 0x7335
eth0: 00:90:7f:ef:6e:3f
eth0 up
athrs17_reg_init_wan done
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x800c0000 cfg2 0x7214
eth1: 00:90:7f:ef:6e:3e
eth1 up
eth0, eth1
Setting 0x18116290 to 0x50a1a14f
Hit enter key to stop autoboot:  0
## Booting image at 9f060000 ...
   Image Name:   Linux Kernel Image
   Created:      2020-05-14  14:01:07 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1169491 Bytes =  1.1 MB
   Load Address: 80002000
   Entry Point:  80266110
   Verifying Checksum at 0x9f060040 ...OK
   Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80266110) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...

ARISTA DEBUG_LOG [590] [start_kernel]
DEBUG_LOG [595] [setup_arch]
Booting QCA955x
DEBUG_LOG [492] [arch_mem_init]

[frollic]

start by verifying your serial cable, short the RX and TX pins/connectors, and you should be able to see yourself type in your serial terminal window.

Should should probably hammer the enter key, before you actually see the press enter text on the screen.

[diego-spw]

I have test it and the console and i see myself in the terminal i have also try presing the key many times before and same result also by holding the key.
Thanks for your response.

[tmn505]

Hi, there are newer, less invasive, instructions to flash this access point: https://git.openwrt.org/0d96d36841e817f368e86d4af725570d757cb0ca. The snapshot images are present at: https://downloads.openwrt.org/snapshots/targets/ath79/generic.

Your bootlog is really short, is that all that is being output until the device is fully booted? I don't know how it was managed, by controller or standalone, but try to set all debugging and access options in web interface of controller or access point. If that doesn't help:

1. disassemble the unit,
2. connect to serial port,
3. apply power,
4. before Hit enter key to stop autoboot: 0 message appears, short two pins (7 and 8) from SPI flash chip (see attached image),
5. keep them shorted until bootloader loads the kernel and fails CRC checksum,
6. after failed kernel load You should be in U-Boot command line,
7. there run setenv bootdelay 3 and saveenv, so next time You won't have to repeat this whole procedure.
8. use installation instructions from the commit message adding support for this device.

P.S. fix the topic title.

[diego-spw]

Thanks your method work!!! I´m now trying set the ip address and upload a the files i´m having some problems but i think i can fix the by myself.

Again thanks for all your help and so fast.

[diego-spw]

I´m sorry about the topic, is it now ok?

[tmn505]

I had in mind the model number (AP 230 vs AP320) when asking to change the title, but this one is also good.

[diego-spw]

After a lot of efort I finaly manage to acces via web ui. Tanks for all your help.