OpenWrt Forum Archive

Topic: RB941-2nD (hAP lite) Support

The content of this topic has been archived between 2 Feb 2018 and 25 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.

Post #26
idahorazor
25 Apr 2016, 23:26

More hAP AC Lite progress!

I was able to initialize the 802.11ac radio. It has a QCA9887 which is not currently supported by ath10k. I have had to make changes to pci.c, hw.h, and core.c in ath10k as well as download: https://github.com/kvalo/ath10k-firmwar … 2.3.31.7-1

As a hack, I duplicated the QCA988X entries and modified the chip_id, rev_id, dev_id's for the QCA9887. I wasn't sure how to properly include a new firmware.bin into the packages so I let it load the QCA988x firmware-5.bin. Once I flashed OpenWRT on the board, I downloaded the QCA9887 firmware from https://github.com/kvalo/ath10k-firmwar … 2.3.31.7-1 and copied it over /lib/firmware/ath10k/QCA988X/hw
2.0/firmware-5.bin. I modified /etc/hotplug.d/firmware/11-ath10k-caldata so the boardname would show up and calibration data would be passed to ath10k if the firmware bin was loaded. Rebooting the board after these changes allowed ath10k to load the phy1 properly with the correct calibration data.

iw phy phy1 info
Wiphy phy1
        max # scan SSIDs: 16
        max scan IEs length: 199 bytes
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0x1 RX 0x1
        Configured Antennas: TX 0x1 RX 0x1
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x19e3
                        RX LDPC
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-7
                VHT Capabilities (0x338001b2):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                        RX antenna pattern consistency
                        TX antenna pattern consistency
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: not supported
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: not supported
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Frequencies:
                        * 5180 MHz [36] (23.0 dBm)
                        * 5200 MHz [40] (23.0 dBm)
                        * 5220 MHz [44] (23.0 dBm)
                        * 5240 MHz [48] (23.0 dBm)
                        * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5500 MHz [100] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5520 MHz [104] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5540 MHz [108] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5560 MHz [112] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5580 MHz [116] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5600 MHz [120] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5620 MHz [124] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5640 MHz [128] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5660 MHz [132] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5680 MHz [136] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5700 MHz [140] (23.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5720 MHz [144] (23.0 dBm) (radar detection)
                          DFS state: usable (for 21122 sec)
                          DFS CAC time: 60000 ms
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
        valid interface combinations:
                 * #{ AP, mesh point } <= 8,
                   total <= 8, #channels <= 1, STA/AP BI must match
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing

It appears scanning works as well:

iw dev wlan1 scan
BSS dc:9f:db:1b:63:d0(on wlan1)
        TSF: 1823008018207 usec (21d, 02:23:28)
        freq: 5180
        beacon interval: 100 TUs
        capability: ESS Privacy ShortPreamble (0x0031)
        signal: -47.00 dBm
        last seen: 2730 ms ago
        Information elements from Probe Response frame:
        SSID: BlueMeshNetworks-5.8G
        Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 
        DS Parameter set: channel 36
        Country: US     Environment: Indoor/Outdoor
                Channels [36 - 48] @ 17 dBm
                Channels [52 - 64] @ 23 dBm
                Channels [149 - 165] @ 30 dBm
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
        HT capabilities:
                Capabilities: 0x11ed
                        RX LDPC
                        HT20
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
        HT operation:
                 * primary channel: 36
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 0
                 * HT protection: no
                 * non-GF present: 0
                 * OBSS non-GF present: 0
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        Extended capabilities: 6
        WMM:     * Parameter version 1
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 70:56:81:cd:50:de(on wlan1)
        TSF: 790153011590 usec (9d, 03:29:13)
        freq: 5785
        beacon interval: 100 TUs
        capability: ESS Privacy SpectrumMgmt ShortSlotTime RadioMeasure (0x1511)
        signal: -86.00 dBm
        last seen: 130 ms ago
        Information elements from Probe Response frame:
        SSID: Dingle-AirPort
        Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 
        DS Parameter set: channel 157
        TIM: DTIM Count 1 DTIM Period 3 Bitmap Control 0x0 Bitmap[0] 0x0
        Country: US     Environment: Indoor/Outdoor
                Channels [36 - 48] @ 30 dBm
                Channels [149 - 165] @ 30 dBm
        Power constraint: 0 dB
        RSN:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        HT capabilities:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT RX MCS rate indexes supported: 0-23
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 157
                 * secondary channel offset: above
                 * STA channel width: any
                 * RIFS: 0
                 * HT protection: no
                 * non-GF present: 1
                 * OBSS non-GF present: 0
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        WPA:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: TKIP
                 * Authentication suites: PSK
        WMM:     * Parameter version 1
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec

When trying to start an AP mode, it appears to have an issue:

[20581.200000] ath10k_pci 0000:00:00.0: firmware crashed! (uuid 2e9dd975-3ef6-456b-9832-070eec0d8eb3)
[20581.210000] ath10k_pci 0000:00:00.0: qca988x hw2.0 (0x4100016d, 0x004000ff sub 0000:0000) fw 10.2.3.31.7-1 fwapi 5 bdapi 1 htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 1p
[20581.230000] ath10k_pci 0000:00:00.0: debug 1 debugfs 1 tracing 0 dfs 0 testmode 1
[20581.240000] ath10k_pci 0000:00:00.0: firmware register dump:
[20581.250000] ath10k_pci 0000:00:00.0: [00]: 0x4100016D 0x00000000 0x004146C8 0x004146C8
[20581.250000] ath10k_pci 0000:00:00.0: [04]: 0x004146C8 0x00060530 0x0000001F 0x00955A00
[20581.260000] ath10k_pci 0000:00:00.0: [08]: 0x0040AE04 0x00400000 0x00000007 0x00000000
[20581.270000] ath10k_pci 0000:00:00.0: [12]: 0x00000002 0xFFFFFFFF 0x00958360 0x0095836B
[20581.280000] ath10k_pci 0000:00:00.0: [16]: 0x809ACDE0 0x0040AD94 0x0040AE04 0x00400000
[20581.290000] ath10k_pci 0000:00:00.0: [20]: 0x00000000 0x00000000 0x00000000 0x0040E830
[20581.300000] ath10k_pci 0000:00:00.0: [24]: 0x809AC4E2 0x0040ADC4 0x00000001 0x0040AE04
[20581.300000] ath10k_pci 0000:00:00.0: [28]: 0x004133E0 0x00000001 0x0040AE08 0x00000000
[20581.310000] ath10k_pci 0000:00:00.0: [32]: 0x00000007 0x00000000 0x00000000 0x004133C8
[20581.320000] ath10k_pci 0000:00:00.0: [36]: 0x809B9C49 0x0040ADE4 0x00411568 0x0041158C
[20581.330000] ath10k_pci 0000:00:00.0: [40]: 0x00000001 0x00000000 0x00955A00 0x0040E840
[20581.340000] ath10k_pci 0000:00:00.0: [44]: 0x809B944C 0x0040AE04 0x00000001 0x00000000
[20581.340000] ath10k_pci 0000:00:00.0: [48]: 0x0040AE04 0x00000001 0x004133C8 0x004117AC
[20581.350000] ath10k_pci 0000:00:00.0: [52]: 0x809B9263 0x0040AEA4 0x0041ECF8 0x00411BC8
[20581.360000] ath10k_pci 0000:00:00.0: [56]: 0x004133C8 0x0040AE34 0x00411F08 0x00411F08
[20581.490000] ieee80211 phy1: Hardware restart was requested

I copied the ath10k-devel mailing list to see if they could help me. ath10k as is does not support this radio, hopefully with some small modifications it can...

Post #27
idahorazor
5 May 2016, 21:41

I just made some hAP AC progress as well, the switch is working!

Here is what is required so far to get gigabit ethernet to work:

The AR9337 switch swaps gmac0 with gmac06, the "mac06_exchange_dis = true" was the smoking gun!

It's not perfect, it seems like if ethernet link changes ( 1gbps to 100mbps ) it loses connectivity. I'm wondering if that's a driver issue, so I may need to pull the latest trunk and do some more testing.

static const struct ar8327_led_info rbhapac_leds_ar8327[] __initconst = {
        AR8327_LED_INFO(PHY0_0, HW, "mikrotik:green:wan"),
        AR8327_LED_INFO(PHY1_0, HW, "mikrotik:green:lan1"),
        AR8327_LED_INFO(PHY2_0, HW, "mikrotik:green:lan2"),
        AR8327_LED_INFO(PHY3_0, HW, "mikrotik:green:lan3"),
        AR8327_LED_INFO(PHY4_0, HW, "mikrotik:green:lan4"),
};

static struct ar8327_pad_cfg rbhapac_ar8327_pad0_cfg = {
        .mode = AR8327_PAD_MAC_RGMII,
        .txclk_delay_en = true,
        .rxclk_delay_en = true,
        .txclk_delay_sel = AR8327_CLK_DELAY_SEL1,
        .rxclk_delay_sel = AR8327_CLK_DELAY_SEL2,
        .mac06_exchange_dis = true,
};

static struct ar8327_pad_cfg rbhapac_ar8327_pad6_cfg = {
        /* Use the SGMII interface for the GMAC6 of the AR8337 switch */
        .mode = AR8327_PAD_MAC_SGMII,
        .rxclk_delay_en = true,
        .rxclk_delay_sel = AR8327_CLK_DELAY_SEL0,
};

static struct ar8327_led_cfg rbhapac_ar8327_led_cfg = {
        .led_ctrl0 = 0xc737c737,
        .led_ctrl1 = 0x00000000,
        .led_ctrl2 = 0x00000000,
        .led_ctrl3 = 0x0030c300,
        .open_drain = false,
};

static struct ar8327_platform_data rbhapac_ar8327_data = {
        .pad0_cfg = &rbhapac_ar8327_pad0_cfg,
        .pad6_cfg = &rbhapac_ar8327_pad6_cfg,
        .port0_cfg = {
                .force_link = 1,
                .speed = AR8327_PORT_SPEED_1000,
                .duplex = 1,
                .txpause = 1,
                .rxpause = 1,
        },
        .port6_cfg = {
                .force_link = 1,
                .speed = AR8327_PORT_SPEED_1000,
                .duplex = 1,
                .txpause = 1,
                .rxpause = 1,
        },
        .led_cfg = &rbhapac_ar8327_led_cfg,
        .num_leds = ARRAY_SIZE(rbhapac_leds_ar8327),
        .leds = rbhapac_leds_ar8327,
};

static struct mdio_board_info rbhapac_mdio0_info[] = {
        {
                .bus_id = "ag71xx-mdio.0",
                .phy_addr = 0,
                .platform_data = &rbhapac_ar8327_data,
        },
};
Post #30
ra1nb0w
7 Jun 2016, 15:24

thanks adron for your work! I tried the binary found on [0] the netboot works flawless but unfortunately when I reboot after sysupgrade the router doesn't start; every time it try to boot from net (failsafe rule). I tried with ttl but doesn't work on routerboot (ver. 3.32) and so I can't see why doesn't load the kernel. I checked that the boot loader is correctly set with rbcfg and seems that mdt[5-7] are correctly written.
Do you have some idea how I can debug this behavior?

Moreover, I tried to build openwrt-trunk (cloned today) with the patch found on [0] but I alway receive

Makefile:2658: *** empty variable name.  Stop.
Makefile:24: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:21: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:15: recipe for target '/home/rainbow/tmp/poi/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq' failed
make[2]: *** [/home/rainbow/tmp/poi/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq] Error 2
/home/rainbow/tmp/poi/include/toplevel.mk:178: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/rainbow/tmp/poi/include/toplevel.mk:192: recipe for target 'world' failed
make: *** [world] Error 2

with make -d m prereq V=99 I found that the bad line is

$(eval $(call BuildImage))

but obviously the problem is somewhere else.
Have you already run into this issue?

Again, thanks for your hard work!!

[0] https://wiki.openwrt.org/toh/mikrotik/rb941_2nd

Post #31
ra1nb0w
10 Jun 2016, 17:51

compilation problem fixed. was ': =' mistake on Makefile. But the router doesn't boot.

Post #32
Gannet
30 Aug 2016, 23:32

Hello, I booted my RB941 from tftp and then flashed it with 'openwrt-ar71xx-mikrotik-rb-941-2nd-squashfs-sysupgrade.bin' file. After that my router doesn't boot. What should I do now, does anybody can help, please?

Post #33
alexpacio
5 Sep 2016, 08:16

Hi,
I confirm that the system boots from tftp but it reboots continuely when flashed on NAND through sysupgrade.

Does anybody can help us to solve this problem?

Post #34
Gannet
22 Sep 2016, 23:46

Returned back to the stock firmware. It is very pity but Openwrt still not ready for this router. sad

Post #35
Gannet
1 Oct 2016, 16:50
ra1nb0w wrote:

compilation problem fixed. was ': =' mistake on Makefile.

What did you meant? What to fix in Makefile?

Recently tried to compile OpenWRT trunk with patches applied, but it fails:

~/mikrotik/openwrt$ make
Makefile:2657: *** empty variable name.  Stop.
Makefile:24: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:21: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:15: recipe for target '/home/eugene/mikrotik/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq' failed
make[2]: *** [/home/eugene/mikrotik/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq] Error 2
/home/eugene/mikrotik/openwrt/include/toplevel.mk:178: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/eugene/mikrotik/openwrt/include/toplevel.mk:192: recipe for target 'world' failed
make: *** [world] Error 2

(Last edited by Gannet on 1 Oct 2016, 17:04)

Post #36
martin.burianek
2 Oct 2016, 19:39

Hi a have the same problem.

Gannet wrote:
ra1nb0w wrote:

compilation problem fixed. was ': =' mistake on Makefile.

What did you meant? What to fix in Makefile?

Recently tried to compile OpenWRT trunk with patches applied, but it fails:

~/mikrotik/openwrt$ make
Makefile:2657: *** empty variable name.  Stop.
Makefile:24: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:21: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:15: recipe for target '/home/eugene/mikrotik/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq' failed
make[2]: *** [/home/eugene/mikrotik/openwrt/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_prereq] Error 2
/home/eugene/mikrotik/openwrt/include/toplevel.mk:178: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/eugene/mikrotik/openwrt/include/toplevel.mk:192: recipe for target 'world' failed
make: *** [world] Error 2
Post #37
cnlohr
27 Nov 2016, 02:48

Also running into the once-flashed-only-looks-for-netboot-servers problem.  Anyone know much about this?  Does it only effect some boards?

We are going to need to roll out a feature that is flat out impossible (From what I can tell) in the routerboard software. -- conditional DHCP, i.e. if the router doesn't have a WAN IP, it won't hand out DHCPs.

I am also frustrated by the whole UART no go at boot thing.

Post #38
Snakus
4 Dec 2016, 12:40

7zip for windows can extract firmware image files (except kernel)
You can check config there

Post #39
cnlohr
7 Dec 2016, 23:06

Check config?  I don't understand what I would be looking for/at?  I can boot the image just fine, it just won't install to the flash.

Post #40
anarchy99
8 Dec 2016, 22:33

someone can make an iperf test with both routeros and openwrt? i've read there's some quite bad wifi performance with hap lite..

Post #41
arbalesttsr
18 Dec 2016, 11:50

Hello, everyone. I also had a problem, when after flashing openwrt image to nand, router was going for bootloop.
Here are the Steps :
1. Restore the original mikrotik firmware using netinstall tool, and do a basic config via winbox, because after reflashing to routeros back again, router won't give you ip.
2. Open webfig (web config), and change sections mentioned.
    System → Routerboard → Settings → Boot device: Try ethernet once then NAND
    System → Routerboard → Settings → Boot protocol: DHCP
    System → Routerboard → Settings → Force Backup Booter: Checked (if supported by your routerboard - !IMPORTANT)    - it seemes that last setting is the key))
3. Reboot router from the webfig (IMPORTANT!), plug-in the cable from pc to wan port, and boot openwrt via tftp (it's better to do it all as quick as possible).
4.Flash sysupgrade image via web interface, and now it should be working with openwrt flashed to nand.

(Last edited by arbalesttsr on 18 Dec 2016, 12:03)

Post #42
f00b4r0
3 Jan 2017, 21:46

Hi

I managed to update the author's patches to current trunk (I can upload the diff somewhere if necessary).

I built and successfully booted OpenWRT r50039 on my hAP lite, however I can't seem to get the ath9k driver to detect the hardware. The module apparently loads, but there's no output whatsoever in dmesg. I've been pulling my hair on this for a while now, and I'm running out of ideas.

Of course it would help a lot if the original configs were provided: I could rule out a config problem.

Post #43
f00b4r0
4 Jan 2017, 23:08

I adapted the patch to LEDE and it works flawlessly there. Patch submitted.

Post #44
samm
13 Jan 2017, 11:54

Hi, i am owner of the hap lite and i have reboot loop after installing OpenWRT. From the memory it boots fine, but after install to nand it is in the reboot loop. I was using images from the  hosting.yapic.net/openwrt/rb941-2nd/ Was trying to update loader. still no luck. I can provide more info if needed.

Post #45
f00b4r0
13 Jan 2017, 12:19
samm wrote:

Hi, i am owner of the hap lite and i have reboot loop after installing OpenWRT. From the memory it boots fine, but after install to nand it is in the reboot loop. I was using images from the  hosting.yapic.net/openwrt/rb941-2nd/ Was trying to update loader. still no luck. I can provide more info if needed.

See the post from arbalesttsr. You don't have to restore RouterOS if you can install rbcfg when booted from memory: you can change the settings with this tool.

BTW, patch has been accepted into LEDE, soon there will be images available.

(Last edited by f00b4r0 on 13 Jan 2017, 12:21)

Post #46
samm
13 Jan 2017, 13:24

See the post from arbalesttsr. You don't have to restore RouterOS if you can install rbcfg when booted from memory: you can change the settings with this tool.

BTW, patch has been accepted into LEDE, soon there will be images available.

sysupgrade openwrt-ar71xx-mikrotik-rb-941-2nd-squashfs-sysupgrade.bin


Thank you for reply. It does not work for me, i tried already. Now will try with rbcfg (installed on the RAM image)
rbcfg set boot_protocol dhcp
rbcfg set boot_device ethnand
rbcfg set booter backup
rbcfg show
boot_delay=2
boot_device=ethnand
boot_key=any
boot_protocol=dhcp
booter=backup
cpu_mode=powersave
uart_speed=115200


Writing from <stdin> to kernel ...
Unlocking rootfs ...

Writing from <stdin> to rootfs ...
Rebooting ...
Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.


At this point i have endless loop. Also i soldered serial and connected to it using 3.3v ttl converter. But there is no any byte sad

Post #47
f00b4r0
13 Jan 2017, 13:28

Have you tried cold booting (i.e. remove power and then boot)?

There's no serial available on this device, it's disabled by Mikrotik in their bootloader apparently. Seems they're not very friendly to modifications.

Post #48
samm
13 Jan 2017, 13:31

Yes, i tried to remove power, etc. No difference, still boot loop. From the same time - it works very well from the ram image, wifi and ethernet working, etc. Sad that console is disabled ( Any ideas how to debug that?

Post #49
samm
13 Jan 2017, 13:34

May be you can share your updated images and i will try it?

Post #50
samm
13 Jan 2017, 13:37

Another idea is that i have more recent version of the booter which bloks openwrt. Could it be the case? I can flash back routeros to find the booter number.

Sorry, posts 51 to 50 are missing from our archive.