Re: Pi5 revision ID, was: about usb3 <> ethernet adapters for raspberry pi 5

On 6/2/26 14:40, bob prohaska wrote:
> On Tue, Jun 02, 2026 at 07:50:43AM -0700, Mark Millard wrote:
>> On 6/2/26 07:29, bob prohaska wrote:
>>>
>>> I do have a Pi5 8GB, but it's confined to RasPiOS for now. I keep 
>>> hoping FreeBSD will add support for the Pi5, at least by the time 
>>> a Pi6 is offered, or something better comes along.
>>
>> Do you know if it is a D0 (modern) vs. pre-D0 (original) RPi5? The
>> labeling on top of the SOC probably indicates which, if you can see that
>> as stands.
> 
> Not sure. The aluminum case markings say
> BROADCOM 
> 2712ZPKFS8001C1T

That C1 means an older/original RPi5. It would instead list D0 there if
it was the more modern variant of the RPi5.

[RPi4's had the same sort of thing when they progressed to C0 RPi4
BCM2711's from B0. (C0 fixed the issue that lead to the RPi4B 3 GiByte
limitation that otherwise required bounce buffer usage, for example.)]

Sometimes these are referenced as: B0T, C0T, C1T, D0T (so: including the
T suffix). (But, I've no clue if the T is relevant to making any
intended distinctions.)

If you do ever experiment with the draft/partial EDK2's for the RPi5, it
would need to be the original one (or one of its forks that did not
progress to D0 instead). The EDK2 for D0 parts would not work.

> TN2342 P31    ^ 
> 340-35 B3     This numeral is smaller, like a superscript, but not raised
> 
> I don't see anything resembling D0 or D1 anywhere, but it was purchased
> from Amazon in June of 2024.

That fits with it being a C1T instead of a B0T.

> It reports
>  
> bob@raspberrypi:~$ tail /proc/cpuinfo
> Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
> CPU implementer	: 0x41
> CPU architecture: 8
> CPU variant	: 0x4
> CPU part	: 0xd0b
> CPU revision	: 1
> 
> Revision	: d04170
> Serial		: 669f8531f8edfc67
> Model		: Raspberry Pi 5 Model B Rev 1.0

These days the "New-style revision codes in use" table shows both:

d04170
5
1.0
8 GB
Sony UK

and:

d04171
5
1.1
8 GB
Sony UK

It is possible that such corresponds to the C1 (1.0/d04170?) vs. D0
(1.1/d04171?) distinction exactly. I do not see a way to find out.

> 
> Is there a better way to interrogate it?

If one enables enough of the early RPi* firmware debug output, it will
report if a "d"/"d0" *.dtbo or *.dtb is loaded vs. not. So capturing a
log of that output is something one can refer to.

> 
> Thanks for writing!
> 
> bob prohaska
> 
> 
> 


-- 
===
Mark Millard
marklmi at yahoo.com