Messages

Can someone share their (working) dts for the R4S and/or R4SE?

I've tried both mainline u-boot and the friendlyarm vendor versions.
Both cause a kernel panic when devmatch fires.

Code Select Expand


Starting device manager...Fatal data abort:
  x0:                0
  x1: ffffa0000758a000
  x2:                3
  x3: ffff0000da33f650 ($d.10 + d8f61078)
  x4: ffff0000da33f5d8 ($d.10 + d8f61000)
<snip>


EDIT - nevermind, I got it working on both the r4s and r4se!

The tl;dr to the last 10 hours of my life is that in the version of rk3399.dtsi that is in u-boot repos, someone fatfingered the first chunk of the pcie address range (I think that's what this field is for). see below

The "ranges" field under "pcie0: pcie@f8000000" needs to start with 0x83000000, not 0x82000000, such that it reads like this:

Code Select Expand


pcie0: pcie@f8000000 {
<snip>
ranges = <0x83000000 0x0 0xfa000000 0x0 0xfa000000 0x0 0x1e00000
  0x81000000 0x0 0xfbe00000 0x0 0xfbe00000 0x0 0x100000>;
<snip>


Made that switch and mostly good now. I'm seeing the same issue I saw in openwrt 21.x where the re0 interface disappears sometimes on soft reboots. The openwrt folks have this patch, I glanced through the freebsd kernel sources and it might be possible to duplicate the effects? I'm not sure how setting the mmc voltage effects the pcie nic though  ???
https://github.com/immortalwrt/immortalwrt/blob/master/target/linux/rockchip/patches-5.15/107-mmc-core-set-initial-signal-voltage-on-power-off.patch

EDIT EDIT - A-HA: (why wasn't this mainlined?)
https://github.com/friendlyarm/kernel-rockchip/commit/8efe01b4386ab38a36b99cfdc1dc02c38a8898c3

Hi all, excited to join in on the fun here!

I currently have 22.7 running from yrzr.tx on an R4S. I now see from a few posts above that this version is broken  so I'll try 22.1.10 shortly. My hope is to replace my hp t730 for home use.

After enabling powerd and setting it to maximum cpu frequency scaling I am able to push around 400mbit in each direction through the unit in cursory iperf3 testing.
I have a Cisco T-Rex benchmarking setup and I plan to do more in depth testing - different packet sizes, number of flows, open states, etc.

When initially testing on openwrt I was able to pin irqs and receive queues for the two nics to the faster A72 cores which was a notable improvement.
Is this possible in opnsense/freebsd? I did a bit of googling and didn't find any definitive answers.

I also have two R4SE's (I dream of HA firewall at home) with 32gb of emmc onboard.
I have tried flashing a few different opnsense images using rkdevtool with no success yet (I didn't really expect it to justwork).
Anyone have any ideas on that? It seems the tool wants the image split into various partitions, but it does allow me to just flash the whole image starting at 0x0.
I haven't dived into the image build process but I'm sure I'll dig into that soon.
I have a 3v3 rs232 adapter on the way so I'll be able to get a console on these things soon.

Anyway, happy to test/help/etc!