Cypress Perform

Home > Documentation > Technical Articles

CAN in 30 minutes or less

Last Updated: 12/05/2011

Since CAN was introduced in the 80’s, it has seen a tremendous evolution in terms of specifications and requirements. Its extended capabilities have led to its wide adoption across applications, from automotive, to industrial machine and factory automation. With this growth, complexity of implementation has also increased on two levels:
1. CAN controller design has gone from a basic controller to a full CAN controller and, in some cases, an extended full CAN controller.
2. CAN software stacks vary, from an automotive communication stack, to CANOpen, and DeviceNet.

Given that CAN is only a single component within the automotive system, developers need to be able to implement it with as few challenges as possible so they can focus on system-level functionality rather than struggle with peripheral configuration. This article will explore the CAN interface and discuss different ways of implementing, configuring, and tuning interfaces to facilitate simplified design. To read more, click the download link below, or visit .


これらの文献はあくまでもご参考のためのみに日本語翻訳されています。誤訳によるトラブルが発生した場合、Cypress Semiconductor Corp. 全ての子会社、関連会社、役員、従業員、販売代理店は一切の責任を負いかねます。 最新の英語版オリジナル文献を必ずご参照いただくことをお勧め致します。

Related Files

Spec No: None; Sunset Owner: OBS; Secondary Owner: JMY; Sunset Date: 06/15/20

Related Pages

Spec No: None; Sunset Owner: OBS; Secondary Owner: JMY; Sunset Date: 06/15/20