XRDC in s32k344 running in lockstep mode

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

XRDC in s32k344 running in lockstep mode

ソリューションへジャンプ
393件の閲覧回数
FabioG
Contributor III

HI There

in XRDC module in a s32k344 running in lockstep , I read in manual that  master core could be CM7 or AHBP or AXI. So i am convinced that a s32k344 in lockstep mode is to referring to a AHBP core master access, is it true?

in RTD4.0.0 in   Rm RTD module ,the  core types are the following:

typedef enum
{
XRDC_CORE_M7_0 = 0x00U,
XRDC_CORE_HSE = 0x03U,
XRDC_CORE_M7_1 = 0x04U
} Xrdc_Ip_MasterCoreType;

It seams that lockstep configuration is not suited for these RTD ...?

What is the situation about XRDC in lockstep mode for s32k344 ?

best regards,

Fabio

 

0 件の賞賛
返信
1 解決策
367件の閲覧回数
VaneB
NXP TechSupport
NXP TechSupport

Hi @FabioG 

A small explanation of how Lockstep Core works is that two identical processors are initialized to the same state, and they receive the same inputs (code, bus operations, and asynchronous events), so during normal operation, the two processors operate in parallel, executing the same set of instructions simultaneously. The key feature of lockstep is that both cores execute the same instructions and compare their results at every step to ensure they match. If a discrepancy is detected, it indicates a potential error or fault in one of the cores, triggering a fault-handling mechanism.

Because of this behavior, in lockstep, there is only a reference to M7_0 and M7_1 would be N/A. 

 

B.R.

VaneB

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
368件の閲覧回数
VaneB
NXP TechSupport
NXP TechSupport

Hi @FabioG 

A small explanation of how Lockstep Core works is that two identical processors are initialized to the same state, and they receive the same inputs (code, bus operations, and asynchronous events), so during normal operation, the two processors operate in parallel, executing the same set of instructions simultaneously. The key feature of lockstep is that both cores execute the same instructions and compare their results at every step to ensure they match. If a discrepancy is detected, it indicates a potential error or fault in one of the cores, triggering a fault-handling mechanism.

Because of this behavior, in lockstep, there is only a reference to M7_0 and M7_1 would be N/A. 

 

B.R.

VaneB

0 件の賞賛
返信
303件の閲覧回数
FabioG
Contributor III

Hi There,

Referring Figure8 Block Diagram page 24 Reference manual:

FabioG_0-1712833197713.png

 

It seems that CM7_1 accesses to bus via MDAC4, when XRDC is enabled. So in Lockstep mode i have to manage only MDAC0 (CM7_0)?

Regards

Fabio

0 件の賞賛
返信