tag 标签: core

相关博文
  • 2024-12-30 14:26
    124 次阅读|
    0 个评论
    在半导体设计的复杂世界里,EDA(电子设计自动化,Electronic Design Automation)和 IP(知识产权,Intellectual Property)是两个极为重要的概念。它们虽然都服务于半导体设计流程,但在功能、性质和应用等方面存在显著差异。理解这些差异,对于深入了解半导体行业的运作至关重要。 EDA:半导体设计的强大工具集 EDA 是一系列软件工具的集合,旨在帮助工程师进行集成电路(IC)的设计、验证和制造。从最初的电路原理图设计,到复杂的芯片布局布线,再到最后的功能验证,EDA 贯穿了整个半导体设计流程。 EDA 工具的功能 设计输入 :工程师可以使用图形化界面或硬件描述语言(如 Verilog、VHDL)来描述电路的功能和结构。这些工具能够将设计转化为计算机可处理的格式,为后续的设计步骤奠定基础。 逻辑综合 :将高层次的设计描述(如行为级描述)转换为门级网表,即实际的逻辑电路结构。在这个过程中,EDA 工具会根据目标工艺库对设计进行优化,以提高性能、降低功耗和面积。 布局布线 :在芯片的物理层面上,将各个逻辑单元(如门电路、寄存器等)放置在合适的位置,并通过金属连线将它们连接起来,以实现电路的功能。布局布线工具需要考虑到信号完整性、电源分布和散热等多方面的因素,以确保芯片的性能和可靠性。 验证 :包括功能验证、时序验证和物理验证等多个环节。功能验证用于确保设计的电路能够按照预期的功能运行;时序验证则关注信号在不同路径上的传播延迟,以保证电路在时钟信号的驱动下能够正确工作;物理验证主要检查芯片的物理设计是否符合制造工艺的要求,如线宽、间距等。 EDA 的作用 EDA 工具极大地提高了半导体设计的效率和质量。通过自动化的设计流程和强大的验证功能,工程师可以在较短的时间内完成复杂芯片的设计,并减少设计错误的发生。同时,EDA 工具还支持不同设计团队之间的协作,使得大规模的芯片设计项目能够顺利进行。 IP:半导体设计的复用模块 IP 是指预先设计好的、具有特定功能的电路模块,这些模块可以被其他设计团队复用,从而加速芯片的设计过程。IP 模块可以是软核(如用硬件描述语言编写的功能模块)、硬核(已完成物理设计的模块)或固核(介于软核和硬核之间,具有一定的物理实现信息)。 IP 的类型 处理器 IP :如 ARM 架构的处理器核,被广泛应用于各种嵌入式系统和移动设备中。这些处理器 IP 具有成熟的架构和高性能的处理能力,设计团队可以直接使用它们,而无需从头开始设计处理器。 接口 IP :如 USB 接口、HDMI 接口等,用于实现芯片与外部设备之间的通信。这些接口 IP 遵循特定的标准协议,能够确保芯片与其他设备的兼容性。 数字信号处理(DSP)IP :用于对数字信号进行处理,如滤波、傅里叶变换等。在通信、音频和视频处理等领域,DSP IP 发挥着重要的作用。 IP 的优势 使用 IP 模块可以显著缩短芯片的设计周期,降低设计成本。由于 IP 模块已经经过了验证和测试,其可靠性也得到了保障。此外,通过复用成熟的 IP 模块,设计团队可以将更多的精力放在芯片的核心功能和差异化设计上,提高产品的竞争力。 EDA 与 IP 的区别 功能定位 EDA 是工具,是为了帮助工程师完成整个半导体设计流程而存在的。它提供了一系列的设计、验证和制造工具,是实现从设计理念到物理芯片的桥梁。而 IP 是设计模块,是半导体设计中的复用单元,为设计提供了现成的功能模块,加速设计过程。 表现形式 EDA 以软件工具的形式存在,工程师通过安装和使用这些软件来进行设计工作。而 IP 则以代码(软核)、物理版图(硬核)或两者结合(固核)的形式存在,是设计中的可复用资源。 应用方式 EDA 工具在整个设计流程中被广泛应用,从设计的最初阶段到最终的制造环节,都离不开 EDA 工具的支持。而 IP 则是在设计过程中根据需要进行选择和集成,将合适的 IP 模块整合到芯片设计中,以实现特定的功能。 开发与维护 EDA 工具的开发需要大量的软件开发和算法研究人员,他们不断更新和优化工具的功能,以适应不断发展的半导体工艺和设计需求。IP 的开发则需要专业的芯片设计团队,他们专注于特定功能模块的设计和验证,确保 IP 的性能和可靠性。在维护方面,EDA 工具的维护主要是针对软件的更新和技术支持,而 IP 的维护则包括对模块功能的改进和对新工艺的适配。 EDA 和 IP 在半导体设计领域中都扮演着不可或缺的角色。EDA 是实现设计的工具,为设计提供了流程和方法;IP 则是设计的复用资源,加速了设计的进程。了解它们的区别,有助于半导体行业的从业者更好地利用这两个关键要素,推动半导体技术的不断发展。
  • 热度 3
    2019-10-13 19:11
    9137 次阅读|
    1 个评论
    《手把手教你设计CPU——RISC-V处理器篇》-- CPU是怎样炼成的
    首先感谢社区提供图书试读活动,能够让我有机会申请到这本期待已久的书 《 手把手教你设计 CPU——RISC-V 处理器篇》 。 之所以期待已久是因为,本书作者是一线工程师出身,工程师写的书往往理论内容少一些,读起来不会很枯燥,另一方面更加结合实际的开发和应用,会有很多的经验总结和分享,能够让读者学以致用,应用到工作和学习的实际项目中。 # 作为一名芯片公司的软件工程师,我对各种架构CPU和生态以及计算机各个方面的基础理论也稍有研究。 这本书主要以设计一颗RISC -V 的 MCU 为例,详细介绍了CPU是怎样炼成的。书中描述了设计过程中的重点环节和模块,并在Github开源了相应芯片蜂鸟E203的源码以及相关文档,项目地址为 https://github.com/SI-RISCV/e200_opensource ,读者可以结合源码仔细阅读书中相应章节。 什么是RISC -V? 简单来说,RISC -V 是一种最近几年比较热门的新的CPU架构,和x 86 和arm一样,它符合基本的CPU体系结构模型能够实现计算和控制功能。所不同的是它并非诞生于商业公司,而是由教育机构和开源社区合作实现并通过开源基金会管理。它能够为开发者提供开源 / 免费的指令集和CPU参考设计,并且是非常高效和先进的设计。 为什么选择 RISC-V 架构? 书中前两章很好的回答了这个问题。想当年,CPU界群雄并起,争霸江湖。但最终x 86 凭借w intel 建立的强大生态联盟,占领了PC和服务器市场。而arm则是凭借优秀的低功耗设计和不错的运气在智能机兴起时期,迅速占领了市场并不断加强生态建设建立自己的护城河。 但是这两种架构的指令集都是归商业公司所有,想要使用相关架构的CPU甚至基于指令集实现CPU都是收费的,而且使用上也有很多限制。Berkeley的同志们就是困扰于没有可靠的免费指令集可用,遂决定重新定义新的架构并基于此架构设计芯片。 从书中概括几个RISC -V 架构的主要特点: 架构简洁 :相比于x 86 和arm , 后两者都经历了多则数十年的发展,不断优化 / 增强的同时还要保持向前兼容,这样不断的打补丁就导致架构变的越来越臃肿,虽然众多优秀的工程师投入巨大精力使得性能仍然非常好,但是从设计者的角度,越来越难去把握其中的细节,有大量的坑在等着你,这一点从x 86 或者arm为架构出的errata文档就可以看出。RISC -V 因为吸取了大量先进的设计理念和经验,具备后发优势,没有历史包袱,架构更加简洁清晰,用作者的话说就是短小精悍。感兴趣的读者可以从基金会官网 https://riscv.org/ 或者本书项目的GitHub主页下载阅读架构文档。 模块化的指令集 :相比于arm架构 A / R / M 三个高中低架构互不兼容, RISC-V 能够使得用户灵活地选择不同个的模块进行组合,满足各种应用需求。如嵌入式选择 RV32IC ,高性能可选择 RV32IMFDC 等 扩展指令集 :用户可以根据需要扩展自己的指令子集, RISC-V 预留了大量的指令编码空间用于用户自定义扩展。为了狙击RISC -V ,arm最近也宣布在部分CPU内核引入自定义指令功能。 CPU长啥样? 书中蜂鸟E203 SOC和C ore 原理图如下: CPU C ore中主要包含取指器 / 译码器(也叫控制器) / 计算执行单元 (ALU) 和寄存器组,流水线的实现就是对这几个模块的硬件多次实现并行执行。 书中 7-10 章讲解了指令执行过程中各个步骤的硬件如何设计和优化,包括取指 / 译码 / 执行 / 交付和写回。 上层软件经过编译链接生成对应机器的字节码,CPU从相应地址根据指令长度依次取指执行。一切看上去很自然也很轻松,但是硬件设计上需要考虑很多问题,比如如何快速取值,如何处理非对齐指令和分支指令等。指令执行过程中会碰到流水线冲突和分支如何预测等更多问题,如何设计可靠的CPU确实需要非常多的经验积累,参考本书可以少走很多弯路。 Co re 中其他硬件模块还包括存储器接口 / 中断控制器,和其他可选的如FPU ( 浮点运算模块 ) 和trace接口等,参见书中相关章节。 这样我们就有了一个可以进行运算的Core。对于SOC来说,我们还需要片内总线进行core和外设的连接,常用的总线协议包括 AHB APB 等,蜂鸟E203中使用自定义总线协议ICB进行Co re 和存储器等外设的互联 书中第三部分具体讲解了如何在FPGA上运行和验证这颗 蜂鸟E203 SOC , 有FPGA硬件开发板并且熟悉verilog的同学可以按照书中的介绍对该芯片的开源代码进行仿真测试和运行。 最后附上arm Cortex M4 架构图做为对比学习
  • 热度 13
    2014-10-21 18:21
    1505 次阅读|
    0 个评论
    Anyone knowledgeable of the specifications of telecom protocols will recognize that they are both detailed and complex. So it is surprising -- especially given the revelations of whistle blowers such as Edward Snowdon and the current cyber security fixation -- that the Optical Transport Network (OTN) does not inherently feature any encryption.   The OTN's evolution has seen the successful inclusion of Ethernet packets into the payload. Originally, the OTN was designed to transport SONET/SDH, but it has been adapted to work with the faster Ethernet standards.   There is growing interest among equipment vendors in the notion of adding encryption to provide privacy and tamper detection on OTN systems with minimal added latency. The growing use of networks for applications such as financial transactions is a key driver for this technology.     Encrypting an OTN system requires the equipment vendor to work closely with an intellectual property (IP) vendor for several reasons. First, the method of securely transmitting the encryption keys must be organized. Fortunately, unlike in many systems, the keys in OTN systems are updated fairly infrequently. This allows for pre-computation of some encryption parameters in software, rather than providing hardware to compute them on the fly, as would be necessary in a protocol such as MACsec or IPsec, in which keys can change for every packet. Another issue is to get an efficient, low-latency core to fit into the design. Nearly every system contains a programmable logic chip such as a field programmable gate array (FPGA) to handle a range of protocol, framing, control, and interfacing tasks. The encryption IP core can be included in the FPGA. Where sufficient spare resources exist, this can even be achieved without moving to a larger device.   Algotronix Ltd.'s recently released OTN encryption core offers an interesting solution. The UK vendor has carefully optimized the core to be compatible with the traffic characteristics of the OTN system, such as fixed packet length. As a result, the lookup table (LUT) usage of the duplex AES-GCM core for the OTN is half what would be necessary for a duplex AES-GCM implementation for encrypting and decrypting 10G Ethernet packets.   The core provides AES-GCM with 96-bit IV and a choice of 128-bit or 256-bit keys. This gives privacy as well as confirmation that the decrypted packet has not been altered, which is mandatory for many systems. Designers can use recent FPGA families supplied by all leading vendors and select from a number of implementation options. Another very useful option is the ability to drive the FPGA tools into using certain resource types for key blocks of the core. The AES system requires the creation of what are known as S-Boxes as a significant part of the total resource requirement. Enabling the design tools to favor logic or memory blocks for these elements can allow the design to fit into the available spare capacity and therefore to squeeze the encryption core into a tightly packed layout.   One special consideration for encryption IP relates to confidence that the security has not been compromised. A concern in any high-security design is to ensure that so-called Trojan Horse features have not been maliciously included. It is important, therefore, to select a reputable vendor whose source code can be carefully inspected. It greatly reduces the risk that anybody has contributed malicious code to, say, an open source project. Licensing source code, rather than just a netlist, gives users the option to analyze the design. It also reduces the burden and cost of a detailed analysis of all the security components in the system.   Verification is the number one headache in system design. AES with Galois/Counter Mode (AES-GCM) was standardized by the National Institute of Standards and Technology (NIST) with a number of different operating modes. The institute also provides a large number of tests with "known answer" patterns to be used in implementation validation. For validation, it is good to know that the core ships with a comprehensive test bench including a behavioral model of AES-GCM. Along with the Algotronix-supplied testbench code, the core can also be simulated in a self-checking configuration within the user design, where it checks its output against a behavioral model.   The introduction of an IP core optimized for OTN systems gives equipment manufacturers the opportunity to differentiate their products with cost-effective, low-latency security features.
  • 热度 17
    2012-12-8 10:28
    2066 次阅读|
    0 个评论
    主控 AT91SAM9X25   400M高速ARM926EJ核心; ◆ 单颗DDR2 SDRAM,128M ◆ 大容量板载电子盘,256M ◆ 优质2.54间距的插件,更低成本 ◆ 双路10M/100M以太网,板载PHY ◆ CPU内置7路RS232串口 ◆ 板载两路CAN 2.0B ◆ 板载IIS,IIC,SPI等外部接口 ◆ 支持SD卡接口,大容量存储; ◆ 高速USB 2.0 Device接口; ◆ 高速USB 2.0 Host接口; ◆ 核心板高集成度,可以直接应用,可根据客户定制主板; 尺寸55*55mm 如需要该核心板,请联系:QQ:64909646
  • 热度 16
    2012-10-15 20:11
    1656 次阅读|
    0 个评论
    The recent news that their licensees have shipped 2 billion IP cores is obviously a reason for rejoicing at Tensilica's world-wide command center. So, if you have had occasion to stroll past Tensilica's corporate headquarters and RD center in Santa Clara, California, recently, you may have wondered at the "For Lease" sign planted firmly in front of the building.   What? How can this be? What is going on? In these days of doom and gloom, it's common to see this sort of thing and assume a worse-case scenario. But fear not my braves, because there is nothing to fear but fear itself (as my dear old dad used to tell me). A little bird tells me that things are going so swimmingly well at Tensilica that they've been hiring furiously, with the result that the current building is bursting at the seams (I hear dire tales of people working out of conference rooms and crammed into closets). Thus, on 20 October 2012 (just a few days' time as I pen these words), we will be seeing a mass exodus from Tensilica's current building as the little scamps all move down the road into a brand-spanking new facility.   If only I had the time, on moving day I would take a lawn chair and some cold drinks and ensconce myself on the lawn outside the new building and cheer them on their way. Sad to relate, however, I am up to my armpits in alligators fighting fires without a paddle (I never metaphor I didn't like), so I will just have to wish them all the best from the comfort of the pleasure dome (my office).  
相关资源