RPi rev 2.0 explained

It was not "leaked"

Well 'leaked' as in someone received one and posted the photo before they announced it.  Sounds like that happened at least a couple of weeks before they were ready. Still, could all be theatre..

It also makes you wonder if Farnell actually have quite low buffer stock and so got to the new ones quicker than expected, or if it was just random chance with what was on top of the pile.

From the software side is not that a big deal if you somehow can read a variable that tells on which board rev you are running, which they did by burning a code revision number on the BCM SoC.

Until you get a devicetree kernel...  at that point you need to know the version of the board, and whether the bootloader has already 'fixed' things for you.

I also saw mention that they'd consider a patch to current kernels to reverse the kernels view of the I2C channels - if there was enough demand.  So same problem, I know from the revision number I have a v2, but that doesn't tell me if the kernel has been patched or not. Therefore the only thing to do is to probe both I2C busses (hopefully ignoring the one connected to HDMI) to see if I can find the device I'm looking for.

Probing random things on the bus could be bad, the i2c-tools utilities are filled with warnings about it. Something gets confused and sends data for the camera module to HDMI and kills someones TV isn't going to go down well. Ok, maybe that's unlikely, but usual problem is that the majority of people getting a Pi are not the experienced engineer who'll get it right.

"Has anyone seen any proper explanation of the reasoning behind moving the I2C channels ?  Not sure if I missed something, but I don't see anything in the datasheet to suggest there's any difference between them, so not clear why the switch was necessary."

They wanted to get I2S working. If you look at the BCM2835 datasheet you will see that GPIO28-31 has on it the options of I2S or 4 GPIO or on two lines I2C0!

Now it seems like they saw the opportunity not to end up with boards connected to the 26pin GPIO connector just having RTC or I2S.

We at CJE Micros/4D have made an effort on our RTC/Temp Sensor to allow pass through of all 26 lines but the connector to do so is very expensive.

We have already worked out how we can fit a new design RTC/temp Sensor to the new connector, above the board or below ( though if above it will like our existing design make plugging into the DSI display connector difficult/impossible)

Makes good sense to me though it will mean having to do two versions of our boards as we would like to advantage of the new connector.

GPIO28-31 has on it the options of I2S or 4 GPIO or on two lines I2C0!

Ok, on I2S, but I2C0 is now shared with the camera connector.  If, as the blog post suggested, it's used 'heavily' by the camera it could end up not being the best place to put a RTC, never mind other stuff.

We have already worked out how we can fit a new design RTC/temp Sensor to the new connector,

You have the pinout for P5 ?

though it will mean having to do two versions of our boards as we would like to advantage of the new connector.

That's my point, you now need two boards.. How many existing Rpi are out there without P5 that won't be able to use the new version of your board ?

I'll be changing my designs to take account of the new connectors and pinouts.  But that's mainly because if one of my v1 boards ever fails it'll now be getting replaced with a v2

I wrote:

>No mention that I can see of FCC/CE residential certification

Much to my surprise, Eben says that Class B FCC/CE certification

will have to wait for the educational release board.

http://www.raspberrypi.org/archives/1929#comment-31756

Back on May 31, Eben said: "there's pcb level work going on

at the moment to accomplish that".

http://www.youtube.com/watch?v=WIf4Fk2252A

starting at about 17:35

Liz has said on April 10, 2012 at 7:04 pm, in page 3 of the

comments to this article: http://www.raspberrypi.org/archives/978

"Happily, we’ve found it doesn’t need a shielded enclosure to

reach Class B, although it will require a (very minimal) redesign."

If the redesign really is "very minimal" and was underway as of

May 31, I'd expect it would have been included in rev 2.0.

With the new revision, will P2 and P5 be populated?  Or will we have to solder our own pins on?  This seems like a warrenty issue as well - solder and warrenty is void.

There was mention that P5 would not be populated, at least for now.

I've not found a use for P2 yet, what are you doing with it that would require you to solder one on ?   Unless I misunderstood, thet were allowing all of the arm jtag to appear on P5 ?

P2 has a 3v3 pin and 2 GND pins that could be useful.

P5 is the main expansion of the GPIO and will include GPIO 7 -10 (4 extra ones onto of the current 8 GPIOs) and will include an extra 5v, 3v3 and 2 GNDs.

That is why I though It was interesting that they were not populated when they can be used as GPIO or extra power.

Also, the P2 header is currently populated on the current board - why would you need to change this when it is aready on?

Strange.

Another hires picture of the Rev2 board.

Glad to see that the voltage regulators are from ON Semi and not the cheap chinese knock off, one of which I found had a huge drift in function of temperature.

P2 does not seem to be populated on this revision.

P5 location is kind of ugly, but better than nothing. Audio jack is blue instead of black.

Lets hope they start populating P5 shortly.  Thanks for the reply.