Closed ThomasKaiser closed 5 months ago
Thanks for the information! Indeed, it seems like they changed the order at some point. I've pushed a commit that should fix it, can you confirm if it works in your machines?
RK3588 gets now 'detected' as that:
root@rock-5b:/home/tk# /usr/local/src/cpufetch/cpufetch
SoC: Rockchip RK3588
Technology: 8nm
CPU 1:
## Microarchitecture: Cortex-A55
###### ## ## Max Frequency: 1.800 GHz
##. ### ##### ##### ## .## ##### ######. ## ##### Cores: 4 cores
#######. ##. # #. ##### ##. ### ### # .## Features: NEON,SHA1,SHA2,AES,CRC32
##. ###. ####. #### ### .## #### ### ### #.##### CPU 2:
## Microarchitecture: Cortex-A76
Max Frequency: 2.400 GHz
Cores: 4 cores
Features: NEON,SHA1,SHA2,AES,CRC32
Peak Performance: 211.20 GFLOP/s
My own try to distinguish between RK3588 and RK3588S is here:
Few NVMEM samples collected (in brackets the SoC revision according to dmesg
output)
RK3588s:
NanoPi R6C (35880000) 52 4b 35 88 91 fe 33 41 5a 43 39 36 00 00 00 00 |RK5...3AZC96....|
NanoPi R6C (35881000) 52 4b 35 88 12 fe 33 41 32 47 50 4b 00 00 00 00 |RK5...3A2GPK....|
Orange Pi 5 (35880000) 52 4b 35 88 12 fe 33 41 32 38 4b 47 00 00 00 00 |RK5...3A28KG....|
ROCK 5A (35881000) 52 4b 35 88 12 fe 33 41 32 4e 55 57 00 00 00 00 |RK5...3A2NUW....|
^^
RK3588:
Orange Pi 5 Plus (35880000) 52 4b 35 88 12 fe 21 41 32 42 44 4e 00 00 00 00 |RK5...!A2BDN....|
Orange Pi 5 Plus (35881000) 52 4b 35 88 12 fe 21 41 32 4e 48 46 00 00 00 00 |RK5...!A2NHF....|
ROCK 5B (35880000) 52 4b 35 88 12 fe 21 41 32 34 39 57 00 00 00 00 |RK5...!A249W....|
ROCK 5B (35880000) 52 4b 35 88 12 fe 21 41 32 38 43 35 00 00 00 00 |RK5...!A28C5....|
ROCK 5B (35880000) 52 4b 35 88 12 fe 21 41 32 38 46 55 00 00 00 00 |RK5...!A28FU....|
ROCK 5B (35880000) 52 4b 35 88 12 fe 21 41 32 38 52 34 00 00 00 00 |RK5...!A28R4....|
ROCK 5B (35880000) 52 4b 35 88 12 fe 21 41 32 47 50 48 00 00 00 00 |RK5...!A2GPH....|
ROCK 5B (35880000) 52 4b 35 88 91 fe 21 41 5a 43 34 31 00 00 00 00 |RK5...!AZC41....|
^^
But same situation as before with RK3568 (since a typo slipped in):
root@nanopi-r5s:/home/tk# /usr/local/src/cpufetch/cpufetch -v
[WARNING]: SoC detection failed using /proc/cpuinfo: No string found
[WARNING]: read_file: /sys/bus/nvmem/devices/rockchip-efuse0/nvmem: No such file or directory
[ERROR]: RK SoC was found but it does not match any known SoCs: 0x3568
[VERSION]: cpufetch v1.04-35-g5e00 (Linux ARM build)
SoC: Unknown
Technology: Unknown
Microarchitecture: Cortex-A55
Max Frequency: 1.992 GHz
Cores: 4 cores
Features: NEON,SHA1,SHA2,AES,CRC32
Peak Performance: 63.74 GFLOP/s
After manually fixing the typo it works as expected:
root@nanopi-r5s:/usr/local/src/cpufetch# ./cpufetch
SoC: Rockchip RK3568
## Technology: 22nm
###### ## ## Microarchitecture: Cortex-A55
##. ### ##### ##### ## .## ##### ######. ## ##### Max Frequency: 1.992 GHz
#######. ##. # #. ##### ##. ### ### # .## Cores: 4 cores
##. ###. ####. #### ### .## #### ### ### #.##### Features: NEON,SHA1,SHA2,AES,CRC32
## Peak Performance: 63.74 GFLOP/s
Thanks again for your feedback, I've fixed the typo. Regarding RK3588/S, checking dmesg is not something that I will do for now, maybe in the future we find more straightforward ways. For now I'm closing this issue, but I'll keep an eye on future updates on this :+1:
Regarding RK3588/S, checking dmesg is not something that I will do for now
Sorry for the misunderstanding. 'My' differentiation is solely based on nvmem
contents (byte 7: 33
vs. 21
), the only thing derived from parsing dmesg
is the 'SoC revision' as I call it to check whether this difference is consistent.
Hi there,
starting from at least RK35xx Rockchip seems to have reverted the relevant SoC bits (confirmed with at least RK3528, RK3566, RK3568 and RK3588/RK3588s):
RK3568 in NanoPi R5S:
And the RK3588 in my Rock-5B is wrongly reported as RK3588s: