LiBwrt-op / openwrt-6.x

This repository is a mirror of https://git.openwrt.org/openwrt/openwrt.git It is for reference only and is not active for check-ins. We will continue to accept Pull Requests here. They will be merged via staging trees then into openwrt.git.
Other
62 stars 57 forks source link

New device support: Wallys DR5018 MP03.5-c1 #33

Open kimocoder opened 1 week ago

kimocoder commented 1 week ago

The board hasn't made it to OpenWRT 23.05 support, only 19.07 at this point, so I figured you got a nice build here with correct feeds and all, so I have a proposal on including my devices in this build :+1:

I'm not too familiar with OpenWRT build system or much around it, but I've been reading lots past 6 months so I pulled the running device-tree to inspect, possibly add. The wireless configuration and everything works very well on running 19.07 Chaos Calmer, but for me the build is ancient :-1:

Let me know if interested in adding the Wallys DR5018 or if anything needed from the running build :1st_place_medal:

running_dts.txt

defconfig.txt

kimocoder commented 1 week ago
[    1.972825] m25p80 spi32766.0: found w25q256jw, expected n25q128a11
[    1.978233] m25p80 spi32766.0: w25q256jw (32768 Kbytes)
[    1.984087] 14 ofpart partitions found on MTD device spi32766.0
[    1.989316] Creating 14 MTD partitions on "spi32766.0":
[    1.995150] 0x000000000000-0x000000030000 : "0:SBL1"
[    2.001513] 0x000000030000-0x000000040000 : "0:MIBIB"
[    2.006668] 0x000000040000-0x000000050000 : "0:BOOTCONFIG"
[    2.011569] 0x000000050000-0x000000060000 : "0:BOOTCONFIG1"
[    2.017088] 0x000000060000-0x000000100000 : "0:QSEE"
[    2.022498] 0x000000100000-0x0000001a0000 : "0:QSEE_1"
[    2.027742] 0x0000001a0000-0x0000001b0000 : "0:DEVCFG"
[    2.032596] 0x0000001b0000-0x0000001c0000 : "0:DEVCFG_1"
[    2.037788] 0x0000001c0000-0x0000001d0000 : "0:CDT"
[    2.043168] 0x0000001d0000-0x0000001e0000 : "0:CDT_1"
[    2.047948] 0x0000001e0000-0x0000001f0000 : "0:APPSBLENV"
[    2.052985] 0x0000001f0000-0x000000290000 : "0:APPSBL"
[    2.058437] 0x000000290000-0x000000330000 : "0:APPSBL_1"
[    2.063417] 0x000000330000-0x0000003a0000 : "0:ART"
[    2.070113] QPIC controller hw version Major:2, Minor:1
[    2.072385] QPIC controller support serial nand.
[    2.077935] nand: device found, Manufacturer ID: 0xc8, Chip ID: 0x41
[    2.082457] nand: GigaDevice GD5F1GQ5REYIG SPI NAND 1G
[    2.088844] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[    2.094306] 3 ofpart partitions found on MTD device qcom_nand.0
[    2.101334] Creating 3 MTD partitions on "qcom_nand.0":
[    2.107223] 0x000000000000-0x000000080000 : "0:TRAINING"
[    2.114044] 0x000000080000-0x000003e80000 : "rootfs"
[    2.164959] mtd: device 15 (rootfs) set to be root filesystem
[    2.165210] mtdsplit: no squashfs found in "rootfs"
[    2.169761] 0x000003e80000-0x000007c80000 : "rootfs_1"
kimocoder commented 1 week ago

Firmware mountpoints

root@ipqwrt:/lib/firmware# ls
IPQ5018                   QCA9984                   firmware_rdp_feature.ini  qca                       qca-nss0-retail.bin       qca-nss0.bin              qcn6122
root@ipqwrt:/lib/firmware# df -h
Filesystem                Size      Used Available Use% Mounted on
mtd:ubi_rootfs           21.5M     21.5M         0 100% /rom
tmpfs                   196.4M     50.9M    145.6M  26% /tmp
/dev/ubi0_4              19.6M      6.4M     12.2M  35% /overlay
overlayfs:/overlay       19.6M      6.4M     12.2M  35% /
tmpfs                   512.0K      4.0K    508.0K   1% /dev
/dev/mtdblock18           3.8M      3.8M         0 100% /lib/firmware/IPQ5018/WIFI_FW
kimocoder commented 1 week ago
root@ipqwrt:~# dmesg | grep "IPQ"
[    0.000000] Machine model: Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1
[    0.198548] CPU: IPQ5018, SoC Version: 1.1
[   39.949451] remoteproc remoteproc0: Booting fw image IPQ5018/q6_fw.mdt, size 1820
[   41.679790] cnss[2]: INFO: platform name: Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1
[   41.737094] cnss[2]: INFO: BDF IPQ5018/bdwlan.b24 size 131072
[   41.747022] cnss[2]: INFO: CALDATA IPQ5018/caldata.bin size 131072 offset 0x20000
[   41.972877] cnss[41]: INFO: platform name: Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1
[   69.749904] remoteproc remoteproc0: Booting fw image IPQ5018/q6_fw.mdt, size 1820
[   69.921797] cnss[2]: INFO: platform name: Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1
[   69.933487] cnss[2]: INFO: BDF IPQ5018/bdwlan.b24 size 131072
[   69.941913] cnss[2]: INFO: CALDATA IPQ5018/caldata.bin size 131072 offset 0x20000
[   71.178109] cnss[41]: INFO: platform name: Qualcomm Technologies, Inc. IPQ5018/AP-MP03.5-C1
root@ipqwrt:~# dmesg | grep "firmware"
[    0.000000] psci: PSCIv1.0 detected in firmware.
root@ipqwrt:~# dmesg | grep "FW"
[   41.629645] cnss[2]: INFO: Waiting for FW ready. Device: 0xfffc, FW ready timeout: 60 seconds
[   41.665222] cnss[2]: INFO: QMI WLFW service connected, state: 0x1
[   41.846138] cnss[2]: INFO: FW ready received for device 0xfffc
[   41.907343] cnss[41]: INFO: Waiting for FW ready. Device: 0xfffb, FW ready timeout: 60 seconds
[   41.967760] cnss[41]: INFO: QMI WLFW service connected, state: 0x1
[   42.126125] cnss[41]: INFO: FW ready received for device 0xfffb
[   45.073465] cnss[2]: INFO: QMI WLFW service disconnected, state: 0x6
[   67.683241] cnss[41]: INFO: QMI WLFW service disconnected, state: 0x6
[   69.908529] cnss[2]: INFO: QMI WLFW service connected, state: 0x1
[   70.000630] cnss[2]: INFO: Waiting for FW ready. Device: 0xfffc, FW ready timeout: 60 seconds
[   70.008391] cnss[2]: INFO: FW ready received for device 0xfffc
[   70.535482] wlan: [98:I:TIF] FW Build Version (Ext.) = 0
[   71.090630] cnss[41]: INFO: Waiting for FW ready. Device: 0xfffb, FW ready timeout: 60 seconds
[   71.162465] cnss[41]: INFO: QMI WLFW service connected, state: 0x1
[   71.416168] cnss[41]: INFO: FW ready received for device 0xfffb
[   71.917367] wlan: [98:I:TIF] FW Build Version (Ext.) = 0
breeze303 commented 1 week ago

Currently this source code for ipq5018 this SUBTARGET is untested state, that is to say, the firmware has not been brushed into any machine for testing, I think it is not time to add new machines at the moment, at the moment it should be the SUBTARGET support for testing first!