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.


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.

  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
Comments Locked


View All Comments

  • spinportal - Thursday, May 28, 2015 - link

    What is interesting is comparing to the Intel NUCs for a media center hub (or HP Stream Mini) with Windows 10. The CPU power is close to the Intel Celeron 2957U, where a i5-5250U (NUC5i5YH/R) is 50% faster, but the Intel HD graphics is probably 20% slower. Both are fighting for the 4K home theater crowd, but Shield TV is cheaper (barebone NUC is 399 extra SDRAM & mSATA & remote/controller) and baked in 10' UI/UX and easier to maintain for the average user with support for DVR in the future and GRID gaming. Sure Win 10 will have a 10' UI and you can install whatever you want on it to customize to your own content, but higher price to entry and more time needed to tweak. The Intel Stick is cute at $150, but falls short in competition for the checklist of features. If sideloading is easy on the Shield TV, tweakers can rejoice and hope apps will scale properly. If people have an XB1 and enjoy the media apps / services and voice activation, then it's a hard sell. Gamestream is just icing, helping the portability of the Shield TV in a remote location (at home most games would have a big enough screen connected and avoid input lag). It's not a Roku or a Chromecast, so to get customers to make a premium purchase like this, targeting 4K video is the bait.
  • nathanddrews - Thursday, May 28, 2015 - link

    "This also means that the SHIELD Android TV will not be doing any HD audio bitstreaming"

    Stopped reading.
  • Sivar - Thursday, May 28, 2015 - link

    ``Consumers need to get their expectations right - the SHIELD Android TV needs consideration only if OTT streaming (4K Netflix, in particular) and gaming credentials are important.''

    The key feature I need is HEVC compatibility. I have many Blu-rays that I encode with FLAC audio, but with my FireTV, I am unable to use HEVC.

    Are you saying that the Shield Android-TV is a poor choice for my requirements?
  • ganeshts - Thursday, May 28, 2015 - link

    If you are savvy enough to encode your Blu-rays with HEVC, then I am sure you understand what I am trying to convey..

    The typical media library also includes TV programs that are interlaced MPEG-2 (for example). The SHIELD is currently not a good solution for such a case.

    I have outlined clearly what works and what doesn't. In your case, I would still suggest waiting for a proper HTPC with HDMI 2.0 / HEVC support unless HEVC-encoded Blu-ray rips are the only media files you plan to play in your setup.
  • TheJian - Friday, May 29, 2015 - link

    Being savvy enough to check a few boxes doesn't mean you know everything about formats. You can muddle through handbrake without doing much more than selecting a profile for your device. The person states they are wanting FLAC+HEVC yet you tell him wait for HTPC. HE was clear in what he needed, so you should just say yes it plays what you need, or no it doesn't instead of a flippant response :( He likely has other players for other formats already hence his main feature desired is what he inquired about.

    But still you're acting as if mpeg2 interlaced is all anyone wants and a reason to NOT buy it, when I'd suggest it's not many people (that can’t get that some other way until this unit CAN do it, like a dvd player or bluray player in your rack already) and most would want all the other stuff this thing can play NOT just bluray HEVC encoded stuff. IE, anything in mkv/mp4 with dolby etc in h264/x264 (which is most libraries of current content and mostly what people rip bluray to also as you even note in the review). This thing plays a LOT more than hevc. IF you're only going to use the NATIVE Android Tv player then it's somewhat limited, but you're not stuck with that and can choose a dozen or more others (paid or free). 3rd party stuff can easily be had to get around it all if not now then at some point most likely. IE you mention kodi can play mpeg2 without license in software. You also mention Deinterlacing might be added soon to Kodi. So your problem with the device here just a software fix away anyway (and only the interlaced part is a problem correct?)? There are many free apps that can deinterlace already on PC for conversion even if players that do it on android don’t exist…but wait for it…

    Just check googleplay store: BSplayer, MX player Pro, KMplayer, vlc, etc (not saying which does the job just noting a bunch):
    1080i mpeg 2 on mxplayer without transcoding. Appears this would solve your combo problem, and this is really old version of the software from 2013 post running on nexus 2013. I’m thinking your excuse for not buying is dead already. You can use de-interlacing option in MX player > settings > decoder. Considering you MENTIONED MX Player in your review, you can’t be this ignorant right or am I missing something? Unlike the OP who may NOT know about all this stuff, you definitely DO know about MX player yet seem to be unable to pass the chance to find some reason to KNOCK an nvidia product even when you know what I just showed fixes it. Typical Anandtech BIAS against Nvidia stuff (**cough AMD portal cough**) here or what?

    From your last sentence it almost seems as you're acting like HEVC encoded blurays is all it does, which is categorically false (even though that is what the guy said he wanted to play as a main feature).

    Worse you even state most people do the following (which it plays fine):
    "The SHIELD Android TV / Kodi combination has absolutely no trouble with the vanilla H.264 files that people usually rip their Blu-rays to."

    But no ignore that, it doesn't play mpeg2 interlaced stuff (yet, at least out of the box, but seems to with at least mxplayer as shown which you know about) so it sucks...LOL. OK...Whatever. With 100million-500million installs I think most know about this app (free with ads, $6 without) yet you avoid using it for testing. 2.8million reviews too...LOL. That has to be one of the MOST KNOWN apps on android as most use videos on mobile. How well it works on a TV who knows (10 foot interface? Not sure) but that isn't the point. Worst case you just use it for specific vids with issues. .ts files play fine on mx player also. It seems to have many multiples of the installs of kodi (or xbmc if you like). Kodi on the other hand is only available to the handful of people that can find it (not directly on googleplay so to speak).
    You can follow how to get to it above I guess if desired (from googleplay & not sideloaded). Maybe this will help it gain popularity ;)

    Instructions here too I guess.

    MX Player features (among other stuff):
    "Plays almost every movie files including .3gp .avi .divx .f4v .flv .mkv .mp4 .mpeg .mov .vob .wmv .webm .xvid and many more."

    Either I'm missing something here, or don't really get the complaints you're making nor your flippant response to the OP. Are you saying MX Player with deinterlacing checked won't work for mpeg2 as shown in the supplied youtube video? That guy is testing 1080i mpeg2 on it. I'm confused.
  • Adding-Color - Thursday, May 28, 2015 - link

    My ibothsion is that it will play hevc/h.265 content with hardware acceleration and flac should have no licensing issues and doesn't need hardware acceleration, software acceleration should very well be possible on such a beefy SOC. I don't know if there's yet a software avaible that combines both though.
  • Adding-Color - Thursday, May 28, 2015 - link

    My impression ...
  • Aegrum - Thursday, May 28, 2015 - link

    Perhaps I missed it, but to me the killer feature is streaming my steam library to my TV from my GTX 680 desktop. Why didn't you cover that? I couldn't care less about the android games. Being able to plop down on my couch and stream Witcher 3 from my PC is worth the price of admission, as it nullifies any desire for a steambox, if it works well.
  • jjj - Thursday, May 28, 2015 - link

    The 50$ Sream Link should do that in a few months. If it works well enough , getting this just for that feature is excessive.
  • Aegrum - Friday, May 29, 2015 - link

    Sadly that price doesn't include the Steam controller, which is likely to be at least $50. I'm also in need of a streaming device for the television, so while yes, a steam link + controller + chromecast would be ~$135, I think the extra capabilities of this device for $200 is a fair price. Plus it's 4K ready for once I get a 4K TV, and all on one HDMI input that I don't have to switch between. And plays more than just what I have in Steam, though unconfirmed whether Steam link will play non-steam titles or not.

    I like the Steam link, especially for the price, but for me I think the Shield console is a better fit.

Log in

Don't have an account? Sign up now