Seeking ARM CPU owners! Any QNAP firmware!

English General
1

Hello community. :nerd_face:

I’m compiling a table of NAS CPU specs to correctly determine compatible QPKGs, but I don’t have access to most of the ARM models that have been produced , so I’m hoping the community can help fill-in the blanks.

UPDATE: good news! The spreadsheet is now up-to-date. No more CPU details are presently needed. At-least, until QNAP release new ARM models. If/when that happens, I’ll post here if I’m unable to figure-out the CPU details.

See the current table here: QNAP ARM models - Google Sheets

Thank you to everyone who has contributed their NAS information.

2

Sorry, only have x86 based Qnap systems so I cannot help but wanted to mention that this is a great spreadsheet - very impressive! :+1:

Do you also have one for x86 models?

3

I think OneCD did this for App Dev reasons, x86 and x64 do not have restrictions in terms of app compatibility

4

Ok, makes sense. No matter what the original purpose may have been that google sheet is also a very good source of information for other purposes.

5

Cheers mate. :nerd_face:

Sorry, no x86 version. I remember doing a rough calculation a while back and figured it would be a spreadsheet 10 times the size of the ARM one.

And as @dolbyman correctly surmised, this sheet was only to assist with ARM QPKG development, due to the diverse range of ARM SoCs used by QNAP.

6

No problem of course. I am happy to at least have the ARM version now - that is not a small spreadsheet either!

7

Here the info :slightly_smiling_face:

TS-431P3
ARM_AL
armv7l

8

Hi @RvXA1 and welcome to the forum.

Cheers mate, but I’ve already got that one. :nerd_face:

Currently there are only 2 models left to check, these are shown in the OP.

:+1:

9

Hi Just got my brand new TS-133, the SSH command returns:
TS-133
ARM_RK
aarch64

Cheers
N.

10

Hi @Nobu and welcome to the forum. :slight_smile:

Thanks for posting the details of your NAS. That’s one more item off the list. :+1:

BTW: The CPU make in your NAS model is unknown. Would you mind checking this for me too please?

/bin/grep '^Processor name\|^model name' /proc/cpuinfo | head -n1 | /bin/sed 's/^.*: //' | tr -s ' '

If it doesn’t show a manufacturer (there are a few QNAP NAS that don’t reveal this), try checking the dmesg log for mentions of the SCMI:

dmesg | grep -i scmi
11

HI

Yes I had the same thought about the CPU identification…
In the mean time I did some other research, and it’s an Armv8-A architecture according to the ARM site (Quad-core ARM Cortex-A55 Processor @ 1.8 GHz)

Thanks again
Cheers
N.

12

Cool, that matches the information about the CPU I have (it’s already in the spreadsheet. :wink: )

What I wasn’t sure about is the make of that CPU. As your platform is ARM_RK, I suspect it will be a Rockchip device. Best-guess at this point is an RK3566.

Did you see mention of Rockchip in your dmesg output?

dmesg | grep -i scmi
13

Sorry, I didn’t further investigate in the first place, but Well spotted Sherlock! yes Rockchip is indeed mentioned via the scmi info request. (without more details…) hence the RK suffix I guess…
Cheers
N.

14

Good work mate, that’s what I needed. :nerd_face:

Cheers!

15

Just finished a major update of the sheet, filled a few empty cells, included legacy software support status, and updated existing NAS information. :nerd_face:

Exception: the ancient TS-419U II is clearly no-longer supported, but it’s not yet shown on QNAP’s product support status page (I’ve advised them of this).

As-always, if you see anything incorrect, please let me know so I can fix it.

16

Luckly we have an AI642 nearby for development. :wink:

TS-AI642
ARM_RK
aarch64

17

Oh hey, thanks mate! :nerd_face:

I opened a ticket earlier to see if someone could look it up. I’ll update the ticket now and advise this has been solved.

18

More updates:

  • decided to use the last firmware release date instead of the date on QNAP’s product support page when the firmware date is later.
  • fixed a few bugs.
  • updated the included filter views including the default.