In system development using microcontrollers and processors, it's necessary to decide "which communication method to use and how to connect things" between ICs, components, and circuit boards. Functionality, stability, debuggability, and future expandability are all crucial considerations.
Interface technologies are diversifying and becoming more sophisticated depending on the application, ranging from IC-to-IC communication such as I²C/I3C/SPI to fieldbuses essential for automotive and industrial applications like CAN, as well as voltage level conversion and USB Type-C.
This page provides information about NXP's interface-related technologies and products.
"Understand the basics → Put it into practice → Interpret its behavior"
This is how I systematically organize Japanese technical articles.
This resource is helpful not only for those learning about communications for the first time, but also for engineers facing design and debugging challenges such as "Why isn't it working?" or "Is this waveform correct?". Please use the categories that interest you according to your purpose.
| the purpose | category |
| I want to understand how serial communication works. | Serial communication: I²C / I3C / SPI (board-to-board and IC-to-IC communication) |
|
I want to learn about CAN communication. |
CAN (Automotive and Industrial Communication) |
| We want to manage bus traffic by expanding the bus network, installing switches, and converting voltages. | Voltage conversion and signal control (bus traffic management) |
| I'm looking for peripheral ICs such as RTCs, temperature sensors, GPIO expanders, and LED/LCD drivers. | Peripheral devices (I²C / I3C / SPI connection ICs) |
| I would like to consider a USB interface. | USB-related products (USB Type-C, etc.) |
■Basic and explanatory section
■Practical Section
■Design and debugging
■Basic and explanatory section
■Practical Section
(One microcontroller board is sufficient)
(Requires 2 microcontroller boards)
Voltage Level Converter (Level Shifter) [General Purpose, I²C, SPI, I3C Compatible]
■Basic and explanatory section
■Practical Section
GPIO Expander [I²C, SPI bus compatible]
LED driver [I²C, SPI bus compatible]
LCD driver [I²C, SPI bus compatible]
Real-time clock (RTC) [I²C, SPI bus compatible]
Temperature sensor [I²C, I3C bus compatible]
Serial protocol bridge
[I²C→UART, SPI→UART, SPI→I²C, I²C→SPI, UART→I²C]
Interface products include Arduino ® shield solution boards that allow for easy evaluation with various microcontroller boards. Ready-to-use sample code is also available for these boards, allowing you to easily examine the characteristics of each product. Please refer to this document for the availability of sample code.
スクリーンショット 2026-02-09 13.04.40.png
If you have any requests or suggestions for improvements regarding content related to the interface, please feel free to contact us using the information below.
NXP Japan Technical Blog (Japanese) Content Request/Improvement Survey – Fill out the form
=========================
We are currently unable to respond to comments in the " Comment " section of this post .
We apologize for the inconvenience, but when making inquiries, please refer to " How to contact NXP with technical questions ( Japanese blog ) " .
(If you are already an NXP distributor or have a relationship with NXP , you may contact the person in charge directly. )
This page summarizes NXP's interface products.
Interface technologies are diversifying and becoming more sophisticated depending on the application, ranging from inter-IC communication such as I²C/I3C/SPI to fieldbuses essential for automotive and industrial applications like CAN, as well as voltage level conversion and USB Type-C.
This page provides information about NXP's interface-related technologies and products.
"Understand the basics → Put it into practice → Interpret its behavior"
This is how I systematically organize Japanese technical articles.
This resource is helpful not only for those learning about communications for the first time, but also for engineers facing design and debugging challenges such as "Why isn't it working?" or "Is this waveform correct?". Please use the categories that interest you according to your purpose.