Tegra X1: The Heart Of the SHIELD Android TV

Along with being NVIDIA’s first entry into the set top box/console market, the SHIELD Android TV also marks the launch of the latest generation Tegra SoC from NVIDIA, the Tegra X1. Formerly known by the codename Erista, NVIDIA first announced the Tegra X1 back at the company’s annual CES mobile presentation. In the long run NVIDIA has lofty plans for Tegra X1, using it to power their ambitious automotive plans – Drive CX visualization and Drive PX auto-pilot – but in the short run Tegra X1 is the successor to Tegra K1, and like K1 is meant to go into mobile devices like tablets and now set top boxes.

We’ve already covered Tegra X1 in quite some depth back at its announcement in January. But I wanted to recap the major features now that it’s finally shipping in a retail device, and in the process highlight what NVIDIA has capitalized on for the SHIELD Android TV.


Tegra X1 Mock-Up Die Shot

The Tegra X1 is something of a crash project for NVIDIA, as NVIDIA originally planned for the codename Parker SoC to follow Tegra K1. However with Parker delayed – I suspect due to the fact that it’s scheduled to use a next-generation FinFET process, which is only now coming online at TSMC – Tegra X1 came in on short notice to take its place. The significance of Tegra X1’s rapid development is that it has influenced NVIDIA’s selection of features, and what they can pull off on the TSMC 20nm process.

This is most obvious on the CPU side. NVIDIA of course develops their own ARMv8 CPU core, Denver. However the rapid development of Tegra X1 meant that NVIDIA was faced with the decision to either try to port a Denver design to 20nm – something that was never originally planned – or to go with an off-the-shelf ARM CPU design that was already synthesized on 20nm, and NVIDIA chose the latter. By pairing up a readily available CPU design with their own GPU design and supporting logic, NVIDIA was able to get Tegra X1 developed in time to roll out in 2015.

The end result is that for Tegra X1, NVIDIA has tapped ARM’s Cortex-A57 and Cortex-A53 CPU cores for their latest SoC. The use of standard ARM cores makes it a bit harder for NVIDIA to stand apart from the likes of Samsung and Qualcomm, both of which use A57/A53 as well, but as A57 is a very capable ARMv8 design it’s not a bad place to be in on the whole.

Overall NVIDIA is using a quad-A57 + quad-A53 design, similar to other high-end SoCs. The A57s have been clocked at 2.0GHz, on part with some of the other A57 designs we’ve seen, meanwhile we’ve been unable to get confirmation on the clockspeed of the A53 cores. Meanwhile rather than a somewhat standard big.LITTLE configuration as one might expect, NVIDIA continues to use their own unique system. This includes a custom interconnect rather than ARM’s CCI-400, and cluster migration rather than global task scheduling which exposes all eight cores to userspace applications. It’s important to note that NVIDIA’s solution is cache coherent, so this system won't suffer from the power/performance penalties that one might expect given experience with previous SoCs that use cluster migration.

Throwing in an extra bonus in NVIDIA’s favor of course is the fact that the SHIELD Android TV is a set top box and not a mobile device, meaning it has no power limitations an essentially unlimited thermal headroom. We’ll see how this plays out in benchmarking, but the biggest impact here is that NVIDIA won’t have to fight with TSMC’s 20nm process too much for SHIELD Android TV, and can keep their A57s consistently clocked high.

Meanwhile feeding Tegra X1’s CPU cores and GPU is a new 64-bit LPDDR4-3200 memory interface, which is attached to a sizable 3GB of RAM. LPDDR4 offers a good mix of bandwidth increases and power consumption reduction through a lower 1.1v operating voltage, and is quickly being adopted by the industry as a whole. Otherwise NVIDIA’s choice to stick to a 64-bit memory bus is expected, though it continues to be an interesting choice as it requires they fully exploit their memory bandwidth efficiency capabilities, as other SoCs geared towards tablets and larger device (e.g. Apple A8X) come with larger memory buses.

GPU

On the GPU side, Tegra X1 features one of NVIDIA’s Maxwell architecture GPUs (the X being for maXwell, apparently). As a GPU architecture Maxwell marks the start of something of a new direction for NVIDIA, as NVIDIA designed it in what they call a mobile-first fashion. By starting in mobile and scaling up to the desktop, NVIDIA is integrating deep power optimizations into their GPU architectures at an earlier stage, achieving better power efficiency than scaling down desktop GPUs. This has also led to the gap between desktop and SoC implements of NVIDIA’s latest and greatest GPUs shrinking, with Tegra X1 showing up on a bit more than a year after Maxwell first appeared in desktop GPUs.

In any case, with Maxwell already shipping in desktops, it has proven to be a powerful and formidable GPU, both on an absolute performance basis and on a power efficiency basis. Though it’s a bit of circular logic to say that NVIDIA is intending to exploit these same advantage in the SoC space as they have the desktop space – after all, Maxwell was designed for SoCs first – Maxwell’s capabilities are clearly established at this point. So from a marketing/branding perspective, NVIDIA is looking to capitalize on that for Tegra X1 and the SHIELD Android TV.

Overall the X1’s GPU is composed of 2 Maxwell SMMs inside a single GPC, for a total of 256 CUDA cores. On the resource backend, NVIDIA has gone from 4 ROPs on Tegra K1 to 16 on X1, which won’t lead to anything near a 4x performance increase, but it is very important for NVIDIA’s desires to be able to drive a 4K display at 60Hz. And while NVIDIA isn’t listing the clockspeeds for the SHIELD Android TV, we believe it to be at or close to 1GHz based on past statements and the device’s very high thermal threshold.

Meanwhile from a feature standpoint Maxwell is as modern a SoC GPU as you’re going to find. Derived from a desktop GPU, it features support for all modern Android APIs and then some. So not only does this include OpenGL ES 3.1 and the Android Extension Pack, but it supports full desktop OpenGL 4.5 as well. On paper it is also capable of supporting Khronos’s forthcoming low-level Vulkan API, though we’re still a bit early to be talking about Vulkan on mobile platforms.

Also introduced on the Maxwell architecture – and by extension Tegra X1 – is NVIDIA’s latest generation of color compression technology, which significantly reduces NVIDIA’s memory bandwidth needs for graphics workloads. NVIDIA’s memory bandwidth improvements are in turn going to be very important for Tegra X1 since they address one of the biggest performance bottlenecks facing SoC-class GPUs. In the case of memory bandwidth optimizations, memory bandwidth has long been a bottleneck at higher performance levels and resolutions, and while it’s a solvable problem, the general solution is to build a wider (96-bit or 128-bit) memory bus, which is very effective but also drives up the cost and complexity of the SoC and the supporting hardware. In this case NVIDIA is sticking to a 64-bit memory bus, so memory compression is very important for NVIDIA to help drive X1. This coupled with a generous increase in memory bandwidth from the move to LPDDR4 helps to ensure that X1’s more powerful GPU won’t immediately get starved at the memory stage.

The other major innovation here is support for what NVIDIA calls “double speed FP16”, otherwise known as packed FP16 support. By packing together two compatible low-precision FP16 operations, NVIDIA is able to double their FP16 throughput per CUDA core relative to the Tegra K1, which coupled with the overall increase in CUDA cores leads to a very significant improvement in potential FP16 performance. Though this feature is perhaps most strongly aimed at NVIDIA’s Drive platforms, Android itself and a good chunk of Android games still use a large number of FP16 operations in the name of power efficiency, so this further plays into X1’s capabilities, and helps NVIDIA stretch X1’s performance a bit further for gaming on the SHIELD Android TV.

Last but certainly not least however is Tegra X1’s media capabilities, which more than anything else are the heart and soul of the SHIELD Android TV. By being one of the newest SoCs on the block the Tegra X1 is also one of the most capable SoCs from a media standpoint, which is allowing NVIDIA to come out of the gate as the flagship Android TV device.

Chief among these is support for everything NVIDIA needs to drive 4K TVs. Tegra X1 and SHIELD Android TV support HDMI 2.0, allowing it to drive TVs up to 4Kp60, and with full quality 4:4:4 chroma subsampling. NVIDIA also supports the latest HDCP 2.2 standard, which going hand-in-hand with HDMI 2.0 is (unfortunately) required by 4K streaming services such as Netflix to protect their content, as they won’t stream 4K to devices lacking this level of DRM.

On the backend of things, Tegra X1 brings with it support for H.264, VP9, and H.265 (HEVC) decoding. The latter two are just now appearing in SoCs, and as higher efficiency codecs are going to be the codecs of choice for 4K streaming. Consequently then Tegra X1 is capable of decoding all of these codecs at up to 4K resolution at 60fps, ensuring that it can decode not just 24fps movie content, but 30fps and 60fps TV content as well. As one final benefit, NVIDIA is also supporting full hardware decoding of 10-bit (Main 10) H.265 video, which means that the Tegra X1 and SHIELD Android TV will be capable of handling higher quality, higher bit depth content, including forthcoming HDR video.

NVIDIA SHIELD SoC Comparison
  SHIELD Tablet (Tegra K1) SHIELD Android TV (Tegra X1)
CPU 4x Cortex A15r3 @ 2.2 GHz 4x Cortex A57 @ 2.0GHz
4X Cortex A53@ ?GHz
GPU Kepler, 1 SMX (192 CUDA Cores)
@ ~800MHz
Maxwell, 2 SMMs (256 CUDA Cores)
@ ~1000MHz?
ROPs 4 16
Memory 2 GB, LPDDR3-1866 3 GB, LPDDR4-3200
Memory Bus Width 64-bit 64-bit
FP16 Peak 365 GFLOPS 1024 GFLOPS
FP32 Peak 365 GFLOPS 512 GFLOPS
Manufacturing Process TSMC 28nm TSMC 20nm SoC

Taken in overall, the use of the Tegra X1 puts the SHIELD Android TV in a very interesting position. From a raw graphics standpoint the system is arguably overpowered for basic Android TV functionality. Even though this is a SoC-class Maxwell implementation, the basic Android TV UI does not heavily consume resources, a design decision mindful of what most other SoCs are capable of. But this also means that NVIDIA should have no trouble keeping the Android TV UI moving along at 60fps, and if they do struggle then it would certainly raise some questions given just how powerful Tegra X1’s GPU is.

Gaming on the other hand still needs all the GPU processing power it can get, and to that end NVIDIA is delivering quite a bit. NVIDIA still has to live with the fact that Tegra X1 isn’t close to the performance of the current-generation consoles, with SoCs having just recently surpassed the last-generation consoles, but by being the most powerful SoC in the Android TV space, it means NVIDIA can at least deliver an experience similar to (and likely a bit better than) the last-generation consoles, which is still a bit step up.

Otherwise from a media decode standpoint, Tegra X1 is the perfect fit for the device that will be the flagship Android TV box. By supporting all of the latest codecs and display standards, NVIDIA is in a good position going forward to work with the increasing number of 4K TVs and the various over-the-top media services that will be utilizing H.265 to drive their 4K streaming. The fact that NVIDIA is pushing media capabilities so hard for today’s launch is not a mistake, as it’s likely to be their most useful advantage early in the device’s lifetime.

Introduction System Performance
POST A COMMENT

168 Comments

View All Comments

  • testbug00 - Friday, May 29, 2015 - link

    Nintendo can design a competent OS. The fact their OS runs smoother than Android did for years on Hardware that Android would choke on isn't really a negative.

    I'm not joking either, the sad part. And, why would the hardware force them to? Why would they risk people being able to pirate all their games super easy?
    Reply
  • tipoo - Friday, May 29, 2015 - link

    The 3DS, sure, modern android would choke on that hardware. But the design of getting around is still pretty byzantine. Anywho. The Wii U though? With 2GB RAM, half reserved for the OS, and three PowerPC750 based processor cores at 1.2GHz, the thing is still terribly slow for something released so recently. Meanwhile Android is butter with four low power Cortex A7 cores and does ok on 1GB RAM total.

    Not saying they should or shouldn't. And I'm not sure it would make piracy easier - even going with Android, being open source they can add their old security. Not that the Wii or DS were very secure from piracy either.
    Reply
  • tipoo - Friday, May 29, 2015 - link

    And what I mean by the 3DS bit...I picked up a 2DS from Target Canada while they were liquidating, half off so I thought what the hell. Didn't have much chance to use it until now.

    Went into street pass, there was an update available. Ok, go for it. Hit ok, confirm ok, yes it's ok it will take a while. Loads for a minute, then tells me I need to do a system update first. Figure out how to do that, easy enough. Start system update, confirm system update, yes it's fucking ok it will take a while. System update done.

    Go back to streetpass plaza, start update. Hit ok, confirm ok, yes it's ok it will take a while. Connecting to online account. Cool. Takes a minute. Then tells me I don't have enough SD storage space. You couldn't check that first?! There's a message that tells me where to go to free storage. So, why can't there just be a button within the message that takes me there?

    It could be because every time you close software, there's a button to really close it, and then a confirmation dialogue. Ach, getting real tired of your shit, Nintendo. A few more seconds of wait after you hit the *real* close button, too, because...I dunno. Nintendo.

    Delete some crap. Go back to install the thing. Hit ok, confirm ok, yes it's ok it will take a while. Works this time. Go through the new Plaza to see what's new. Go through a bunch of dialogue with a talking rabbit just to see screenshots of each game. You can hold R, but it's still pretty slow.

    Did I mention slow? The byzantine software layout may not even bug me as much if the thing was fast, but this is *really* slow. It's old hardware, I get that, plus it was low end hardware even at launch, but that doesn't stop it from being aggravating. The eShop being the worst of it. Going back and forth through pages is painstaking.

    Some people have and probably will try to remind me that Nintendo is focused a lot on children. I honestly don't think even kids need all this padding though - this is the iPad generation, they'll get the hang of things in a jiffy, and don't need three confirmations from a talking dildo or whatever weird crap Nintendo wants to do every time they open or close software or after they've already said yes to a download.

    Even with more attractive games on it than smartphones have, I find myself almost reluctant to use it every time for the slowness and very pre-iPhone software.
    Reply
  • eanazag - Friday, May 29, 2015 - link

    Nintendo just needs to give up on the hardware aspect and just distribute software. I would even pay for oldies like Excite Bike on iOS/MS Store/Google Play. I think they can still do regular consoles, but I have been disappointed with them. Good peripherals is still a market they could sell for.

    If anything, just sell the old stuff on those other services a make a dollar.
    Reply
  • mkozakewich - Saturday, May 30, 2015 - link

    If I were them, I'd work with a vendor to design a Nintendo Phone. Like, imagine an LG phone with Nintendo branding, a thumbstick, and four buttons? Maybe shoulder buttons, too. Whatever they could fit. (They might be able to get away with shoving all the usual 3DS buttons on.) Reply
  • smorebuds - Tuesday, June 2, 2015 - link

    This is more what I was referring too. If Nintendo focused on releasing software (to the Android/iOS market where they'd make the biggest splash) then wouldn't a Nintendo set top box like this Shield make sense too? It would just be the Nintendo-branded and skinned Android box, maybe with some extra Nintendo-specific features thrown in. Reply
  • FMinus - Wednesday, June 3, 2015 - link

    Why would they do that, I'm still pretty happy with my WiiU and their hardware offers something that noone else does, or usually copies it in one way or another. Besides Nintendo is sitting on a lot of cash, possibly more as Microsoft and Sony game divisions together anyway, so there's no fear of them going away anytime soon.

    Aside of that, they are the only company making consoles relatively affordable and kid friendly. Just as an example The Xbox/Playstation UI are an abomination to navigate for a 6 to 10 year old. And most importantly, Nintendo is focusing on games, not being the center of your living room, I'd gladly strip both the Xbox One and Playstation 4 of all the useless features (to me) if they offered them for $250.
    Reply
  • stoicromance - Thursday, May 28, 2015 - link

    So am I to understand that you can load pretty much any Google Play app onto this? Can I just throw VLC and Plex onto the Shield? Reply
  • Ryan Smith - Thursday, May 28, 2015 - link

    Through the Play Store, an app needs to be flagged as supporting the 10ft Android TV UI in order to show up. Though you can sideload practically anything. Reply
  • ganeshts - Thursday, May 28, 2015 - link

    Plex already comes pre-bundled

    VLC doesn't work that well right now on the SHIELD
    Reply

Log in

Don't have an account? Sign up now