These tests:
I'm a little late and maybe you already figured this out.
From the output it seems you made a typo when setting and env var and typed "namd0" (note the "m") instead of "nand0".
This is on step 5 "Set U-boot env variable: mtdids"
Fixing the typo should get you a working OpenWrt version.
It seems you did (note the "m"):
# fw_setenv mtdids 'namd0=nand0'
But it should have been:
# fw_setenv mtdids 'nand0=nand0'
From boot without interruption:
Hit any key to stop autoboot: 0
incorrect device type in namd0=nand0
Error initializing mtdparts!
Error, no UBI device/partition selected!
From printenv
mtdids=namd0=nand0
3 Likes
Thank you very much!
I am glad that it is my typo at fault, not the procedure.
With help of the serial console, my second attempt proceeded OK (this time I proof read every command 3 times before pressing enter.)
1 Like
Just to re-state:
initramfs: For temporary booting of OpenWRT. Runs OpenWRT in RAM (live image essentially) while keeping stock firmware on flash
factory: For persistent booting of OpenWRT. Should be written to flash in place of stock firmware on flash
sysupgrade: For use with the 'sysupgrade' command or the Luci web interface upgrade page. Should be used when going from OpenWRT to OpenWRT (both on flash)
1 Like
My apologies, most of my posts are referencing the three files and their names that I built myself for this device. It's a good way to include Luci and other packages you want from the start without having to use opkg later. Those file names don't exist anywhere but on my machine. You were correct to pull the public snapshots from downloads.openwrt.org.
Hello, I have just successfully flashed my DL-WRX36 an anything looks stable. Is it possible to shutdown the device - I tried with "poweroff" and "halt" but its' allways rebooting
1 Like
Does anyone know if VLAN or 802.1Q works with this router on OpenWRT?
1 Like
thanks for the help though! Couldn't have done it without you guys. I setup wireguard correctly, now to trying and setup a mesh.
So a last question for now, what is that update file used for? The Firmware OpenWrt snapshot Upgrade bin file.
Should we flash that at firmware upgrade menu? Why? Isnt this kind of a package manager and it can update those itself?
Furthermore, i will use my own guide soon that i created to flash the second and third routers, to make the mesh network, so i can then confirm if that works 100%.
Reread Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion - #604 by frollic
Yes, or the sysupgrade command in cli.
You always do full upgrades.
No, the package manager doesn't do dependencies, making it risky.
1 Like
thanks, updated the instructions to include the firmware update. also applied it to my dynalink.
Does someone have access to the wiki page? It would be nice to link this thread or replace the wiki with some parts of my tutorial, to make it easy for newbees.
It says at the bottom not just anyone can make edits so.
The update is pointless, if you've DLed it at the same time as the install image, they're exactly the same, just made for different purposes.
Your tutorial assumes the user uses Windows, which isn't always the case.
Keep the wiki instruction OS neutral.
1 Like
still, it would be in my opinion good to have a guide there for windows installation, or at least have it a bit more noob friendly, but thats my 2c.
I just quickly went through my instructions with my second dynalink, and everything went fast and smooth without issues.
EDIT: Third one now also flashed fine. Time to create a mesh network tommorow with fast transitioning! 
1 Like
That's fine, the your Win guide can be linked to from the wiki, just as the post for decrypting the backup file is.
VLANs work like a dream.
1 Like
I followed your Windows guide and installed OpenWRT without issue. It also saves people from skimming through hundreds of messages to understand the process. Thanks for sharing it!
1 Like
Also curious at this, but openwrt probably doesnt do anything with it. Would love for it to be on, can always use some repeaters for iot devices.
Thanks, appriciate it, just know all the work is done by the tech savy folks here.
Hi all, any help would be appreciated. I bricked my device; I did save all the commands I executed after I ssh'ed to my device running initramfs from memory:
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00080000 00020000 "0:bootconfig"
mtd3: 00080000 00020000 "0:bootconfig1"
mtd4: 00300000 00020000 "0:qsee"
mtd5: 00300000 00020000 "0:qsee_1"
mtd6: 00080000 00020000 "0:devcfg"
mtd7: 00080000 00020000 "0:devcfg_1"
mtd8: 00080000 00020000 "0:apdp"
mtd9: 00080000 00020000 "0:apdp_1"
mtd10: 00080000 00020000 "0:rpm"
mtd11: 00080000 00020000 "0:rpm_1"
mtd12: 00080000 00020000 "0:cdt"
mtd13: 00080000 00020000 "0:cdt_1"
mtd14: 00080000 00020000 "0:appsblenv"
mtd15: 00100000 00020000 "0:appsbl"
mtd16: 00100000 00020000 "0:appsbl_1"
mtd17: 00080000 00020000 "0:art"
mtd18: 06100000 00020000 "rootfs"
mtd19: 00900000 00020000 "0:wififw"
mtd20: 06100000 00020000 "rootfs_1"
mtd21: 00900000 00020000 "0:wififw_1"
mtd22: 01600000 00020000 "ubifs"
mtd23: 00080000 00020000 "0:ethphyfw"
mtd24: 00280000 00020000 "certificate"
root@OpenWrt:~# ubiformat /dev/mtd18 -y -f /tmp/openwrt-ipq807x-generic-dynalink_dl-wrx36-squashfs-factory.ubi
ubiformat: mtd18 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 775 -- 100 % complete
ubiformat: 776 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 89 -- 100 % complete
ubiformat: formatting eraseblock 775 -- 100 % complete
root@OpenWrt:~# ubiformat /dev/mtd20 -y -f /tmp/openwrt-ipq807x-generic-dynalink_dl-wrx36-squashfs-factory.ubi
ubiformat: mtd20 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 775 -- 100 % complete
ubiformat: 776 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 89 -- 100 % complete
ubiformat: formatting eraseblock 775 -- 100 % complete
root@OpenWrt:~# fw_setenv mtdids 'nand0=nand0'
root@OpenWrt:~# cat /sys/class/mtd/mtd18/offset
16777216
root@OpenWrt:~# fw_setenv mtdparts 'mtdparts=nand0:0x6100000@0x1000000(fs),0x6100000@0x7a00000(fs_1)'
root@OpenWrt:~# fw_setenv bootcmd 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt50
10w-d350- rev0'
root@OpenWrt:~# reboot
root@OpenWrt:~# Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.
I am pretty sure this part is the problem:
root@OpenWrt:~# fw_setenv bootcmd 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt50
10w-d350- rev0'
I thought I could factory reset my device and that would wipe bootcmd to then boot from initramfs from my usb
but pressing and holding the reset button for 7 seconds does not wipe the bootcmd command.
Also, while I do have serial to my device, I never get the U-Boot prompt
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 - 203 - PBL, Start
B - 2739 - bootable_media_detect_entry, Start
B - 4227 - bootable_media_detect_success, Start
B - 4231 - elf_loader_entry, Start
B - 6892 - auth_hash_seg_entry, Start
B - 44701 - auth_hash_seg_exit, Start
B - 106558 - elf_segs_hash_verify_entry, Start
B - 169412 - PBL, End
B - 178608 - SBL1, Start
B - 229909 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B - 236314 - pm_device_init, Start
B - 355843 - PM_SET_VAL:Skip
D - 119102 - pm_device_init, Delta
B - 358253 - pm_driver_init, Start
D - 5337 - pm_driver_init, Delta
B - 364566 - clock_init, Start
D - 2104 - clock_init, Delta
B - 368562 - boot_flash_init, Start
D - 12718 - boot_flash_init, Delta
B - 385032 - boot_config_data_table_init, Start
D - 3080 - boot_config_data_table_init, Delta - (575 Bytes)
B - 392535 - Boot Setting : 0x00000618
B - 396469 - CDT version:2,Platform ID:8,Major ID:133,Minor ID:1,Subtype:5
B - 403484 - sbl1_ddr_set_params, Start
B - 407297 - CPR configuration: 0x30c
B - 410774 - cpr_init, Start
B - 413549 - Rail:0 Mode: 5 Voltage: 808000
B - 418734 - CL CPR settled at 760000mV
B - 421571 - Rail:1 Mode: 5 Voltage: 880000
B - 425841 - Rail:1 Mode: 7 Voltage: 904000
D - 16531 - cpr_init, Delta
B - 432642 - Pre_DDR_clock_init, Start
B - 436638 - Pre_DDR_clock_init, End
B - 440054 - DDR Type : PCDDR4
B - 446794 - do ddr sanity test, Start
D - 1067 - do ddr sanity test, Delta
B - 450515 - DDR: Start of HAL DDR Boot Training
B - 455243 - DDR: End of HAL DDR Boot Training
B - 460916 - DDR: Checksum to be stored on flash is 1935662099
B - 471316 - Image Load, Start
D - 505507 - QSEE Image Loaded, Delta - (1378368 Bytes)
B - 976915 - Image Load, Start
D - 61 - SEC Image Loaded, Delta - (0 Bytes)
B - 984601 - Image Load, Start
D - 293898 - DEVCFG Image Loaded, Delta - (32488 Bytes)
B - 1278590 - Image Load, Start
D - 305122 - RPM Image Loaded, Delta - (93060 Bytes)
B - 1583804 - Image Load, Start
D - 369934 - APPSBL Image Loaded, Delta - (537454 Bytes)
B - 1953891 - QSEE Execution, Start
D - 91 - QSEE Execution, Delta
B - 1959686 - USB D+ check, Start
D - 0 - USB D+ check, Delta
B - 1966091 - SBL1, End
D - 1789770 - SBL1, Delta
S - Flash Throughput, 6737 KB/s (2042617 Bytes, 303192 us)
S - DDR Frequency, 600 MHz
S - Core 0 Frequency, 1651 MHz
I already ordered another device, if I recover this one this would become my test device.
'- rev0'
The extra space after '-' seems an issue.
A good start you got some outputs from serial console.
Please try swap the Transit/Receive pins.
You do not got to u-boot shell because the pressed key is not detected during boot.
I got the same issue, which after swap the pins fixed the issue.
1 Like
if the Transmit/Receive pins were connected incorrectly I would not get anything on my screen