USB High Speed Inter-Chip (HSIC) IP: What is it? And why should I use it?
来源: https://www.synopsys.com/dw/dwtb.php?a=hsic_usb2_device
What is HSIC?
HSIC (High-Speed Inter-Chip) is an industry standard for USB chip-to-chip interconnect with a 2-signal (strobe, data) source synchronous serial interface using 240 MHz DDR signaling to provide only high-speed (480 Mbps data rate). No external cables or connectors and hot plug-n-play are supported. There is also no analog transceivers, and hence reduces the complexity, cost, power consumption, and manufacturing risk. Low power can be achieved with 1.2 V LVCMOS signaling levels instead of the 3.3 V signaling requirement. Both data and strobe are bi-directional utilizing NRZI encoding. In addition, HSIC interface is always operated at high speed, 480 Mbps. Hence, no high-speed chirp protocol is needed during enumeration. Finally, HSIC USB is fully compatible with existing USB software stacks and provides all data transfer needs through a single unified USB software stack. For more technical information regarding the requirements to implement a HSIC USB solution, please refer to the High-Speed Inter-Chip USB Electrical Specification, Version 1.0 (a supplement to the USB 2.0 specification.) which is now available online at http://www.usb.org/developers/docs/docs

Why HSIC?
- HSIC replaces I2C
- I2C isn’t fast enough and requires special drivers
- HSIC allows USB Software reuse
- PHY reuse/adaptation of existing PHY technologies
HSIC Device Using Synopsys USB 2.0 Device Controller and HSIC PHY
USB chip-to-chip interconnect can be achieved with the use of both Synopsys device controller and HSIC PHY. It eliminates USB cables and connector connection down to two wires for high speed chip-to-chip communication. It also allows low power high-speed data transfers (480 Mbps) using a source-synchronous serial interface. By eliminating the need of 3.3 V signaling and 5 V short protection logic, Synopsys HSIC PHY can offer approximately up to 50 percent lower power and 75 percent smaller area compared to traditional USB 2.0 PHYs.

USB 2.0 HSIC PHY
- HSIC USB version 1.0 compliance
- HSIC USB Features
- Supports 8/16-bit unidirectional parallel interfaces for HS mode of operation in accordance with the UTMI+ specification
- Implements data recovery from serial data on the HSIC connector
- Implements SYNC/End-of-Packet (EOP) generation and checking
- Implements bit stuffing and unstuffing, and bit-stuffing error detection
- Implements Non Return to Zero Invert (NRZI) encoding and decoding
- Implements bit serialization and deserialization
- Implements holding registers for staging transmit and receive data
- Implements logic to support suspend, sleep, resume, and remote wakeup operations
- General Features
- Occupies small area
- Implements low power dissipation while active, idle, or on standby
- Implements one parallel data interface and clock for high-speed HSIC data transfers
- Provides parameter override bits for optimal yield and interoperability
- Provides on-chip PLL to reduce clock noise and eliminate the need for an external clock generator
- Provides Built-in Self-Test (BIST) circuitry to confirm high-speed operation
- Provides extensive test interface
- Technical Specification
- Small area with approx. 0.18 sq. mm (macro + pads)
- Low power
- HS transmit ~27 mW (typical)
- HS receive ~18 mW (typical)
- Suspend and sleep modes ~4uA
- Supports 12/24/48 MHz clock
- Initial process - TSMC 65LP
- Compatability
- The HSIC PHY uses the same UTMI interface to communicate with Synopsys device controller. Since there is no well defined standard on the UTMI interface for HSIC and we have not tested the HSIC PHY with non-Synopsys device controllers yet, we do not guarantee that the UTMI interface of HSIC PHY would work well with that of non-Synopsys device controllers.
- Availability
- Please contact Synopsys if you are interested in this feature for your USB product.
USB 2.0 Device Controller with HSIC feature
- Configuration
- New device controller configuration option is available to enable HSIC support.
- HSIC logic is implemented through an `ifdef statement. The logic will additionally be controlled by a strap pin.
- Device controller needs to be configured to support unidirectional UTMI PHY interface.
- New device controller configuration option is available to enable HSIC support.
- PHY interface specific
- No new pin is required to interface to Synopsys HSIC PHY for HSIC purposes. Unidirectional UTMI PHY interface is used.
- When the device controller is interfacing to Synopsys HSIC PHY, both the device controller and the PHY are of the understanding not to go through the chirp enumeration steps, but rather go to high-speed idle directly.
- Application Interface/logic
- New strap input pin from Application to enable/disable HSIC support (if the core is already configured to support HSIC through coreConsultant/RapidScript)
- This new strap input pin will not be existed if the device controller is configured not to support HSIC.
- Hardware impact
- Device controller will bypass the Chirp enumeration stage in the chirp_gen_state state machine of udc20_speed_enum module if HSIC feature is supported.
- The bypassing of the chirp enumeration stage will only happen if the associated strap signal is also enabled. If the strap signal is not yet enabled, the core will go through the normal chirp handshake mechanism to support non-HSIC PHY.
- Firmware impact
- No significant change is needed. Supporting high speed falling back to full speed mode is no longer needed when attaching to a HSIC USB host during enumeration because HSIC chip-to-chip interconnect supports high-speed operation only. Hence, a high-speed only device driver is needed.
- Compatability
- The device controller uses the same UTMI interface to communicate with Synopsys HSIC PHY. Since there is no well defined standard on the UTMI interface for HSIC and we have not tested the device controller with non-Synopsys HSIC PHYs yet, we do not guarantee that the UTMI interface of device controller would work well with that of non-Synopsys HSIC PHYs.
- Availability
- Please contact Synopsys if you are interested in this feature for your USB product.
USB High Speed Inter-Chip (HSIC) IP: What is it? And why should I use it?的更多相关文章
- Linux usb 1. 总线简介
文章目录 1. USB 发展历史 1.1 USB 1.0/2.0 1.2 USB 3.0 1.3 速度识别 1.4 OTG 1.5 phy 总线 1.6 传输编码方式 2. 总线拓扑 2.1 Devi ...
- Android 不通过USB数据线调试的方法
在开发Android应用时,通常情况下是通过USB数据线连接设备和计算机,但对于一些需要使用USB设备的应用,这种方法就碰到了麻烦,手机的USB接口已经和外接的USB设备连接,无法再连数据线,此时可以 ...
- USB眼图
/********************************************************************** * USB眼图 * 说明: * 对于USB眼图,并不是很 ...
- USB的挂起和唤醒(Suspend and Resume)【转】
转自:http://m.blog.csdn.net/blog/luckywang1103/25244091 USB协议的第9章讲到USB可见设备状态[Universal Serial Bus Spec ...
- PHP简单爬虫 爬取免费代理ip 一万条
目标站:http://www.xicidaili.com/ 代码: <?php require 'lib/phpQuery.php'; require 'lib/QueryList.php'; ...
- USB各种模式 解释
1.MTP: 通过MTP这种技术,可以把音乐传到手机里.有了U盘功能为什么还要多此一举呢?因为版权问题,MTP可以把权限文件从电脑上导过去:如果只使用手机的U盘功能,把歌的文件拷过去之后,没有权限文件 ...
- USB详解
USB作为一种串行接口,应用日益广泛.如同每个工程设计人员必须掌握I2C,RS232这些接口一样,我们也必须掌握USB.但是USB的接口协议实在有点费解,Linux UCHI驱动作者之一Alan St ...
- 技巧.【转】在虚拟机Vmware中使用HID设备(如USB免驱键盘)
ZC:我的环境:Win7x64.VMware10 ZC:我的处理: ZC: (1).usb.generic.allowHID = "TRUE" (本来就有,将它的位置提前) ZC: ...
- STM32 USB复合设备编写
目的 完成一个CDC + MSC的复合USB设备 可以方便在CDC,MSC,复合设备三者间切换 可移植性强 预备知识 cube中USB只有两个入口. main函数中的MX_USB_DEVICE_Ini ...
随机推荐
- 「6月雅礼集训 2017 Day2」B
[题目大意] 求n*n的棋盘,每行每列都有2个黑格子的方案数. n<=10^7 [题解] zzq的做法好神奇啊 行列建点,二分图 左边有i个点,右边有j个点的方案数 f[i,j] 左边有i个点, ...
- 01-modal
Demo示例程序源代码
源代码下载链接:01-modal.zip37.8 KB // MJAppDelegate.h // // MJAppDelegate.h // 01-modal // // Created by ...
- [转]在树莓派上搭建LAMP服务
之前介绍过树莓派上LNMP环境的搭建方法,本文将详细介绍如何在树莓派上配置LAMP服务. 为LAMP,是最流行的服务器配置之一,LAMP的含义是: Linux - 操作系统 Apache - 网络服务 ...
- Codeforces Round #475 Div. 2 A B C D
A - Splits 题意 将一个正整数拆分成若干个正整数的和,从大到小排下来,与第一个数字相同的数字的个数为这个拆分的权重. 问\(n\)的所有拆分的不同权重可能个数. 思路 全拆成1,然后每次将2 ...
- 上传代码到github上
初始化 git init 添加远程仓库 git remote add origin[仓库名] 仓库地址 添加文件 git add . 本地提交 git commit -m 'message' 拉去远程 ...
- python学习笔记 可变参数关键字参数**kw相关学习
在Python中可以定义可变参数,顾名思义,可变参数就是传入参数是可变的.可以是任意个,以一个简单的数学编程为例,计算 sum = a * a + b * b + .....z * z 函数定义可以如 ...
- C# WinForm窗体界面设置
设置方法: 一:Form对象 属性: 设计中的Name:窗体类的类名AcceptButton:窗口的确定按钮CancelButton:窗口按ESC的取消按钮 1.外观 Backcolor:背景颜色Fo ...
- django定义模型类
模型类被定义在应用文件夹下的model.py中 模型类必须继承Django的models.Model类 属性名不能用连续的两条下划线__ 主键:primary key,简写 pk 不需要主动定义,dj ...
- Java处理文件BOM头的方式推荐
背景: java普通的文件读取方式对于bom是无法正常识别的. 使用普通的InputStreamReader,如果采用的编码正确,那么可以获得正确的字符,但bom仍然附带在结果中,很容易导致数据处理出 ...
- Android 网络url设置View背景图
imgstr为url网络图片地址,topllay是要设置背景的控件: 方法1.Android Glide设置View背景图 Glide.with(this).load(imgStr).asBitmap ...