How to build Google Tensor G5 without Samsung

It’s no secret that the upcoming Google Tensor G5 inside Pixel 10 -Series Will be special – unlike all current pieces in the series, it will be built without Samsung’s help. We know that the chip will be built using TSMC’s 3NM class process node and has seen a good look at the core specifications, but not much more than that. Building an entire soc from scratch is a monumental task, which raises a question: How did Google, a relatively new company in the chip business, did that?

Thanks to a source in Google, Android Authority Have learned previously unknown Tensor G5 specifications, giving us a unique insight into how it was created.

The most important of a modern soc is obviously CPU and GPU. As we previously knew, Google has chosen to licenses Arm Cortex CPU cores, the same as those used in the Samsung-built Tensor tags. Unlike the previous pieces, however, Google has chosen a new Img dxt gpuReplace the arm Mali graphics parts used in tensor so far.

The previous tensor pieces had some Google-designed IP blocks that have been transferred to Tensor G5. The sound is treated on “AOC”-“always-calculation”, a specially built audio-DP that was first introduced in the original Tensor. The same goes for the “Emerald Hill” memory compressor.

Another noticeable thing that was transmitted was TPU. AI features are one of the most important reasons why Tensor exists initially, so it’s not surprising that Google brought it (or at least a developed version) to the Tensor G5. Similarly, “GXP” DSP, Google’s design was built around licensed Tensillica Xstena cores, brought to the G5 to help with specific workloads, including image processing.

This is where things begin to deviate from previous generations – former tensor pieces used a combination of two video codes: Google’s “Bigwave” of1 Codec Core and Samsung’s MFC (Multi format Codec) for the other formats. It will seem logical for Google to use something built into the house, maybe even for all the formats, but that is not the case. Instead, Google uses third -party IP to handle all formats. Specifically, the core used is Chips & Media Wave677DV, specified to handle up to 4K120 coding and decoding in AV1, VP9, ​​Hevc and H.264.

Google has also decided to licenses a third -party screen control and 2D GPU. The core used is Verisilicon’s DC9000. The former tensor pieces used full standard exynos DPUs for this purpose.

Of course, cameras are one of the pixel’s most important features, and Google has been working to build customized ISP hardware since the first tensor chip. The previous pieces had only a few customized Google-designed blocks to complement the usual Samsung isps, but it is now changing. The Tensor G5 will have a completely adapted ISP from front end to back-end parts of the pipeline.

Google has specially built a few basic parts for its pieces, such as a memory control, cache-level cache (GSLC) and clock/power modules. This is where Google’s commitment ends. The other parts of the chip, including many basic interfaces such as USB, PCIE, I3C, as well as the physical team controllers (PhYS) for interface such as DSI (Display), DisplayPort and Memory (LPDDR5X) are all licensed from different IP suppliers, mostly synopsys.

However, this is not an unusual practice – some of these exact cores were even used by Samsung! This is because building and verifying IP is a costly effort with the potential for things to go wrong. It simply does not make sense to build something that will only meet standard functions (as is the case with checkers for interfaces) when proven versions built by other companies can be licensed. Obviously, this limits flexibility, but in many cases it is an acceptable balance.

Although Google’s Tensor G5 says goodbye to Samsung, it shows why the partnership was the right choice in the first place. Even after releasing Tensor, Google still has to rely on third -party IP for most of the interfaces and features. Besides the fact that it will be built on the TSMC process, Tensor G5 will not be so different from the former tensor pieces. It still only has certain pieces and pieces of Google, while the rest is generic and built by someone else, with the less difference between who someone is.

The partnership with Samsung has allowed Google to test and develop its own IP road before it was ready to use its own foundation for the chip, and now it is finally mature enough to be on its own. I can’t wait to see how the future tensor pieces will develop with the basics that are now in place.

The Google Tensor G5 comes in the Pixel 10 series, and will be launched later this year.