R68s a new openwrt arm device. RK3568 2*2.5G+2*1G

I been doing some progress with the rk3568 SoC on OpenWrt and the mainline kernel,I got a r5s yestarday ,I could make it work with some issues with the WAN and LAN1 not working at a full speed , LAN2 is working and I did some tests.

3 Likes

@mj82 i tried to use your r5s image under your releases and dd onto sdcard but it wont boot. I have the 4gb version would that be different?

They ship the r5s with friendlywrt on the emmc, to boot from the sd card you neet to put the device in maskrom, press the mask key and keep pressed, power on, release the mask key after 4 sec.

1 Like

thanks a lot this worked. On reboot i have to keep doing this, is there a way to make this permanent or selectable?

actually nevermind, it tells you on their wiki https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S

I backported patches from linux-next to kernel 5.19 and changed the WAN port to LAN1 on the R5S

5 Likes

Yes i see the problem. the wan port depends on the correct configuration for the PHY but we do not have that yet. How did you get the r5s patches to start with?

I modified the DTS from their repo ,they are using the 5.10 rockchip kernel https://github.com/mj22226/linux-stable/blob/nanopi5-v5.10.y_opt/arch/arm64/boot/dts/rockchip/rk3568-nanopi5-rev01.dts

1 Like

Great work on the R5S!

I will be buying one in a bit.

1 Like

hello
can't boot with v.5.19 for R5S 4G https://github.com/mj22226/openwrt/releases/download/rockchip-5.19/openwrt-rockchip-armv8-friendlyelec_nanopi-r5s-ext4-sysupgrade.img.gz. burn img in Windows and in Linux - just solid red light and nothing happens after. please help, what do I do wrong?

unzip it and burn the img file. i suggest balanaetcher for windows img making.

Same here. Solid red on the SYS LED when booting from MicroSD. Card witten with balenaEtcher and dd.

Tried to flash the image to eMMC using FriendlyArm's eFlasher tool. Device failed to boot and the eMMC wasn't detected after trying to reflash it with any of the OEM's images. Had to put the device in MaskROM mode to recover the device using RKDevTool.

Perhaps you didn't press the mask button before booting from the sd card, works for me.

What is the different between openwrt and friendlywrt?

Yeah, button was pressed. Solid Red LED with no activity. Can flash it through the terminal with FriendlyWRT already installed but it renders the device unserviacable after rebooting. This is with the new 4GB model.

@Andy-Voigt FriendlyWRT is FiriendlyArm's fork of OpenWRT. I have yet to dive into the the detail of the changes they've made. One thing I have noticed with their image is that Wireguard doesn't work- even after the kmod package is reinstalled.

I found some security flaws on friendlywrt kernel debug .

7.332820] ********************************************************************
[    7.332826] **     NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE           **
[    7.332832] **                                                                **
[    7.332838] **  WRITEABLE clk DebugFS SUPPORT HAS BEEN ENABLED IN THIS KERNEL **
[    7.332844] **                                                                **
[    7.332849] ** This means that this kernel is built to expose clk operations  **
[    7.332854] ** such as parent or rate setting, enabling, disabling, etc.      **
[    7.332859] ** to userspace, which may compromise security on your system.    **
[    7.332864] **                                                                **
[    7.332869] ** If you see this message and you are not debugging the          **
[    7.332874] ** kernel, report this immediately to your vendor!                **
[    7.332880] **                                                                **
[    7.332885] **     NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE           **
[    7.332890] ********************************************************************

| __| _(_)___ _ _  __| | |_  \ \    / / _| |_
| _| '_| / -_) ' \/ _` | | || \ \/\/ / '_|  _|
|_||_| |_\___|_||_\__,_|_|\_, |\_/\_/|_|  \__|
                          |__/
 -----------------------------------------------------
 FriendlyWrt 21.02.3, r16554-1d4dea6d4f
 -----------------------------------------------------
root@FriendlyWrt:~#

In the latest version of FriendlyWrt they fixed wireguard error. Now it's working.

1 Like

I fixed on my latest build , now we need a tool so that user can easily flash the firmware on the eMMC, the friendlywrt tool doesn't work because use a different partition, to flash the firmware to eMMC we need;
1- check the name of the device fdisk -l
2- cp the firmware to /tmp
3- dd if=openwrt-rockchip-armv8-friendlyelec_nanopi-r5s-ext4-sysupgrade.img of=/dev/mmcblk* bs=10MB ( replace * with the eMMC name 0,1,2.)

1 Like

Is there an easy way to upgrade from Friendly eMMC to your firmware with SSH?

root@NanoPi-R5S:~# fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk2: 7.28 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F0250000-0000-492E-8000-6A280000480F

Device           Start      End  Sectors  Size Type
/dev/mmcblk2p1   16384    24575     8192    4M unknown
/dev/mmcblk2p2   24576    32767     8192    4M unknown
/dev/mmcblk2p3   32768    40959     8192    4M unknown
/dev/mmcblk2p4   40960    73727    32768   16M unknown
/dev/mmcblk2p5   73728   155647    81920   40M unknown
/dev/mmcblk2p6  155648   221183    65536   32M unknown
/dev/mmcblk2p7  221184   286719    65536   32M unknown
/dev/mmcblk2p8  286720  1490943  1204224  588M unknown
/dev/mmcblk2p9 1490944 15269854 13778911  6.6G unknown

so what are * in your step 3 in my case? Is it

dd if=openwrt-rockchip-armv8-friendlyelec_nanopi-r5s-ext4-sysupgrade.img of=/dev/mmcblk2p1 bs=10MB

Thank you

Try with a sd card method first, by pressing the mask button, connect the usb power cable, release the button after 5 sec, if boot , then do the upgrade, yours is 2 (/dev/mmcblk2)
This is .img format easier to flash https://github.com/mj22226/openwrt/releases/download/rockchip-5.19/r5s.img
dd if=r5s.img of=/dev/mmcblk2 bs=10MB

2 Likes