Dynalink DL-WRX36

Installing and Using OpenWrt
1

Followed this guide and it looks like it's bricked.

I was able to get initramfs booted and SCP'd the factory image for dl-wrx36 (openwrt-ipq807x-generic-dynalink_dl-wrx36-squashfs-factory.ubi) found here '. I am finding it odd the wiki for dl-wrx36 mentions you'll need to download the factory image, it mentions nothing about where to find it. I happened to find another post that pointed to above.

Steps provided below. I now have a solid red (or purple?) light and router won't boot.

Anyone see anything I did wrong here?

root@OpenWrt:~# cat /proc/mtf
cat: can't open '/proc/mtf': No such file or directory
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 /root/openwrt-ipq807x-generic-dynalin
k_dl-wrx36-squashfs-factory.ubi
ubiformat: mtd18 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131                                                     072 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 95 -- 100 % complete
ubiformat: formatting eraseblock 775 -- 100 % complete
root@OpenWrt:~# ubiformat /dev/mtd20 -y -f /root/openwrt-ipq807x-generic-dynalin
k_dl-wrx36-squashfs-factory.ubi
ubiformat: mtd20 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131                                                     072 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 95 -- 100 % complete
ubiformat: formatting eraseblock 775 -- 100 % complete
root@OpenWrt:~# cat /sys/class/mtd/mtd18/offset
16777216
root@OpenWrt:~# fw_setenv mtdparts 'mtdparts=nand0:0x6100000@0x1000000(fs),0x610
0000@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@rt5010w-d350-rev0'
root@OpenWrt:~# reboot
root@OpenWrt:~#
2

On the surface of it, you missed step 5 from the wiki.

5. Set U-boot env variable: mtdids
   # fw_setenv mtdids 'nand0=nand0'
1 Like
3

You also missed

Read the whole chapter before you start your OpenWRT installation

and because of the above

* The factory image can be found in the same place (URL) as the initramfs image.
1 Like
4

It sounds like it's time for you to simply step away from the forums given your burnout is clearly causing patronizing and unhelpful responses.

"* The factory image can be found in the same place (URL) as the initramfs image" is listed in a area where it mentions nothing about the URL of the initramfs image.

The only mention of the locationof the initramfs image is a direct download link.

If you spent more time helping improve the wiki pages vs simply calling people out for not reading minds, this open platform would be a better place.

5

That would be it! Thank you.

6

you need it for the initial install, so it should be hard to miss, you apparently didn't, since you made it half way through the process.

if you can't figure out how to edit an URL, you probably shouldn't handle anything more complicated than a calculator with + - * / and =.

if you really want to know why there's no direct link to the factory image, feel free to read the long WRX36 thread.

9

I am connected via JTAG and i am seeing this. Should I be able to boot from USB, or what do you recommend?

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 -      2735 - bootable_media_detect_entry, Start
B -      4197 - bootable_media_detect_success, Start
B -      4202 - elf_loader_entry, Start
B -      6862 - auth_hash_seg_entry, Start
B -     44676 - auth_hash_seg_exit, Start
B -    106505 - elf_segs_hash_verify_entry, Start
B -    169362 - PBL, End
B -    185165 - SBL1, Start
B -    238357 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B -    245006 - pm_device_init, Start
B -    368867 - PM_SET_VAL:Skip
D -    123311 - pm_device_init, Delta
B -    371276 - pm_driver_init, Start
D -      5337 - pm_driver_init, Delta
B -    377590 - clock_init, Start
D -      2135 - clock_init, Delta
B -    381616 - boot_flash_init, Start
D -     12627 - boot_flash_init, Delta
B -    397994 - boot_config_data_table_init, Start
D -      3080 - boot_config_data_table_init, Delta - (575 Bytes)
B -    405497 - Boot Setting :  0x00000618
B -    409432 - CDT version:2,Platform ID:8,Major ID:133,Minor ID:1,Subtype:5
B -    416447 - sbl1_ddr_set_params, Start
B -    420259 - CPR configuration: 0x30c
B -    423736 - cpr_init, Start
B -    426481 - Rail:0 Mode: 5 Voltage: 800000
B -    431697 - CL CPR settled at 752000mV
B -    434533 - Rail:1 Mode: 5 Voltage: 880000
B -    438803 - Rail:1 Mode: 7 Voltage: 896000
D -     16531 - cpr_init, Delta
B -    445605 - Pre_DDR_clock_init, Start
B -    449600 - Pre_DDR_clock_init, End
B -    453016 - DDR Type : PCDDR4
B -    459757 - do ddr sanity test, Start
D -      1067 - do ddr sanity test, Delta
B -    463447 - DDR: Start of HAL DDR Boot Training
B -    468175 - DDR: End of HAL DDR Boot Training
B -    473939 - DDR: Checksum to be stored on flash is -1715939099
B -    484370 - Image Load, Start
D -    505568 - QSEE Image Loaded, Delta - (1378368 Bytes)
B -    990030 - Image Load, Start
D -        61 - SEC Image Loaded, Delta - (0 Bytes)
B -    997685 - Image Load, Start
D -    293807 - DEVCFG Image Loaded, Delta - (32488 Bytes)
B -   1291583 - Image Load, Start
D -    305183 - RPM Image Loaded, Delta - (93060 Bytes)
B -   1596858 - Image Load, Start
D -    369599 - APPSBL Image Loaded, Delta - (536590 Bytes)
B -   1966609 - QSEE Execution, Start
D -        61 - QSEE Execution, Delta
B -   1972404 - USB D+ check, Start
D -         0 - USB D+ check, Delta
B -   1978809 - SBL1, End
D -   1795932 - SBL1, Delta
S - Flash Throughput, 6732 KB/s  (2041753 Bytes,  303283 us)
S - DDR Frequency, 600 MHz
S - Core 0 Frequency, 1651 MHz


U-Boot 0.0.1-1-80112-CS (May 21 2021 - 09:29:10 +0800)

DRAM:  smem ram ptable found: ver: 1 len: 4
1 GiB
Led init ...
NAND:  Could not find nand_gpio in dts, using defaults
ONFI device found
ID = 1590aa2c
Vendor = 2c
Device = aa
qpic_nand: changing oobsize to 80 from 128 bytes
SF: Unsupported flash IDs: manuf ff, jedec ffff, ext_jedec ffff
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
256 MiB
MMC:   sdhci: Node Not found, skipping initialization

PCI0 is not defined in the device tree
PCI1 is not defined in the device tree
In:    serial@78B3000
Out:   serial@78B3000
Err:   serial@78B3000
machid: 8850105
MMC Device 0 not found
eth5 MAC Address from ART is not valid
Hit any key to stop autoboot:  0
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=1", size 97 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 776, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 13                                                                                                             36810140
ubi0: available PEBs: 0, total reserved PEBs: 776, PEBs reserved for bad PEB han                                                                                                             dling: 40
Read 0 bytes from volume kernel to 44000000
No size specified -> Using max size (4190208)
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Net:   MAC0 addr:a4:97:33:df:9a:c6
PHY ID1: 0x4d
PHY ID2: 0xd0b1
PHY ID1: 0x4d
PHY ID2: 0xd101
EDMA ver 1 hw init
Num rings - TxDesc:1 (0-0) TxCmpl:1 (7-7)
RxDesc:1 (15-15) RxFill:1 (7-7)
ipq807x_edma_alloc_rings: successfull
ipq807x_edma_setup_ring_resources: successfull
ipq807x_edma_configure_rings: successfull
ipq807x_edma_hw_init: successfull
eth0
IPQ807x#
10

if you haven't installed openwrt already, do it by following one of the guides.

11

I am trying to USB boot but it doesn't work.
Not sure what you are refering to, I stated that I am connected via JTAG?

12

No, you aren't.
You're connected to the serial console, not JTAG, which is a quite different beast.

I know that this is a common mistake and might sound like hair-splitting, but it isn't - both "serial console" (or UART access) and "JTAG" exist, both provide rather different access to the target board and you can do different things with them. While serial console access is kind of 'easy', in the sense of just 3 cables and human readable input/ output, JTAG provides low-level SOC access using over a dozen cables and requires very SOC specific knowledge and experience to operate.

1 Like
13

Did you follow the wiki ?

It doesn't look like you did.

14

I appreciate the explanation.
UART it is then.
How to something loaded to this mofo then?

15

By reading the paged linked to in the 1st post of this thread?

If you have issues, provide specifics.

16

the specific is that this doesn't work:
"1. Stop auto boot to get to U-boot shell."

17

The IPQ807x# prompt would disagree...

Use the ssh method instead ?

18

It won't accept any input.
I can type but don't get anything on the screen.

I get a 3 second or so count-down to stop auto-boot.
It won't take any input.

SSH? I get no connection to IP 192.168.1.1

19

What you've posted isn't the default boot sequence.
You must have done something since the boot halted/aborted.

SSH is if the device booted, yours haven't.
The details for installing using ssh are in the wiki.

20

via what? USB?
It won't boot anything from a USB stick.

I will post the output tomorrow again without halting or pressing anything.

21

USB boot fails are often related to flash drive or it's layout.

22

Ihave formated it with windows 4096, 16, 32 kB and with ubuntu.
No luck. I will see if I can find another flashdrive ...