-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Radxa Rock 5C #41
Comments
Radxa put a Rock-5-ITX and a Rock 5C Lite (RK3582 with some SoC cores disabled) in the mail. Interestingly idle consumption with 5C Lite is slightly higher than on my 5B (with same RPi USB-C power brick on same Netio powermeter):
And since you seem to have the RK3588S2 variant can you please post NVMEM contents from your board once you start testing? For my RK3582 it looks like this:
|
@ThomasKaiser - Just got shipment notification today, so I'll test when it gets here! |
...and it finally arrived today. I have RS131-D4R26, Radxa ROCK 5C 4GB, and I went to the Getting Started link on the box (https://rock.sh/5c), but can't find any place to download an image for the board. The downloads section of the page just has: I've asked over on the Radxa forums where I can find an image to boot the board and test it. I also don't see anything Armbian-wise for the Rock 5C yet, not sure where to go to get something to boot! The downloads section of Radxa's site also doesn't have any images available, just an SPL Loader. |
It's also interesting the packaging says "Radxa Compute Module", and "ROCKPI 5C" whereas the board itself says "Radxa ROCK 5C V1.1" and it seems the official name is Rock 5C. Maybe an older packaging design got through to production, but it did make me do a double take, like I had ordered a weird model or something. |
@ThomasKaiser - Thanks! It'd be nice if they linked to those anywhere on the Radxa site / Wiki :) |
Well, to arrive at Radxa's correct download locations it's quite a journey through various Github/wiki pages that contain deprecation notices, further links and so on. Also a bit worrying that the device is shipped to customers now and still only images labeled 'for internal testing' are available :) BTW: I would either choose the t3 build from https://github.com/radxa-build/rock-5c-6_1/releases or the Armbian flavour of your choice. But no idea whether the 6.1 builds work correctly asides headless use (that's all I tried to far with my 5C Lite) |
Radxa seem to still be in the 'ship hardware, then customers help us get software side running' stage. I like their hardware, but it's impossible to recommend them over something like Pi until they get out of that mindset. At minium, a full tested build should be ready before the first board is shipped (and it should be linked from the product page, downloads, wiki, etc.), or they should very prominently mark the board as 'devkit' or 'beta/alpha' (kinda like what Lichee has done with the RISC-V boards). The hardware > software side works better for accessories, like their Penta SATA HAT, than full SBCs/computers. |
@ThomasKaiser - That image download did work, I'm running kernel 6.1.x and things work okay; it seems like there's no GPU acceleration though; things are a little choppy, UI-wise. HDMI output works fine, though, unlike on CM5 with the CM4 IO Board. |
Just a quick test of the UI, it's a little stuttery (enough to be a little jarring), like when resizing windows or dragging windows around (I'd rather that decoration be turned off if it's not buttery smooth). YouTube plays back okay in 1080p, with a little stuttering at 4K. When I shut down the board, it actually powers off to < 1W (near 0W) poweroff state. Pressing the power button, it boots right back up, and consumes around 2W idle (with or without HDMI plugged in). |
@ginkage - What I don't get is how, if you can get that going as an individual in the community, Radxa can't get that going on their own OS image? Where is it even documented? Not sure if maybe Armbian has a better default image for the Rock 5C or if you have a custom concoction of kernel patches? |
I'm using a custom kernel, yes. And a custom image. And then I put some more magic on top, so I have this board running perfectly just a couple hours after having it delivered... |
😭 why can't we have nice things! :D Thanks for your work though—is there anywhere I could follow along, like do you keep build logs or a repo with patches or anything like that? It seems like it would be handy if they're not centralized anywhere else. |
I've only received my 5C a few hours ago, so no real repo yet. :)
One thing I don't have is a readily built and uploaded image you can flash though, sorry about that. And, I'm having difficulties with the wireless module. As in, I made it work, but I had to compile some extra stuff from https://github.com/radxa-pkg/aic8800 |
Using the Raspberry Pi M.2 HAT+ with the Pinedrive 2242 256GB NVMe SSD:
It's running at PCIe Gen 2 x1 speed. Benchmarking now and I'll update the post above. |
@geerlingguy could you please provide output from |
|
Thank you. So they changed their metadata format. After three weeks in rural France with only MacBooks as ARM thingies around I'm about to get back to the SBC zoo soon so I'll investigate later on my own :) |
The Rock 5c gets a couple mentions in today's video on the LattePanda Mu. |
A small question on the side: Did you have a look at using the eMMC on your Rock 5Cs? I've obtained the 5C Lite and I'm sort of lost because I cannot find an SPI loader for it. |
@cweickhmann - I didn't, sorry! |
Do you really need a special SPI loader? I've simply flashed an Armbian image to my eMMC on the 5C, and it just worked. |
No worries. The wiki says you have to and for the 5A and B there are instructions and images. And so far I've only had a blank screen when starting it up without a working µSD card (same on the Zero 3E I got in parallel, btw). I'll check if your idea just works, @ginkage . Have you had success with this on other 5s? That would be great and I'll let you know what I got. But I have the hunch that changing the SPI loader is necessary to tell it to boot from eMMC instead of µSD. |
No, it's not (at least when TF card is missing the SoC will boot from eMMC) and you'll have a hard time flashing an 'SPI loader' to a device lacking any SPI flash anyway. Wrt Radxa's 'documentation': welcome to this funny world called 'Linux on ARM'. |
If that is the case, it's unclear to me why the docs describe the process like that. I think this is not a Linux on ARM issue. It's a unclear docs issue. In particular, for whatever reason there are two things, it seems: U-Boot files labelled "... SPI ..." and one labelled "...spl..." (yeah, lower case and actually not i but L). |
Yeah, that's two different things: Serial Peripheral Interface (SPI) (totally irrelevant here since SPI NOR flash is missing on the Rock 5C) and secondary program loader (SPL). On some devices the latter can be accessed via the former (protocol). But not on Rock 5C unless you buy an adapter and then can't use eMMC any more. And of course this is a 'Linux on ARM' issue since documentation over here sucks a lot (or to be more precise this affects the 'Linux on Android e-waste' world where all the SoCs originate from we have on these cheap ARM thingies. Devices relying on those ARM SoCs from vendors who take Linux seriously (NXP, TI, Renesas and a few others) come with proper documentation and are at least three times as expensive. |
All right. Let's not get into this debate here. Maybe elsewhere ;-) So, here's my feedback so far:
Radxa's Wiki is a bit weird* as when you get to Installing The Operating System and select eMMC it guides you through a process where flashing the eMMC is done using So, I've done what many others have: Flash a small system on a µSD, put the image file on there, boot into the system and Now, it does in fact boot. At least with the Radxa-provided Debian Bullseye. *) Others may find this choice of words amusing. I know. |
rkdevtool is useful when you don't have an eMMC to USB adapter, otherwise you can simply flash eMMC directly. |
That's what I wanted to do, and in fact: after doing it there were two partitions on the eMMC, but apparently incomplete or faulty.
In any case, thanks for the feedback!
29 mai 2024 19:28:39 Ivan Podogov ***@***.***>:
…
rkdevtool is useful when you don't have an eMMC to USB adapter, otherwise you can simply flash eMMC directly.
—
Reply to this email directly, view it on GitHub[#41 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ADT5B5TQYOHHZKEIX2YETYLZEYF4FAVCNFSM6AAAAABFXMMRRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXHEZDEOBQG4].
You are receiving this because you were mentioned.
[Image de pistage][https://github.com/notifications/beacon/ADT5B5TSFHMBLMZQKORX2F3ZEYF4FA5CNFSM6AAAAABFXMMRRWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7NYOPO.gif]
|
Btw rockchip are not fusing off the disabled cores. if you are lucky youll only have some of the things disabled faulty, they can be reenabled with a uboot patch. Armbian rolling release currently has the patch https://github.com/armbian/build/blob/main/patch/u-boot/legacy/u-boot-radxa-rk35xx/board_rock-5c/reopen_disabled_nodes.patch I have two Rock 5c Lite 4gb. one only had a bad GPU and the other only a bad encoder core. you can also check what ends up being reenabled with this script provided by a user on radax forums https://forum.radxa.com/t/rk3582-soc-broken-ip-node-check/21562 its output is in chinese but its: @cweickhmann also in case anyone doesnt know the orangepi emmc module is compatiable with the rock 5c and also ime was cheaper over half the price for the same storage. |
My Lite runs with all CPU cores available since months thanks to Jianfeng's |
Hey, little update on the Rock 5C Lite plus Penta SATA HAT using Armbian in case your SATA devices just vanish after a kernel update: Armbian 2.8.4's If anyone ran into (or will run into) a similar problem, please let me know how you fixed it. For now, I'm just staying on the Armbian 24.8.2 kernel. |
Just got into possible simliar issues booting system from EMMC with Rock 5C board. The board seems not able to recognize the nvme ssd connected by pcie slot. |
Some updates in the tests. I don't have the knowledge set to dig into the issue itself, but I think this thread could be discussing the simliar issue: https://forum.armbian.com/topic/24605-issue-with-emmc-nvme/ |
@cweickhmann looks like there is a fix for that in armbian already: armbian/linux-rockchip@74b836e |
Thanks! I hope I get around to testing it this weekend. |
Hey, I skipped 24.11.1 (that your link was referring to @ddeath ) and upgraded to 24.11.2, which: Works. :-) |
Basic information
Linux/system information
Benchmark results
CPU
Power
stress-ng --matrix 0
): 9.5 Wtop500
HPL benchmark: 12.4 WDisk
Samsung Pro Plus 512GB A2 microSD card
Pinedrive 256GB 2242 NVMe via Pi 5 PCIe HAT
curl https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh | sudo bash
Run benchmark on any attached storage device (e.g. eMMC, microSD, NVMe, SATA) and add results under an additional heading. Download the script with
curl -o disk-benchmark.sh [URL_HERE]
and runsudo DEVICE_UNDER_TEST=/dev/sda DEVICE_MOUNT_PATH=/mnt/sda1 ./disk-benchmark.sh
(assuming the device issda
).Also consider running PiBenchmarks.com script.
Network
iperf3
results:iperf3 -c $SERVER_IP
: 937 Mbpsiperf3 --reverse -c $SERVER_IP
: 881 Mbpsiperf3 --bidir -c $SERVER_IP
: 930 Mbps up, 419 Mbps down(Be sure to test all interfaces, noting any that are non-functional.)
GPU
glmark2-es2
results:IMPORTANT NOTE: This test was run using the newest test release of Debian from Rockchip after the board was released. Apparently the GPU is better supported right now in Armbian builds with some custom patches applied. I have not run the board with that configuration yet, but it may be better to run Armbian if you want GPU acceleration.
TODO: See this issue for discussion about a full suite of standardized GPU benchmarks.
Memory
tinymembench
results:Click to expand memory benchmark result
sbc-bench
resultshttps://sprunge.us/5pv8oh
Phoronix Test Suite
Results from pi-general-benchmark.sh:
The text was updated successfully, but these errors were encountered: