Yea, it looks like they moved a VRM.
Do you have a small 3 legged SOT component near the I in MICRO SD on the bottom?
The area around the PMIC looks identical so I assume the USB-C CC fix hasn't gone in yet. I'd expect an extra resistor and the parts to move around slightly accomodate it.
Ah, you're a wee pedant. I knew what I meant. I've submitted a pull request for the RPF revision number documentation (since we've now seen one in the wild).
See my previous post. The three-legged SOT is on the board edge, hence 1.1.
So far as I can tell...that's backwards. The resistors are so that the PSU can sense what voltage and current levels to supply to the Pi. If the Pi is misidentified or can't be identified, a "smart" PSU/cable will supply the default of 5v at 900mA.davidcoton wrote: ↑Mon Dec 02, 2019 11:23 pmThat depends. There are various levels of fix. R1 could be repurposed, leaving no capability on the Pi to sense the remote PD resistors. Then it would be a tracking change only. At the other extreme, both R1 and R79 need to be duplicated (and possibly a value change for R1), to give full sensing capability in both plug orientations. I'm not certain whether the Pi needs to sense the remote PD resistors -- I think (though I may be wrong) that only purpose is to control power delivery from the Pi via USB-C, and I see no sign of the circuitry necessary for that (it would be tricky to permit power input and control power output in different circumstances on the same connections).
Actually, it's a misidentification that's causing the lack of power. The Pi is being detected as a self powered audio device, so the PSU sends no power.
No, the resistors are there to establish whether a port is a host or a device, and hence (among other things) if VBUS should supply an initial 5V. If a USB C device wants to activate higher current modes it needs to negotiate that using power delivery communications.
This stating that you personally have one in hand? Merely analyzing what the prior poster typed?
It shows in the photos that Cakeslob posted. I'm assuming they're genuine.ehem wrote: ↑Wed Dec 04, 2019 2:42 amThis stating that you personally have one in hand? Merely analyzing what the prior poster typed?
If you're confirming then we've got a confirmation from a long-term registered user. The previous poster was new here, though they still increment the count of supporting reports. (grr, US Snail is sure transporting that case slowly, so no comments until tomorrow)
Have you observed any differences?
Could personnel from the Raspberry PI Foundation give a time-frame for when the foundation will be admitting to the existence of this variant and what changed?
Your silkscreen is completely different to the one in the hatenablog.jp post. It looks more like the UK purchased Pi 4 I have as it doesn't have all the certification numbers. One strange difference is that the solder connections for the stacked USB 3.0 port has a white silkscreen square over it on yours.
Why not just ask the operating system what board you're running.
That is what I meant by "appears to be the v1.2 board". The software is reporting values consistent with the reports of the v1.2 board, `cat /proc/cpuinfo` and find "Revision : c03112", "Model : Raspberry Pi 4 Model B Rev 1.2". I won't claim to have the longest history on this board, but hopefully I have enough for Cob to accept my report as believable.DougieLawson wrote: ↑Thu Dec 05, 2019 8:59 amWhy not just ask the operating system what board you're running.
grep -i 'revision' /proc/cpuinfo then decode the revision number (heres a clue: the last digit is the version)
No direct evidence that the rev. 1.2 fixes the USB-C issue has been presented. It's also not clear that fixing that is much of a priority, especially since the less expensive ways to power a Pi4B don't run into the issue.
What mess? Are you talking about the massively overblown click bait articles about the USB C power problem? Its a complete non issue except for those people with power supplies that cost three times the pi itself, or those people who get money from clicks.