Advanced

Raspberry Pi 3 Released

Posted by bob on · 34 comments
Raspberry Pi Foundation; By Eben Upton
Mail this story
Print this story

Raspberry Pi 3 is now on sale for $35 (the same price as the existing Raspberry Pi 2), featuring: A 1.2GHz 64-bit quad-core ARM Cortex-A53 CPU (~10x the performance of Raspberry Pi 1), Integrated 802.11n wireless LAN and Bluetooth 4.1, Complete compatibility with Raspberry Pi 1 and 2.

Exactly four years ago, on 29 February 2012, we unleashed the original 256MB Raspberry Pi Model B on a largely unsuspecting world. Since then, we’ve shipped over eight million units, including three million units of Raspberry Pi 2, making us the UK’s all-time best-selling computer. The Raspberry Pi Foundation has grown from a handful of volunteers to have over sixty full-time employees, including our new friends from Code Club. We’ve sent a Raspberry Pi to the International Space Station and are training teachers around the world through our Picademy program.

In celebration of our fourth birthday, we thought it would be fun to release something new. Accordingly, Raspberry Pi 3 is now on sale for $35 (the same price as the existing Raspberry Pi 2), featuring:

- A 1.2GHz 64-bit quad-core ARM Cortex-A53 CPU (~10x the performance of Raspberry Pi 1)

- Integrated 802.11n wireless LAN and Bluetooth 4.1

- Complete compatibility with Raspberry Pi 1 and 2



BCM2837, BCM43438 and Raspberry Pi 3

For Raspberry Pi 3, Broadcom have supported us with a new SoC, BCM2837. This retains the same basic architecture as its predecessors BCM2835 and BCM2836, so all those projects and tutorials which rely on the precise details of the Raspberry Pi hardware will continue to work. The 900MHz 32-bit quad-core ARM Cortex-A7 CPU complex has been replaced by a custom-hardened 1.2GHz 64-bit quad-core ARM Cortex-A53. Combining a 33% increase in clock speed with various architectural enhancements, this provides a 50-60% increase in performance in 32-bit mode versus Raspberry Pi 2, or roughly a factor of ten over the original Raspberry Pi.

James Adams spent the second half of 2015 designing a series of prototypes, incorporating BCM2837 alongside the BCM43438 wireless “combo” chip. He was able to fit the wireless functionality into very nearly the same form-factor as the Raspberry Pi 1 Model B+ and Raspberry Pi 2 Model B; the only change is to the position of the LEDs, which have moved to the other side of the SD card socket to make room for the antenna. Roger Thornton ran the extensive (and expensive) wireless conformance campaign, allowing us to launch in almost all countries simultaneously. Phil Elwell developed the wireless LAN and Bluetooth software.

All of the connectors are in the same place and have the same functionality, and the board can still be run from a 5V micro-USB power adapter. This time round, we’re recommending a 2.5A adapter if you want to connect power-hungry USB devices to the Raspberry Pi.

Raspberry Pi 3 is available to buy today from our partners element14 and RS Components, and other resellers. You’ll need a recent NOOBS or Raspbian image from our downloads page. At launch, we are using the same 32-bit Raspbian userland that we use on other Raspberry Pi devices; over the next few months we will investigate whether there is value in moving to 64-bit mode. FAQS

We’ll keep updating this list over the next couple of days, but here are a few to get you started.

Are you discontinuing earlier Raspberry Pi models?

No. We have a lot of industrial customers who will want to stick with Raspberry Pi 1 or 2 for the time being. We’ll keep building these models for as long as there’s demand. Raspberry Pi 1 Model B+ and Raspberry Pi 2 Model B will continue to sell for $25 and $35 respectively.

What about Model A+?

Model A+ continues to be the $20 entry-level Raspberry Pi for the time being. We do expect to produce a Raspberry Pi 3 Model A, with the Model A+ form factor, during 2016.

What about the Compute Module?

We expect to introduce a BCM2837-based Compute Module 3 in the next few months. We’ll be demoing Compute Module 3 at our partners’ launch events this morning.

Are you still using VideoCore?

Yes. VideoCore IV 3D is the only publicly documented 3D graphics core for ARM-based SoCs, and we want to make Raspberry Pi more open over time, not less. BCM2837 runs most of the VideoCore IV subsystem at 400MHz and the 3D core at 300MHz (versus 250MHz for earlier devices).

Where does the “10x performance” figure come from?

10x is a typical figure for a multi-threaded CPU benchmark like SysBench. Real-world applications will see a performance increase of between 2.5x (for single-threaded applications) and >20x (for NEON-enabled video codecs).

Credits

A project like this requires a vast amount of focused work from a large team over an extended period. A partial list of those who made major direct contributions to the BCM2837 chip program, BCM43438 integration and Raspberry Pi 3 follows: Dinesh Abadi, James Adams, Cyrus Afghahi, Sayoni Banerjee, Jonathan Bell, Marc Bright, Srinath Byregowda, Cindy Cao, KK Chan, Nick Chase, Nils Christensson, Dom Cobley, Teodorico Del Rosario Jr, Phil Elwell, Shawn Guo, Gordon Hollingworth, Brand Hsieh, Andy Hulbert, Walter Kho, Gerard Khoo, Saran Kumar, Yung-Ching Lee, David Lewsey, Xizhe Li, Simon Long, Scott McGregor, James Mills, Alan Morgan, Kalevi Ratschunas, Paul Rolfe, Matt Rowley, Akshaye Sama, Serge Schneider, Shawn Shadburn, Mike Stimson, Stuart Thomson, Roger Thornton, James Tong, James Turner, Luke Wren. If you’re not on this list and think you should be, please let me know, and accept my apologies.

  Nav
» Read more about: Story Type: Announcements; Groups: Embedded, Raspberry Pi

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (34)

14 earlier comments in the full thread.

@skelband:

just did...

I agree. OpenElec is the way to go for a media center. It connects to my DLNA server and is much faster than my 'smart TV.' I suppose now, every TV will be a smart TV with a $35 RPi box.

No more hidden ad networks or weird open ports.
> No more hidden ad networks or weird open ports.

Exactly. I spend a lot of time protecting my right to privacy, and it was very refreshing finally moving away from proprietary media solutions over to a FOSS solution. No more wasted time with Wireshark trying to determine which apps were not calling home so that I could safely open my firewall to them.

To me a "smart TV" is not an marketing advantage. A vendor controlled closed proprietary smart TV is a liability, it just means more work for me before I could deploy and use it.

Firewall your TV and replace the "smarts" with an RPi (or an Odroid-C2).
UPS truck arrived !

@OpenElec for RPi....

I don't like systems that have an unchangeable default root password.

I guess I'm going to have to "unsquash" the thing like this:

https://www.dustpla.net/howto-update-openelec-root-ssh-password/
I found the original Pi to be useful with Kodi on it, but when using WiFi it would often choke on 1080p video. Since I upgraded the unit in the living room to a Pi 2, I haven't had any issues with 1080p video. I admit that I use NFS on my file server to make the network faster, though I'm not sure this is really necessary anymore with the Pi 2. OSMC is my current favorite pure Kodi system for use on the Pi 2.

For video on a Pi in desktop mode (or from the command line) I've always used omxplayer.

I'm not really concerned with 2160p video. To me, it doesn't seem worth the file size and bandwidth it uses. Some of my Blu-Rays are ripped to 720p just because it takes up less space. I still have more movies at 480p than at higher resolutions, and I don't really feel deprived when I watch them (of course, quite a number of them don't have a release at higher resolution).
RPi3 -- first impressions:

- Just unplugging an sdcard from a working RPi2 doesn't bring up an RPi3. A download of the current Raspbian and a fresh dd to an sdcard was what it took to bring it up.

- The on-board Wifi came right up with a WPA2 login screen and the association was quick with no fuss, however, dhcp was not invoked correctly and an incorrect IP address was assigned to the wlan0 interface. I had to configure IPV4 settings manually in order to place it in the local network. This was not really a big deal and I'm sure this will be quickly worked out, but it is likely to cause some beginners some trouble getting started.

Other than those two points, the RPi3 is performing as expected.
>an incorrect IP address was assigned to the wlan0 interface

I'm not asking you to post the errant IP address... However, I'm very curious as to how the address was 'incorrect'.

What do you mean by incorrect?
  1. Wrong address pool within the correct DHCP network.
  2. Wrong Class A net.
  3. Wrong Class C net.
Ex:
  1. 192.168.0.25 vs. 192.168.0.180
  2. 10.0.0.5 vs. 192.168.0.5
  3. 192.168.10.5 vs. 192.168.5.5
I've had some strange DHCP assignments of my own before I disabled my ISP's router's DHCP and implemented my own DHCP server and registered it as 'authoritative' ... I seem to remember even getting a DHCP assignment from openDNS or something... So, depending on the kind of 'incorrect' DHCP address, you may want to look a bit deeper into the various DHCP servers and how they are all interacting.
>an incorrect IP address was assigned to the wlan0 interface

The initial address assignment after wifi association was

169.254.225.46/16 
with a gateway assignment of:
169.254.0.0
My subnet here is a class C in 192.168...

There are six RPis (RPi1 and RPi2 models, all running Raspbian Wheezy) on this wlan all of which are successfully fetching a dhcp assignment on bootup, so there is some sort of weirdness going on with the RPi3 or more likely with the Raspbian Jessie (Feb 29, 2016) software configuration.

I didn't spend a lot time on this issue since it was easy to manually configure the settings and then just move on.
> 169.254.225.46/16 with a gateway assignment of: 169.254.0.0

That's a default IP when it can't get a dhcp address. So yes, there's something strange going on.
@169.254.0.0/16

This is the 'link-local' address range:

https://en.wikipedia.org/wiki/Link-local_address

I've seen this pop up on my network when I was figuring out how to disable the ISP dhcp server on the LAN side... my guess is there is some sort of contention between the ISP router and perhaps your own internal wireless router DHCP. If that's the way you have it setup..
It's quite possible that this problem is due to marginal signal quality on the wifi.

I've noticed that the on-board wifi antenna needs to be oriented just right, otherwise we get some packet loss. We could go on the theory that we had packet loss during the dhcp handshake which resulted in the failed IP assignment. In this case the wifi box is located on the other end of the house from the RPi3 although some of the other RPis on this network are solid with their usb wifi adapters.

@penguinist:

that's an interesting thought.

I bet you could test that using the iw utilities on the client [RPi] and looking through the DHCP and other logs on the router...

***

It wouldn't be surprising to find out that the RPi 3 wifi has a signal problem versus the USB dongles. Is there an antenna connection on the board? I haven't looked through the RPi 3 docs yet...
nodough: You suggested I check out the $40 odroid-c2 for my media center upgrade. After looking at the specs I put in an order and mine came in yesterday.

First impressions:

- The download of a 1.2GB Ubuntu image for this device took about 6 hours to complete. The servers are evidently being hit pretty hard right now.

- Odroid-c2 supports 4K/2160p at 60Hz. I don't have a 60Hz monitor, but I was able to verify it on my 4K 30 Hz monitor and it worked fine, no complaints. The hardware accelerated driver is not yet complete, so the screen is currently being updated with software (too slow for movies) but the driver is being actively worked and I'm looking forward to testing it when it comes out. The performance right now is fine for desktop use but we'll need the hardware acceleration before we have a viable media box solution.

- Ethernet at 1 Gbps was a joy to use. Transferring big files from my media storage server over to this device runs really fast. I'm thinking that this network performance will permit playing videos directly over an nfs connection without use of a local disk.

- This device supports both an sdcard and an emmc card. I'm using the sdcard right now and the speeds are quite comfortable, however the vendor claims 120MB/s speeds when running on an emmc card. That would be incredible. I just may order an emmc card so that I can check this out.

- There are some minor software stability issues, like Firefox crashes (Chromium is stable), but the vendor seems to be active in working the issues as fast as they can.

All in all, I think the odroid-c2 will be a device to watch over the weeks ahead. The specs on this device are ahead of the pack, and the developers seem to be on the right track with the software.

(This post was written using an Odroid-c2 running Ubuntu64 16.04lts-mate with the Chromium browser.)
penguinist: Thanks for the update. I've been holding off ordering more Pi. Now I'm thinking the Odroid-c2 is more to my liking.
Since my last post, a hardware accelerated kodi (alpha) has been released for the c2. I'm checking it out now and there are issues with it not handshaking correctly with a 4k monitor, so it's not ready for prime-time yet, but it's encouraging to see the work progressing rapidly.
penguinist: Normally, I wouldn't post a link to an online sale, but I think this is germane to the discussion.

One of today's NewEgg ShellShockers is a 4K UHD 28" LED 3840x2160 60Hz monitor for $279. Of course, it's a brand I've never heard of, but if you're looking for a 60Hz 4K display, now might be a good opportunity.

http://www.newegg.com/Product/Product.aspx?Item=9SIA90V3V039...

My apologies to the moderators for posting a sale link.

NoDough

P.S.: To add a little humor, here's a line from the manufacturer: "4K UHD resolution has over than 800M pixel, so it is shown the objects close to real."
@NoDough:

That is indeed interesting. The claim is that this is a 4K monitor with support for 60Hz, and the price is right. But on a closer read of the specs we see that this monitor supports hdmi 1.4a which limits performance over hdmi to 30Hz frame rates. The odroid-c2 supports hdmi 2.0 which is what we need to get true 60Hz updates. I notice also that this monitor supports DisplayPort 1.2a, and it is with DisplayPort that it reaches its 60Hz potential. But the odroid-c2 does not support DisplayPort so that would be a disconnect for us. So I'm still hunting for my hdmi2.0 / 4k / 60Hz display upgrade.

On another topic, I've been closely following the software side of the odroid-c2 and there continues to be some good work in the direction of harnessing the mali-450 hardware accelerated gpu. Right now there is a hardware accelerated framebuffer driver and there is active work to run the kodi media app on it. I've tested it and have found that it will drive 4k/30Hz (sorry I don't have a 4k/60Hz display yet) with acceleration, however there are still issues with the kodi integration, so odroid-c2 is very close to supporting 2160p/60Hz in a media center application but it's not quite there yet.
penguinist: Good catch. The devil is in the details.
Odroid-C2 update:

I've been testing the 4K hardware accelerated Kodi (formerly xbmc) on the C2, and it is starting to look pretty good. The C2 can now play 4K video with reasonably good quality. The C2 supports 60Hz but my monitor is limited to 30Hz so I can't test it at full speed, that will need to wait for a monitor upgrade. The video shows no sign of tearing or other anomalies, and is basically "watchable" right now.

The only issue I can see is that I'm getting some minor jerkiness on fast moving scenes (unnoticable on slower moving scenes). It's quite possible that the cause of this is not the C2's GPU/driver but the bandwidth limitation of the sdcard I'm using to store the video file. I have an emmc card on order which should give me a way to eliminate storage bandwidth as the cause.

All in all, I'm pretty pleased with what we have. It's time to start looking for a large screen 2160p@60Hz hdmi 2.0 tv for my next entertainment center upgrade.

On the downside, this Kodi implementation is based on fbdev framebuffer display, so we can't run a full desktop accelerated yet. That part is still in the works, but if you are happy with a dedicated Kodi system, that part seems to be in our hands.
penguinist - I'm really enjoying reading your updates, as you experiment with the Odroid-C2. Thanks for sharing your findings with us. Good Stuff!

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post