Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

For Developers
2923

Since I switched to WPA/WPA2 as some old HW didn't work with WPA2/WPA3, I was experiencing complete loss mDNS, DHCP and ARP packets, IPv6 SLAAC seemed to work.

To fix this, I had to run wifi, restart the both wireless interfaces or even the router.

As I was really annoyed by this, reading this thread I found some people was in a more recent firmware, so I downloaded ath11k-firmware-ipq8074_2024.03.14~795809c7-r2_aarch64_cortex-a53.ipk and after 7 days I have no issues running on upstream 23.05.3 version.

1 Like
2924

hmm I dont see anything new in the upstream repo, is that just a new compile of the same source, what is the fw-build-id in your dmesg output?

am I looking in the right place
https://github.com/egc112/OpenWRT-egc-add-on/tree/main/DL-WRX36

2925

This firmware drop with 3.14 date is on Snapshot.

1000222225
1000222225864×380 33.1 KB

"Stable" is known to be behind. I personally believe this router (and ones that are fairly new) are typically working way better on snapshot.

OpenWrt SNAPSHOT, r26937-7ca4190c18

[    9.421321] ath11k c000000.wifi: fw_version 0x290604a
5 fw_build_timestamp 2023-10-12 02:06 fw_build_id WLAN.H
K.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1
[    9.560689] remoteproc remoteproc0: Booting fw image
IPQ8074/q6_fw.mdt, size 668
[    9.961281] ath11k c000000.wifi: fw_version 0x290604a
5 fw_build_timestamp 2023-10-12 02:06 fw_build_id WLAN.H
K.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1
2927

if that’s showing as 01977 , is it really new firmware ?

I have a snapshot build thats on 01977 ; the wifi isn’t stable

2928

Is it fine to decrypt this and put it on a git repo so everyone can see the changes? Just wanted to make the files in here transparent for everyone.

EDIT: https://github.com/economic2408/dynalink-dl-wrx36-backup.cfg-unpacked

I went ahead and did it. Let me know if I have to take it down or if I accidentally fat fingered an edit.

2929

Hi guys! I tried to restore the firmware to OEM using these instructions:

but after the reboot the router is unreachable and the led is color purple.

I don't know what I did wrong.

openwrt
openwrt784×523 14.8 KB

Is this fixable with a serial cable?

1 Like
2930

If you did the u-boot initramfs boot config, you can always recover through it.

2931

I am a little late to the party and somehow unable to clearly follow the discussion around this config file. Kindly let me kwhat the file is about. I am running SNAPSHOT.

2932

If you're already running Openwrt, you don't need it ?

2 Likes
2933

It is about a downloadable OEM firmware config file that has the SSH console functionality enabled for OEM firmware, so that you can avoid using serial connection in the initial installation from OEM to OpenWrt.
Mentioned also in wiki: https://openwrt.org/toh/dynalink/dl-wrx36#part_1_-_copy_and_boot_initramfs

Like frollic says, if you are already in OpenWrt, no need for it any more.

1 Like
2934

Yes I did. Good to know, thanks frollic.

2935

the config file enables ssh for a router running stock firmware. I just decrypted it and shared it so that everyone can see how it was modified.

1 Like
2938

I have, or rather it seems I had, a Dynalink DL-WRX36 router that, according to the instructions, I was able to flash with OpenWrt and use without any issues. Then I attempted to upgrade from 23.05.3 to 23.05.4, which, although not officially communicated, I found under the following path: https://downloads.openwrt.org/releases/23.05.4/targets/ipq807x/generic/. I performed the installation via LAN cable, as always, while keeping the current /etc config. Before the installation, I always create a packages.lst file, which I restore using this command: opkg install $(cat /etc/config/packages.list).

So far, everything had worked fine with this method, even with major version upgrades. However, this time, while loading the packages list, I kept receiving messages that the storage was full and the package could not be installed. I struggled with it for a while, then decided to run a firstboot command and restart the device. That turned out to be a mistake, because since then, it doesn't go any further than this, which is the output from the serial port:

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.3.1-00163
S - IMAGE_VARIANT_STRING=HAACANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x000002e5
B - 201 - PBL, Start
B - 2736 - bootable_media_detect_entry, Start
B - 4214 - bootable_media_detect_success, Start
B - 4219 - elf_loader_entry, Start
B - 6886 - auth_hash_seg_entry, Start
B - 44727 - auth_hash_seg_exit, Start
B - 106704 - elf_segs_hash_verify_entry, Start
B - 169557 - PBL, End
B - 179248 - SBL1, Start
B - 230702 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B - 237137 - pm_device_init, Start
B - 357612 - PM_SET_VAL:Skip
D - 120048 - pm_device_init, Delta
B - 360022 - pm_driver_init, Start
D - 5368 - pm_driver_init, Delta
B - 366396 - clock_init, Start
D - 2135 - clock_init, Delta
B - 370331 - boot_flash_init, Start
D - 12627 - boot_flash_init, Delta
B - 386740 - boot_config_data_table_init, Start
D - 3080 - boot_config_data_table_init, Delta - (575 Bytes)
B - 394212 - Boot Setting : 0x00000618
B - 398147 - CDT version:2,Platform ID:8,Major ID:133,Minor ID:1,Subtype:5
B - 405253 - sbl1_ddr_set_params, Start
B - 408974 - CPR configuration: 0x30c
B - 412421 - cpr_init, Start
B - 415288 - Rail:0 Mode: 5 Voltage: 792000
B - 420412 - CL CPR settled at 744000mV
B - 423248 - Rail:1 Mode: 5 Voltage: 880000
B - 427518 - Rail:1 Mode: 7 Voltage: 896000
D - 16439 - cpr_init, Delta
B - 434320 - Pre_DDR_clock_init, Start
B - 438315 - Pre_DDR_clock_init, End
B - 441701 - DDR Type : PCDDR4
B - 734775 - do ddr sanity test, Start
D - 1037 - do ddr sanity test, Delta
B - 736026 - DDR: Start of HAL DDR Boot Training
B - 740875 - DDR: End of HAL DDR Boot Training
B - 746548 - DDR: Checksum to be stored on flash is 988447749
B - 756857 - Image Load, Start
B - 1239489 - Error code 37000105 at boot_config.c Line 329

Does anyone have any ideas if this can be salvaged, or is it trash?

2939

Does anyome know how to make the front LED change behavior in this router? Preferably i would like it to blink red if on wan no internet is detected, blink purple if on the vpn network interface there is no internet detected. And blue if on both internet is detected.

2940

Script that flashes Internet Red LED as a function of Internet reachability paths to LED will differ, trial and error.

2941

We dont know for the wrx-36 what the path is?

And isnt there a way to ping through different interfaces?

2942

we do, but I can't be arsed to look it up ... :slight_smile:
you got one, so I guess figuring it out should be pretty simple ?

2943

pingcheck is your friend!

I already exercise it not just with pppoe-wan but with mesh connectivity too!

1 Like
2944

It can be definitely salvaged, but it requires running a couple of commands over the serial console and a USB memory.
Please be sure to use a 3.3V serial console device, since that is the only voltage that it can accept input from (I went thru 3 different ones until I got one that was compatible).

https://openwrt.org/toh/dynalink/dl-wrx36#tab__part_1_option_b_-_use_a_serial_connection_33v_to_copy_and_boot_initramfs

2946

During upgrade from 23.05.2 to 23.05.4 I getting "user.info upgrade: The device is supported, but the config is incompatible to the new image (1.1->1.0). Please upgrade without keeping config (sysupgrade -n)." error message, and I guess there was same error when I migrated from pre-23.05 snapshot to 23.05 release build.

Forcing upgrade and keeping config does not break anything, so I guess it's just something left in config files from snapshots times? How can I found why this error appear and what should be done to fix it without performing reset? (There is just too much to reconfigure, so I would like to avoid that, if possible.)