NXP Tech Blog

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NXP Tech Blog

Takayoshi_Obara
NXP Employee
NXP Employee

NXPのパワーマネージメントIC(PMIC/SBC)を車載向けマイコン(S32シリーズ)に使用するメリットを4つ説明します。

Read more...

More
2 0 689
bradloane
NXP Employee
NXP Employee

NXP’s S32N55 device is the first in NXP’s new 5nm S32N family of vehicle super-integration processors for central compute applications. We will walk through the main modules and features shown in the S32N55 block diagram to explain them in more detail.

Read more...

More
2 0 435K
briancarlson
NXP Employee
NXP Employee

The S32N55 virtual prototype from Synopsys provides a comprehensive development platform for the S32N55 enabling software developers to debug and analyze their software efficiently, leading to faster turnaround and higher software quality. It includes the processing subsystem, the security subsystem, functional safety models, PCI Express communication interface, multi-port TSN Ethernet switch and CAN hub. 

Read more...

More
0 0 1,718
briancarlson
NXP Employee
NXP Employee

The S32N55 is the first member of the S32N family of vehicle super-integration processors.  It targets centralized, safe, real-time vehicle control in software-defined vehicles (SDVs).

 

Read more...

More
1 0 5,633
briancarlson
NXP Employee
NXP Employee

To support the transition to future vehicles where capabilities and features are defined with software code, rather than with hardware boxes, a new approach to design them is required. NXP's new S32N family targets the super-integration of vehicle functions for central compute applications in SDVs.

Read more...

More
0 0 2,107

The following has evaluated to null or missing: ==> defaults.manyEnable [in template "Language_CP_BulkTranslation_Angular" at line 168, column 56] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign displayConn = defaults.manyEn... [in template "Language_CP_BulkTranslation_Angular" at line 168, column 33] ----