Is there any work in progress about adding OpenWrt support to NanoPI R5S?
I already purchased a R5S, and while I wait it to be delivered I've started looking at what would be required to have OpenWrt running on it.
I did a FriendlyWrt build but it is a mess. The .config seems to have a R2S profile with some adaptations. I really will not spend much time trying to understand what FriendlyWrt is doing.
On the other hand, github user @kidding9 seems to have created an armv8.mk patch that seems to be a good starting point (which seems to also be reusing R2S DTS file). When I have some free time, I will try applying this patch to OpenWrt to see what happens.
The reviewer noted however that, in order to get the full speed, the following configuration change was needed:
(…) To achieve maximum throughput, delete the pre-configured bridge interface br0, and configure both multigigabit eth1 (LAN1 port) and eth2 (LAN2 port) as standalone unbridged interfaces.(…)
BTW, shouldn’t we split this topic into a new one dedicated to R5S? (this topic is for the R68s….).
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.
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.
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?
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.
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:~#
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.)
