Processor identification
Rick Murray (539) 13840 posts |
Hi, The little program below should return the Processor ID on the modern systems. If you have such a system, could you please run this program and let me know what the result is?
As far as I am aware, the usual distributions of RISC OS are for:
Have I missed any? ;-) All of the Pi1 are likely to report the same thing. Ditto the Pi2… Thanks. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
rob andrews (112) 200 posts |
Hi this is an OMAP5432EVM cpu ID &412FC0F2 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Chris Hall (132) 3554 posts |
could you please run this program and let me know what the result is? Yes. Hope this helps. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Steve Pampling (1551) 8170 posts |
Interesting RPCEmu gives &4401A102 and the old processor message |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Rick Murray (539) 13840 posts |
Wow, Chris, that’s a heck of a collection. It looks like the BCM2835 boards (Pi 1/Compute/Zero) all have an ID of BTW, what do you mean by the Pi Model A+ “can’t find it”? For others reading, the devices outstanding on the list are:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
Rick Murray (539) 13840 posts |
This means…
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
Chris Mahoney (1684) 2165 posts |
Just tested my Pi 1 and 3 and I get the same results. As expected, but just confirming :)
Presumably that it’s hiding in a drawer somewhere! |
|||||||||||||||||||||||||||||||||||||||||||||||||||
David Pitt (102) 743 posts |
Found it in this drawer |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Stephen Unwin (1516) 154 posts |
Just for completeness, RPi A+ returns the same as A/B/B+ etc. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Sprow (202) 1158 posts |
Apropros yesterday’s thread about using defined APIs rather than making assumptions about machine level detail, you probably want OS_PlatformFeatures. This SWI insulates you from ARM’s ever changing definition of the CPU ID register, in fact ARM spilled out into lots more than just one ID register now. Gone are the days when you could say “ah, ARM7, so it has 8k caches”. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
John Rickman (71) 646 posts |
My Iyonix reported:- |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Rick Murray (539) 13840 posts |
I was wondering when somebody would join the dots. ;-) Problem is, if a nice API is created tomorrow, it doesn’t help those using older versions (like those who prefer to stick to the “stable” versions). Plus, in my specific case (which IIC bus is the expansion), it would be serious feature creep for PlatformFeatures to return that.
I noticed. That code is a cut down version of my CPUinfo program which “should” cover ARM6 to the Cortex-A8 (and similar). The code for parsing the ID word is rather horrible.
Yup. That’s the extended ID stuff. So the processor can finally report useful stuff about its behaviour. Rather necessary given the many permutations of the ARM design around these days, though thankfully in our “world” they’re all fairly similar at application level. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Rick Murray (539) 13840 posts |
For people who’d like more details on their processor (tested on a Pi and emu, should work on ARM6+): http://heyrick.co.uk/random/cpuinfo,ff8 Note that even with the shiny new tell-us-lots identification, it appears that the interpretation of some bits vary (does bit=0 mean this or…?) from one core to the next… ;-) |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Rick Murray (539) 13840 posts |
Still outstanding – CPU ID for the original Beagleboard (OMAP3530), and the original Pandaboard (OMAP4430). |