Yep, they're in there. Here's Features from /proc/cpuinfo on mine: Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddpe
You can also see /proc/crypto and which ciphers have hardware support in the kernel. Heres aes-cbc:
driver : cbc-aes-ce
module : kernel
priority : 300
refcnt : 1
selftest : passed
internal : no
type : skcipher
async : no
blocksize : 16
min keysize : 16
max keysize : 32
ivsize : 16
chunksize : 16
walksize : 16
This allows anything using the kernel crypto engine to take advantage, but userspace crypto services (any using openssl/wolfssl) will need a provider to allow for this. For wolfssl, that's just the wolfsslcpu provider, but openssl needs a bit more including libopenssl-devcrypto, which has a handful of kernel module (kmod-crypto-) dependencies that need to be installed as part of the package. OpenSSL also needs /etc/openssl.cnf updated to use the engine - this is especially helpful if you're running OpenVPN, SSH or web services using Openssl-backed ciphers for encryption.
Fortunately, these are all compiled for most OpenWRT builds so any dependencies as part of the distribution can be pulled down and installed. Once your changes are merged, those kernel module packages will install without any problem and I'll be able to test/leverage any openssl acclerations in this chip.
From my understanting, since 23.05 the default is mbedtls, installing openssl is optional, and wolfssl is downright discouraged. Current main branch has mbedtls 3.6, which should include armv8 hardware crypto engine support ( support has been merged since 2023). Therefore trunk mbedtls, with software thats -mbedtls should just use hardware by default, i think. Though i admit, i did not test this, as i'm not really using openvpn anywhere.
Hi,
short question, received my r3s with 2+32 yesterday and installed FriendlyWRT to test the unit... can i flash the releases from wh2k9 also with the RKDev tool or what's the way to get they running?
Have not tried flashing through FriendlyWRT, although in theory that should work. The usual way is to use dd or similar tools (e.g. Rufus on Windows) to write the image to a microSD card and then you can directly boot off that.
Hi all,
after flashing the firmware on the emmc I can't get the device booting through the sd card anymore. Is it that the standard behaviour?
How can I get back this option?
I'm pretty sure the MASK button is for this purpose. ie try holding the button while powering up the device. For more precise description you could always consult the friendlyelec wiki.
With friendlywrt installed onto emmc, the sd card still keeps priority on boot without using the maskrom mode (which looks like a more drastic resource), so I would have expected the same by openwrt.
This device runs very well.
However I'm a bit confused by the presence of the emmc where I'd rather install openwrt.
The only way I found to expand root partition and filesystem on emmc is using ext4.
In such scenario, if you mess something (and I'm a very talented messer), you have to unbrick the device since there are no reset options and after openwrt installation on the emmc, booting from SD card doesn't work anymore.
Until my configuration won't be stable, it's safer for me to keep the system on the SD card.
Worst comes to worst, you can always access the system u-boot via serial debug and force microSD boot (admittedly this is inconvenient). Otherwise, this article might be helpful:
Interesting, even if it is out of my knowledge range.
I've never tried serial debug but unbrick the device via the mask button is not so hard, otherwise pressing reset button is easier to do.
At this point the simplest and direct (and safest and fastest to me) approach is tryng to expand squashfs filestystem on the emmc in order to keep a working reset button.
I think the only way is building a custom image
My device is running really well, no complaints so far.
Thank you @wh2k9 for working on this.
The only way I found to expand root partition and filesystem on emmc is using ext4.
Did you follow the guide at https://openwrt.org/docs/guide-user/advanced/expand_root ? I was confused as well why it was not working after trying both the manual and automated process, as it turns out it only expands AFTER you do a sysupgrade (which makes sense if you think about why).
I did get stuck a few times in the process of installing snapshot Openwrt and had to debrick twice. With Openwrt on the SD card it seemed to have a hard time installing, it's like it bricked the system. I don't remember exactly how I fixed it but I think it went like: debrick with Maskrom > install FriendlyWrt > use eMMC tools inside FriendlyWrt to install snapshot OpenWrt > boot into Openwrt > do the script to expand partitions in the eMMC > do a sysupgrade > reboot into Openwrt. After this it was working just peachy.
You should not really use snapshot for now if you just want to use this device. 24.10-rc2 works perfectly, and can be installed easily to a microsd card.
