A Word on Packaging

Unlike the first two iPads, the 3rd generation iPad abandons the high density flip-chip PoP SoC/DRAM stack and uses a discrete, flip-chip BGA package for the SoC and two discrete BGA packages for the DRAMs.

If you think of SoC silicon as a stack, the lowest layer is where you'll find the actual transistor logic, while the layers of metal above it connect everything together. In the old days, the silicon stack would sit just as I've described it—logic at the bottom, metal layers on top. Pads around the perimeter of the top of the silicon would connect to very thin wires, that would then route to the package substrate and eventually out to balls or pins on the underside of the package. These wire bonded packages, as they were called, had lower limits of how many pins you could have connecting to your chip.

There are also cooling concerns. In a traditional wire bonded package, your cooling solution ultimately rests on a piece of your packaging substrate. The actual silicon itself isn't exposed.

As its name implies, a flip-chip package is literally the inverse of this. Instead of the metal layers being at the top of the stack, before packaging the silicon is inverted and the metal layers are at the bottom of the stack. Solder bumps at the top of the silicon stack (now flipped and at the bottom) connect the topmost metal layer to the package itself. Since we're dealing with solder bumps on the silicon itself rather than wires routed to the edge of the silicon, there's much more surface area for signals to get in/out of the silicon.

Since the chip is flipped, the active logic is now exposed in a flip-chip package and the hottest part of the silicon can be directly attached to a cooling solution.


An example of a PoP stack

To save on PCB real estate however, many SoC vendors would take a flip-chip SoC and stack DRAM on top of it in a package-on-package (PoP) configuration. Ultimately this re-introduces many of the problems from older packaging techniques—mainly it becomes difficult to have super wide memory interfaces as your ball-out for the PoP stack is limited to the area around your die, and cooling is a concern once more. For low power, low bandwidth mobile SoCs this hasn't really been a problem, which is why we see PoP stacks deployed all over the place.

Take a look at the A5, a traditional FC-BGA SoC with PoP DRAM vs. the A5X (this isn't to scale):


Images courtesy iFixit

The A5X in this case is a FC-BGA SoC but without any DRAM stacked on top of it. The A5X is instead covered in a thermally conductive paste and then with a metallic heatspreader to conduct heat away from the SoC and protect the silicon.

Given the size and complexity of the A5X SoC, it's no surprise that Apple didn't want to insulate the silicon with a stack of DRAM on top of it. In typical package-on-package stacks, you'd see solder bumps around the silicon, on the package itself, that a separate DRAM package would adhere to. Instead of building up a PoP stack here, Apple simply located its two 64-bit DRAM devices on the opposite side of the iPad's logic board and routed the four 32-bit LP-DDR2 memory channels through the PCB layers.


iPad (3rd gen) logic board back (top) and front (bottom), courtesy iFixit

If I'm seeing this correctly, it looks like the DRAM devices are shifted lower than the center point of the A5X. Routing high speed parallel interfaces isn't easy and getting the DRAM as close to the memory controller as possible makes a lot of sense. For years motherboard manufacturers and chipset vendors alike complained about the difficulties of routing a high-speed, 128-bit parallel DRAM interface on a (huge, by comparison) ATX motherboard. What Apple and its partners have achieved here is impressive when you consider that this type of interface only made it to PCs within the past decade.

Looking Forward: 12.8GB/s, the Magical Number

The DRAM speeds in the new iPad haven't changed. The -8D in the Elpida DRAM string tells us this memory is rated at the same 800MHz datarate as what's used in the iPhone 4S and iPad 2. With twice the number of channels to transfer data over however, the total available bandwidth (at least to the GPU) doubles. I brought back the graph I made for our iPhone 4S review to show just how things have improved:

The A5X's memory interface is capable of sending/receiving data at up to 12.8GB/s. While this is still no where near the 100GB/s+ we need for desktop quality graphics at Retina Display resolutions, it's absolutely insane for a mobile SoC. Bandwidth utilization is another story entirely—we have no idea how good Apple's memory controller is (it is designed in-house), but there's 4x the theoretical bandwidth available to the A5X as there is to NVIDIA's Tegra 3.

There's a ton of memory bandwidth here, but Apple got to this point by building a huge, very power hungry SoC. Too power hungry for use in a smartphone. As I mentioned at the start of this article, the SoC alone in the new iPad can consume more power than the entire iPhone 4S (e.g. A5X running Infinity Blade 2 vs. iPhone 4S loading a web page):

Power Consumption Comparison
  Apple A5X (SoC + mem interface) Apple iPhone 4S (entire device)
Estimated Power Consumption 2.6W—Infinity Blade 2 1.6W—Web Page Loading

There's no question that we need this much (and more) memory bandwidth, but the A5X's route to delivering it is too costly from a standpoint of power. There is a solution to this problem however: Wide IO DRAM.

Instead of using wires to connect DRAM to solder balls on a package that's then stacked on top of your SoC package, Wide IO DRAM uses through-silicon-vias (TSVs) to connect a DRAM die directly to the SoC die. It's an even more costly packaging technique, but the benefits are huge.

Just as we saw in our discussion of flip-chip vs. wire bonded packages, conventional PoP solutions have limits to how many IO pins you can have in the stack. If you can use the entire silicon surface for direct IO however, you can build some very wide interfaces. It also turns out that these through silicon interfaces are extremely power efficient.

The first Wide IO DRAM spec calls for a 512-bit, 200MHz SDR (single data rate) interface delivering an aggregate of 12.8GB/s of bandwidth. The bandwidth comes at much lower power consumption, while delivering all of the integration benefits of a traditional PoP stack. There are still cooling concerns, but for lower wattage chips they are less worrisome.

Intel originally predicted that by 2015 we'd see 3D die stacking using through-silicon-vias. Qualcomm's roadmaps project usage of TSVs by 2015 as well. The iPhone won't need this much bandwidth in its next generation thanks to a lower resolution display, but when the time comes, there will be a much lower power solution available thanks to Wide IO DRAM.

Oh and 2015 appears to be a very conservative estimate. I'm expecting to see the first Wide IO memory controllers implemented long before then...

The GPU & Apple Builds a Quad-Channel Memory Controller The Impact of Larger Memory
Comments Locked

234 Comments

View All Comments

  • kwamayze - Friday, March 30, 2012 - link

    WOW!!! What a nice review!!! Well done
  • michalkaznowski - Saturday, March 31, 2012 - link

    Just to say as always a brilliant view. Your site is a must view for any enthusiast here in the UK. I also have appreciated your wireless router reviews of the Airport Extreme Base Station. Only you have pointed out that it has a quantum leap stability when compared to other makes of routers, something that a group of us have had to find out a very hard, frustrating and long way!

    Michal
  • x0rg - Saturday, March 31, 2012 - link

    I have a suggestion. Instead of taking pictures you could take screenshots of these devices when you show how beautiful the screen is while working with Remote Desktop. Pictures taken with the camera look terrible and the whole concept of taking pictures instead of screenshots seems unprofessional for the portal like AnandTech. Things like focus, gamma, apperture are not affecting the picture quality when you just take a screenshot (Home+Power on iPad, you know that). Please replace these terrible pictures with screenshots. Thank you.
  • slashbinslashbash - Sunday, April 1, 2012 - link

    You missed the whole point of that part of the review. The point of the photos was to show that the text over Remote Desktop is actually readable in real-world use. A screenshot wouldn't convey that information.

    Imagine this. Say you took an iPhone 4 screenshot of the same scene in Remote Desktop, and you posted it on the site. This would be a 640x960 pixel image. Text would be readable on a desktop monitor, but it would probably not be readable on the actual 3.5" iPhone screen. That is the question, and it applies equally to the iPad3 review. A screenshot just shows you what pixels the iPad is showing; a photo shows you how those pixels look in real-life.
  • x0rg - Thursday, April 5, 2012 - link

    I agree, my bad.
  • TekFanChris - Sunday, April 1, 2012 - link

    Thank you Anand and Vivek! You guys always take the iPad reviews to the next level. Comprehensive and complete.

    Cheers.
  • Death666Angel - Monday, April 2, 2012 - link

    That kinda reminded me of the PS2 vs PC quality back in the days. :D
  • josemonmaliakal - Monday, April 2, 2012 - link

    Hi Your article seems be so good . And i have got something about the upcoming iPhone 5 of Apple here @ http://wp.me/p2gN9B-lq
  • Wardawg - Thursday, April 5, 2012 - link

    You forget the new iPad just came out 95% of the apps have not upgraded for the new retina display yet. So all of these comparisons are very inaccurate. It doesn't matter that the iPad has higher res and 3.1 million pixels if the app isn't upgraded for retina display it won't display as such you would expect. I expect you guys to make a new article soon fixing these concerns of mine with this article.
  • Noobuser45 - Monday, April 9, 2012 - link

    Anand, you're the only tech expert that I trust so I would love to have my mind put at ease with a definitive answer from you. Is it fine to charge the iPad whenever you want? Can I charge without running it down first? Can I charge for a while and unplug it before it has reached a full charge? Can I use it while it's charging? I just don't want to screw up the battery life.

Log in

Don't have an account? Sign up now