A System on a Chip (SoC) is exactly what the name implies, an entire system integrated on a single piece of silicon. This chip or integrated circuit (IC) contains many components of a computer that are designed to work together to achieve a common goal. The first part of the term, "system", indicates that it is a complex electronic component, while the last part, "chip", indicates that all the components of this system are crammed onto a single IC. Depending on the type of system that is shrunk to the size of a chip, it can perform a variety of functions, including artificial intelligence, signal processing, wireless communications, and more.

There is no simple answer to this question, which reflects the nature of SoC design itself, which is that it is a complex, multi-dimensional topic with many variables to consider. As technology advances, the difficulty of designing SoCs increases. In this blog, I will introduce some key ideas that I think are useful in most, if not all, SoC designs, and they will enable you to successfully understand the design and implementation process of your own SoC.

1. Plan

Before we dive in, I'll add one thing – specifications and schedules are likely to change over time. This is not a bad thing, but it needs to be accepted, understood, and allowed for.

With this in mind, a detailed and well-written specification is key at the start of any SoC design. You can have a game-changing idea, but if no one understands what it does and how it works, then it's hard to implement that idea in silicon. Having a detailed specification allows those who read it to understand exactly what the SoC does. The specification will likely evolve as the idea goes through different stages of design. Not only can you go deeper, but you can also improve the description of the module as you learn how the system works in practice.

Specifications should also be well-written. In short, if the engineer doesn't clearly understand what the module does when designing it from the specification, then the module will most likely not behave as expected. Having someone who didn't write the specification peer review the specification can be a very useful tool to address any issues the author may have missed.

A successful SoC design should also include a schedule. Having a schedule that documents the expected time for each part of the project is a valuable tool for making more informed decisions. A key part of a schedule, and one that can be overlooked, is flexibility. This flexibility is about leaving time in the schedule so that errors can be addressed and improvements can be made if the implementation is found to be deficient. This flexibility will allow for better management of risk and a more accurate timeline for the project. It also allows the various phases to be rearranged and sometimes run in parallel to achieve the desired timeframe.

2. Design Process

To say that the success of an SoC depends heavily on the design process would be an understatement as this is where the groundwork of the system is done.

Many books have been written about team structure and dynamics but I would just like to focus on some of the simpler points – having a team with the right skills and communication within the team. Now these may seem obvious but they are so important that they should be mentioned anyway.

The design team is more than just front-end design, it also includes verification, DfT, physical design and software. All of these parts need to function correctly and work together for the SoC to be durable and well-structured. Having a diverse range of skills within a team of experienced and capable engineers is important. Likewise, taking a design from specification to the next stage at the foundry is no easy task so the need for a tightly integrated cross-flow structure remains critical.

It is also important to ensure that each team can communicate with each other effectively. Changes may need to be made to a block due to revelations from the physical design team. Effective communication is important here as it means that changes can be explored, designed, verified and implemented in the shortest possible time.

3. Software

Last, but by no means least, is the role that software design must play in SoC design. This is an often overlooked part of the design process, but it is a critical part of the SoC and can make or break a design.

Let's start with the boot ROM. The boot ROM is a small section of memory that contains the code that the CPU needs at boot time. This code will initialize all of the buses, memory, and peripherals that the SoC needs to boot properly. This must be determined early on as it is critical to the design. It can be used to understand what the initial state of the system should be, which gives us a solid foundation.

Software security is another important topic to consider when building an SoC. I won't go into the specifics of software security here, except to say that software security future-proofs the system, which makes for a successful SoC. The software we load into memory can change from customer to customer, so having a way to protect the device from intrusions while still allowing official software changes and upgrades is an excellent way to make your SoC a viable option for future customers and extend the life of your product.

There is no easy answer to this question, which reflects the nature of SoC design itself, which is a complex, multi-dimensional topic with many variables to consider. Furthermore, as technology advances, the design of SoCs becomes increasingly difficult, and the answer to this question becomes increasingly difficult.

A detailed discussion of all aspects of SoC design and the technologies we can use to create SoCs would require several books. However, I will introduce some key ideas that I believe are useful in most, if not all, SoC designs, and will help you successfully understand the design and implementation process of your own SoCs.

So, while there is no easy answer to this question, I believe the ideas presented in this article will apply to most, if not all, SoC designs. Ideas such as planning and design flow are examples of this; having a firm grasp of these ideas will make your project run as smoothly as possible. Additionally, considering the software used on the SoC gives you a solid, secure foundation to develop your implementation. From these ideas, I hope you will gain new inspiration to design a successful SoC.

Source: Content compiled from design-reuse

View more at EASELINK