Hello to you all! In this blog, we will focus on low power management in PCIe. PCIe Power management aims at reducing power consumption in PCIe devices by putting them to low power states when they are idle and bringing them back to full power state when required.

Why does it matter ?  Because PCIe devices in the market such as graphic cards, storage devices, Network Interface Cards can consume significant power when they are active. Power management allows them to scale down their power consumption during idle or periods of low activity.

Hey everyone! This blog will cover the following: -

1. System Overview
2. Use-case
3. What are Outbound and Inbound windows in PCIe and how do they work?
4. What is ATU and why is it important in PCIe?
5. How to configure the PCIe windows in LS1028 and iMX8QXP
6. Code walkthrough
7. Running the test case

I3C温度センサ：P3T1755をMCXマイコンで動作させるサンプルコードが，NXPアプリケーション・コード・ハブで公開されています．この記事では，このサンプルコードを動作させるための手順を紹介．
必要となる機材はMCXマイコンの評価基板：FRDM-MCXN947，またはFRDM-MCXA153．これらの評価基板上にはP3T1755を搭載しているので，そのままの状態でI3Cの動作を試せます．同サンプルコードではP3T1755の単体評価基板：P3T1755DP-ARDを接続しての動作評価も可能．複数のP3T1755を接続しての動的アドレス割り当てやIBI(In-band interrupt:インバンド割込)機能も試せます．

マイコン/プロセッサと周辺デバイス間の通信に使われるSPIバス．

あまりに当たり前に使われるこのシリアルバスですが，あえていま，その成り立ちについてまとめてみます．

マイコン/プロセッサと周辺デバイス間の通信に使われるI²Cバス．

あまりに当たり前に使われるこのシリアルバスですが，あえていま，その成り立ちについてまとめてみます．

最近耳にするようになった『I3Cバス』．
これはI²CやSPIの後継となるべく，MIPIによって規定された新世代のシリアルバス仕様です．I3CはI²Cと同じ2線式のバスですが，I²Cに比べ通信速度が速く，低消費電力．さらにこれまでは追加で必要となった割り込み信号もこの2本線で扱えるよう少線化にも役立つような仕様となっています．
またI²Cと下位互換性を持ち，同一バス上にこれまでのI²CターゲットとI3Cターゲットを混在させて使うこともできます．
NXPではI3C対応のマイコン/プロセッサやセンサ，ターゲットとなるセンサ・デバイスや，ハブ/マルチプレクサ/信号レベル変換器などの様々な製品がラインナップされています．

An interactive tutorial on how to create your own MATLAB Simulink temperature sensor application by applying the model-based design approach, how to configure and use the i.MXRT1060 EVK using NXP MCUXpresso, a thermistor module and the IMXRT Toolbox.

The Local Interconnect Network (LIN) was developed as a complementally bus standard to the Controller Area Network (CAN bus) to address the need for a cost-efficient network for lower performance devices within the vehicle.  While the CAN network was already in place within vehicles, its high bandwidth and advanced error detection capabilities were overkill (and thus, cost-prohibitive) for lower performance applications such as seat and window controllers.

CAN FD is an extension to the Classic CAN protocol that was developed to meet the needs of modern vehicles wherever-increasing numbers of embedded electronics are transmitting ever-increasing amounts of control and diagnostic data.  Because the original CAN specification has a maximum bandwidth limitation of 1 Mbps, data-dense activities like ECU flashing and advanced driver assistance systems (ADAS) ADAS applications were being impeded, forcing automotive manufacturers to add multiple CAN networks into newer vehicles.

Communication between these subsystems is critical to ensure the reliability and safety demanded in the automotive market.  The Controller Area Network (CAN bus) is a message-based communication network standard that allows ECUs to communicate within a vehicle without the use of dedicated analog signal wires.