Installation on DGS-1210-20 F1

Installing and Using OpenWrt
1

Hi,

I just tested installation of Openwrt 22.03 RC4 onto DGS-1210-20 F1. Without having a matching image i tried the best match DGS-1210-16. From documenationion I expect 1210-16 G1 to be nearly the same as 1210-20 F1.

Loading imageramfs works nice. However during load I get an error - NEVERTHELESS openwrt will start

u-boot># tftpboot 0x8f000000 10.90.90.1:openwrt.bin
Using rtl8380#0 device
TFTP from server 10.90.90.1; our IP address is 10.90.90.90
Filename 'openwrt.bin'.
Load address: 0x8f000000
Loading: Got ARP REPLY, mac addr (e8:6a:64:e8:d5:2f), ip addr (10.90.90.1)
T T T T T T #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############
done
Bytes transferred = 6842989 (686a6d hex)
u-boot># bootm

Loading Runtime Image .OS:...FAILED
read: 0x4a650465, calculated: 0x49f786a4FS:...FAILED!!
os_ver = 1030, fs_ver = 1.........(os_ver & fs_ver) = 0...
## Booting kernel from Legacy Image at 8f000000 ...
   Image Name:   MIPS OpenWrt Linux-5.10.120
   Created:      2022-06-10   7:20:21 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    6842925 Bytes = 6.5 MB
   Load Address: 80000000
   Entry Point:  80000400
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] Linux version 5.10.120 (builder@buildhost) (mips-openwrt-linux-musl-gcc (OpenWrt GCC 11.2.0 r19426-2b1941e47d) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 Fri Jun 10 07:20:21 2022
[    0.000000] RTL838X model is 83826800

Setup will continue through webui. Flashing works but restart hangs. After poweroff/poweron cycle the system starts, gives the same error and falls back to failsafe image

**** RTL8214FC config - MAC ID = 24 ****
Now External 8214FC
Net:   Net Initialization Skipped
rtl8380#0
Hit Esc key to stop autoboot:  0

Loading Runtime Image .OS:...FAILED
read: 0x4a650465, calculated: 0x4a13593aFS:...FAILED!!
os_ver = 83ddf784, fs_ver = 1.........(os_ver & fs_ver) = 0...
## Booting kernel from Legacy Image at b4e80000 ...
   Image Name:
   Created:      2020-09-04   8:33:36 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    1035503 Bytes = 1011.2 KB
   Load Address: 80000000
   Entry Point:  80262000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Seems to be related to DGS-1210-28 installation fails but I do not get the clue how to solve this.

Any ideas?

2

Usually for me those T means problem in the tftp connection. I have only seen those when I have no connection at all. But then it usually fill a whole line with T and then aborts.

I have only # when loading the file from the tftp server.

1 Like
3

Those, I always get after the original firmware was replaced with OpenWRT (the second line is for me only the text FS:….Failed!! instead. But it doesn’t matter because it works anyway.
I think it somehow looks for the original firmware or something?

Have you actually made a setup firmware dts file for your device hardware or did you just took anything from the source code pile and rolled the dice?

4

The TFTP errors above came only from my linux firewall being not open ...

Whatever I tried, boot will fallback to legacy image after flash of OpenWRT. Looking at the mtd layout I get with vendor image:

Creating 9 MTD partitions on "Total SPI FLASH":
0x00000000-0x00080000 : "BOOT"
0x00080000-0x000c0000 : "BDINFO"
0x000c0000-0x00100000 : "BDINFO2"
0x00100000-0x00280000 : "KERNEL1"
0x00280000-0x00e80000 : "ROOTFS1"
0x00e80000-0x01000000 : "KERNEL2"
0x01000000-0x01040000 : "SYSINFO"
0x01040000-0x01c40000 : "ROOTFS2"
0x01c40000-0x02000000 : "JFFS2"

and with OpenWRT

[    1.962759] 0x000000000000-0x000000080000 : "u-boot"
[    1.974670] 0x000000080000-0x0000000c0000 : "u-boot-env"
[    1.983643] 0x0000000c0000-0x000000100000 : "u-boot-env2"
[    1.997484] 0x000000100000-0x000000e80000 : "firmware"
[    2.006608] 2 uimage-fw partitions found on MTD device firmware
[    2.013401] Creating 2 MTD partitions on "firmware":
[    2.018984] 0x000000000000-0x000000310000 : "kernel"
[    2.032271] 0x000000310000-0x000000d80000 : "rootfs"
[    2.040534] mtd: device 5 (rootfs) set to be root filesystem
[    2.050200] 1 squashfs-split partitions found on MTD device rootfs
[    2.057281] 0x0000005f0000-0x000000d80000 : "rootfs_data"
[    2.066279] 0x000000e80000-0x000001000000 : "kernel2"
[    2.079603] 0x000001000000-0x000001040000 : "sysinfo"
[    2.088263] 0x000001040000-0x000001c40000 : "rootfs2"
[    2.101834] 0x000001c40000-0x000002000000 : "jffs2"

Not sure about the mismatch between KERNEL1+ROOTFS1 (default) = firmware (openWRT) = 0x100000-0xe80000

5

Just took the prebuild rc4 images

6

Looking at bootlog from the wiki it seems as if OpenWRT will boot always from the backup partition. My device is booting original legacy from b4e80000 (see above) while G1 is booting OpenWRT legacy from b4100000 (see G1 bootlog )

Loading Runtime Image .OS:...FAILED
FS:...FAILED!!
...
## Booting kernel from Legacy Image at b4100000 ...
   Image Name:   MIPS OpenWrt Linux-5.4.124
   Created:      2021-06-13  22:02:19 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    2814581 Bytes = 2.7 MB
   Load Address: 80000000
   Entry Point:  80000400
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] Linux version 5.4.124 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16172-2aba3e9784)) #0 Sun Jun 13 22:02:19 2021
7

Other than knowing this isn't the supported device, are you just documenting your attempts to boot this device?

1 Like
8

So you took a 16-port H/W rev G1 and put it in a 20-port H/W rev F3.
And just expected it to work without making any attempts to check anything other than the fact that D-Link was the manufacturer on both.

9

I know that seems strange but from my understanding 1210-20 F1 = 1210-16 G1. initramfs works flawless. MTD layout is the same. Maybe some U-Boot differences ... I will have a look at the 1210-28 OpenWRT config. This is an F model too.

10

problem fixed. Boot address was wrongly set in U-Boot environment. Pointed to backup location. changed it via setenv and now it works. Will update the wiki.

11

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.