The A6 SoC

Section by Anand Shimpi

All great tech companies have their showing up to the fight moment. I borrow this phrasing from former ATI/AMDer, current Qualcomm-er Eric Demers. While at ATI/AMD, Eric came to the conclusion that the best way to lose market share was by simply not showing up to the fight. Customers tend to spend their money at key points throughout the year (holidays, back to school, etc...). If you don't have something shiny and new when those upticks in spending happen, you're not going to win. Eric called it showing up to the fight. By showing up to the fight every year, you at least had a chance of selling whatever it is that you're trying to hock.

Intel came to a similar realization after the Pentium 4, which eventually resulted in its famous tick-tock cadence. Every year you get evolutionary improvements, either in power or performance (sometimes in both). Over the course of several years, especially if your competition isn't as aggressive, you end up with a series of products that look downright revolutionary.

Apple learned from the best and quickly adopted a similar approach after it released the iPhone in 2007. With the exception of last year's 4S launch, like clockwork, Apple brought out a new iPhone every year at around the same time. The summer launch cycle was pushed back to fall last year but, since then Apple continued its roughly 12 month cadence for the iPhone.

The smartphone SoC space is still operating on this hyper Moore's Law curve which allows for significant innovation on a yearly cadence rather than a big update every 18 - 24 months. Even Intel recognized this fact as it will shift Atom to a yearly update cadence starting towards the end of next year.

The fast pace of changes on the smartphone side combined with the similarly aggressive release schedules from its competitors explain the difference in Apple's approach to iPhone/iPad vs. new Mac releases. The former are launched with much more pomp and circumstance, and are on a 2-year chassis redesign cadence. There's also the fact that devices running iOS make up the largest portion of Apple's yearly revenue. At some point I would expect the innovation/release cadence to slow down, but definitely not for the next few years.

The first few iPhones largely leveraged Samsung designed and manufactured silicon. Back then I heard Samsung was paying close attention to Apple's requirements and fed that experience into its own SoC and smartphone design.

With a couple of successful iPhone generations under its belt, Apple set its sights much higher. Steve Jobs hired some of the brightest minds in CPU and GPU design and kept them close by. They would influence silicon supplier roadmaps as well as help ensure Apple was on the forefront of performance. Remember that CPU and GPU makers don't just set their own roadmaps, they ask their biggest customers and software vendors what they would like to see. As Apple grew in size, Apple's demands carried more weight.

Unlike the desktop/notebook CPU space, there was no truly aggressive SoC provider. The why is easy to understand. Mobile SoCs sell for $14 - $30, while the desktop and notebook CPUs that Intel invests so heavily in sell for around 10x that, despite being 1 - 4x the physical die size of their cheaper mobile counterparts. In short, most SoC providers felt that no one would be willing to pay for a big, high performance chip, so no one made them. Ultimately this led to a lot of embarassment, with companies like NVIDIA being known for their graphics prowess losing when it came to SoC GPU performance.

Realizing the lack of an Intel-like player in the mobile SoC space, Apple took it upon itself to build the silicon it needed to power the iPhone and iPad. By controlling its own SoC destiny it could achieve a level of vertical integration that no OEM has enjoyed in recent history. Apple would be able to define the experience it wanted, then work with the device, OS, application and SoC teams to deliver that experience. It's a very tempting thing to strive for, the risks are plentiful but the upside is tremendous.

The A4 SoC was Apple's first branded solution, although internally it still leveraged licensed IP blocks from ARM (Cortex A8) and Imagination Technologies (PowerVR SGX 535). Its replacement, the A5, moved to a dual-core Cortex A9 setup with a much beefier GPU from Imagination (PowerVR SGX 543MP2). For the 3rd generation iPad, Apple doubled up GPU core count and built the largest ARM based mobile SoC we've seen deployed.

When I first looked at the A4, I wrote the following:

Apple is not a microprocessor company, nor does Apple want to toss its hat in with the likes of Intel, NVIDIA, Qualcomm and TI as an SoC maker. History has shown us that the only way to be a successful microprocessor company is to be able to subsidize the high cost of designing a powerful architecture over an extremely large install base. That's why x86 survived, and it's why the ARM business model works.

Designing high performance SoCs just for use in the iPad and iPhone just doesn't make sense. In the short term, perhaps, but in the long run it would mean that Apple would have to grow the microprocessor side of its business considerably. That means tons of engineers, more resources that aren't product focused, and honestly re-inventing the wheel a lot.

The fact that the A4 appears to be little more than a 45nm, 1GHz Cortex A8 paired with a PowerVR SGX GPU tells me that Apple isn't off its rocker. I don't exactly know what Apple is doing with all of these CPU and GPU engineers in house, but licensing tech from the companies who have experience in building the architectures is still on the menu.

While I still believe that, long term, Apple will either have to commit to being a full blown chip company or buy processors from whoever ends up dominating the mobile SoC industry it's clear that for the foreseeable future Apple will be a device company that also makes mobile SoCs. Given the state of the mobile SoC space at this point, I can't blame Apple for wanting to build its own chips.

Apple SoC Evolution
  Apple A4 Apple A5 Apple A5r2 Apple A5X Apple A6
Intro Date 2010 2011 2012 2012 2012
Intro Product iPad iPad 2 iPad 2 iPad 3 iPhone 5
Product Targets iPad/iPhone 4 iPad 2/iPhone 4S iPad 2/iPhone 4S iPad 3 ?
CPU ARM Cortex A8 2 x ARM Cortex A9 2 x ARM Cortex A9 2 x ARM Cortex A9 2 x Apple Swift
CPU Frequency 1GHz/800MHz (iPad/iPhone) 1GHz/800MHz (iPad/iPhone) 1GHz/800MHz (iPad/iPhone) 1GHz 1.3GHz
GPU PowerVR SGX 535 PowerVR SGX 543MP2 PowerVR SGX 543MP2 PowerVR SGX 543MP4 PowerVR SGX 543MP3
Memory Interface 32-bit LPDDR2 2 x 32-bit LPDDR2 2 x 32-bit LPDDR2 4 x 32-bit LPDDR2 2 x 32-bit LPDDR2
Manufacturing Process Samsung 45nm LP Samsung 45nm LP Samsung 32nm LP HK+MG Samsung 45nm LP Samsung 32nm LP HK+MG

Apple's A6 is the next step in the company's evolution. Although it continues to license graphics IP from Imagination Technologies (PowerVR SGX 543MP3) and it licenses the ARMv7 instruction set from ARM, it is the first SoC to feature Apple designed CPU cores. The A6 is also the second Apple SoC to be built using Samsung's 32nm LP High-K + Metal Gate transistors. Thanks to UBM Tech Insights and Chipworks we have some great die shots of A6 as well as an accurate die size.

I've updated our die size comparison to put the A6 in perspective:

The new SoC is smaller than the A5 used in the iPhone 4S, but it's built on a newer process which will have some added costs associated with it (at least initially). Over time I would expect A6 pricing to drop below that of the A5, although initially there may not be much (if any at all) cost savings. Note that Apple's 32nm A5r2 is very close in size to the A6, which made it a great test part for Samsung's 32nm process. Apple likely caught the bulk of its process issues on A5r2, making an aggressive ramp for A6 on 32nm much easier than it would have been previously. It's clear that the Apple SoC team benefitted from the practical experience of its members.

Putting the A6 in perspective, we have the usual table we throw in our CPU reviews:

CPU Specification Comparison
CPU Manufacturing Process Cores Transistor Count Die Size
Apple A6 32nm 2 ? 97mm2
Apple A5X 45nm 2 ? 163mm2
Apple A5r2 32nm 2 ? 71mm2
Apple A5 45nm 2 ? 122mm2
Intel Ivy Bridge HE-4 (GT2) 22nm 4 1.4B 160mm2
Intel Ivy Bridge HM-4 (GT1) 22nm 4 ? 133mm2
Intel Ivy Bridge H-2 (GT2) 22nm 2 ? 118mm2
Intel Ivy Bridge M-2 (GT1) 22nm 2 ? 94mm2
Intel Sandy Bridge 4C 32nm 4 995M 216mm2
Intel Sandy Bridge 2C (GT1) 32nm 2 504M 131mm2
Intel Sandy Bridge 2C (GT2) 32nm 2 624M 149mm2
NVIDIA Tegra 3 40nm 4+1 ? ~80mm2
NVIDIA Tegra 2 40nm 2 ? 49mm2

Although the A6 is significantly smaller than the mammoth A5X, it's still quite large by mobile SoC standards. At 97mm2 Apple's A6 is slightly larger than a dual-core Ivy Bridge with GT1 graphics. Granted that's not a very impressive part, but it's still a modern chip that Intel sells for over $100. I'm still not sure what the die size sweet spot is for a smartphone/tablet SoC, perhaps something around 120mm2? I just can't see the 200mm2 chips we love on the desktop being the right fit for ultra mobile.


A6 die photo courtesy UBM Tech Insights

Looking at the A6 die we clearly see the two CPU cores, three GPU cores and 2 x 32-bit LPDDR2 memory interfaces. The Chipworks photo shows the GPU cores a bit better:


Apple A6 die photo courtesy Chipworks

Chipworks was first to point out that Apple's custom CPU cores appeared to be largely laid out by hand vs. using automated tools. Not using automated layout for all parts of a CPU isn't unusual (Intel does it all the time), but it is unusual to see in an ARM based mobile SoC. Shortly after the iPhone 5's launch we confirmed that the A6 SoC featured Apple's first internally designed ARM CPU cores. As a recap there are two types of ARM licensees: architecture and processor. A processor license gives you the right to take an ARM designed CPU core and integrate it into your SoC. Apple licensed ARM's Cortex A9 design in the A5/A5X SoCs for example. An architecture license gives you the right to design your own core that implements an ARM instruction set. Marvell and Qualcomm are both examples of ARM architecture licensees.

For years it's been rumored that Apple has held an ARM architecture license. With the A6 we now have conclusive proof. The question is, what does Apple's first custom ARM CPU core look like? Based on Apple's performance claims we know it's more than a Cortex A9. But to find out what the architecture looks like at a high level we had to do a lot of digging.

 

Build Quality Issues, Scuffgate Decoding Swift
Comments Locked

276 Comments

View All Comments

  • Zink - Wednesday, October 17, 2012 - link

    That's would be light enough to float.
  • manders2600 - Wednesday, October 17, 2012 - link

    It would be really nice to see some of these benchmarks next to an Android device running Jellybean.

    From my personal experience with the Galaxy Nexus, all of the benchmarks run in this article improve dramatically (many by more than 50%) with that OS version.

    I'm really curious to see what a comparison between the performance of an S4 (Krait) and an A6 would be in that situation, since so much of the CPU tests are impacted by OS.
  • manders2600 - Wednesday, October 17, 2012 - link

    But great read, though!

    . . . sorry, forgot to include that.

    Tremendous research went into this, and it is well appreciated.
  • phillyry - Sunday, October 21, 2012 - link

    I agree.

    I mean it's good that you have the devices on their native OSes but showing them on their upgraded OSes would bee good too 'cause it would add another realistic point of comparison.
  • cjl - Wednesday, October 17, 2012 - link

    In the article, you state:

    "Which brings us to the next key detail with the anodization process: typically, the thickness of the anodization is half the thickness of the base aluminum. So if you had an aluminum plate that was 1mm thick, post-anodization, you would end up with a 1.5mm thick plate"

    You also talk about the pore density in anodizing, and claim that apple has a pore density higher than most.

    To put it quite simply, all of this is wrong.

    Anodizing creates a layer that is on the order of micrometers thick. How thick the coating is depends on the details of the anodizing process, not on the thickness of the base metal. Most decorative anodized coatings are a few micrometers thick, and as you discussed, it's really not that hard to scratch them. Thicker anodizing, sometimes known as hard anodizing, is possible, and it can be done to thicknesses of 25 micrometers (0.001") or greater - from what I can find, over 100 micrometers is possible. These thicker coatings provide pretty substantial scratch resistance, and significant increases in durability, but they require substantially more process control, and it is more difficult to get a consistent coating. Note that even the thickest of these coatings is around 0.006 inches (150 micrometers) or so, which is far, far less than a 2:1 ratio on the aluminum on which it is applied. Interestingly, this thickest possible coating is about what you speculate is the thickness on the iPhone 5, but given its propensity for scratching, I sincerely doubt this to be the case.

    Now for pores. The pore size on anodized aluminum is a few tens of nanometers. There is absolutely no way that you could visibly see this, or any improvement in this from one product to the next. This is 20 times smaller than the smallest wavelength of visible light. Quite simply, you can't possibly see this, and this won't be any different between Apple and any other manufacturer.

    That having been said, there are some slight differences in pore structure between coatings. They won't make a significant visible difference (if any at all), but they can make a difference in durability. Specifically, hard anodized coatings (as mentioned above) tend to have thicker walled pores relative to the pore diameter. This again helps increase the wear resistance of hard anodized parts.

    TL,DR: The iPhone probably has a really thin anodizing coat (<10 um). The pores are never visible on anodizing. Anodizing can be done, even on very thin aluminum, such that it would be incredibly scratch resistant.
  • Jaguar36 - Wednesday, October 17, 2012 - link

    +1 on this.

    Not sure where the Vivek got the 2:1 ratio for an anodization thickness, but its nonsense. If you have a 0.25" thick part you're not going to be getting a 0.125" thick anodization. Anodization is usually less than 0.001" thick, and has no relation to the base part thickness.
  • Cibafsa - Wednesday, October 17, 2012 - link

    Whilst Android based device manufacturers do not have to bear the majority of the SOC design/manufacture costs or the OS development costs, they do not share in the iAds/App Store type revenue Apple does.

    Surely it is Apple that can afford to cut prices to cost or even lower. Perhaps it is the Android manufacturers that have to worry about cheap high end phones.

    Will be interesting to see what price point the iPad mini comes in at.
  • steven75 - Wednesday, October 17, 2012 - link

    Most people following this industry are well aware by now that the App Store is run near break-even and iAds were not very successful.
  • Calista - Wednesday, October 17, 2012 - link

    A good and through review but I found it a bit too long-winded. An example would be the following example straight from the first page:
    'All previous iPhones have maintained the same 3.5-inch, 3:2 aspect ratio display. With the rest of the world quickly moving to much larger displays, and with 16:9 the clear aspect ratio of choice, when faced with the decision of modernizing the iPhone platform the choice was obvious.'

    It could have been shortened to:
    'iPhone 5 moves from the previously used 3.5", 3:2 aspect ration to a 4", 16:9 aspect ratio as common among smartphones of today. They kept roughly the same width while increasing the hight with xx mm. The resolution went from 960x640 to 1136x640."

    More information is contained in the rewritten part while at the same time being shorter. Don't forget that this is Anandtech and I assume every single one of your readers are familiar with both the size and resolution of previous iPhones as well as common aspect ratios used on phones.

    The same could be said about the design. I'm sure every single one of your readers have held and played with an iPhone 4/4s, and so when comparing to those two you guys could have kept a lot shorter.
  • phillyry - Sunday, October 21, 2012 - link

    Read better as originally posted than as you rewrote it.

Log in

Don't have an account? Sign up now