manualshive.com logo in svg

ST SPC582B Series, Примечание к применению, Страница: 20 / 35

Поделиться
Скачать
ST SPC582B Series Скачать руководство пользователя страница 20

3.14.3

Frequency out of range (fault #53)

Using the IRCOSC frequency as monitor references, the CMU_1 monitors the clock frequency used by Core_2
and XBAR, the CMU_2 monitors the clock frequency used by HPBM, the CMU_3 monitors the clock frequency
used by the PBRIDGE, the CMU_11 monitors the clock frequency used by the FBRIDGE and the CMU_14
monitors the clock frequency used by the PFBRIDGE. If one of the monitored frequencies is above or below
the relevant monitoring thresholds, the relevant CMU detects this fault and forwards it to the FCCU. The
FCCU receives the signal in OR from these CMU modules. The user can inject this fault by a SW procedure
that sets a misconfigured value for one of the monitoring thresholds, for example, the user can set the
CMU_x_HFREFR[HFREF] field (with x = 1, 2, 3, 11, 14) to a value lower than the correct one. The FCCU
error reaction path is verified if the FCCU_RF_S1[RFS21] and the CMU_x_ISR[FHHI] status bits (with x = 1, 2,
3, 11, 14) are set. The user must clear CMU_x_ISR[FHHI] status bit (with x = 1, 2, 3, 11, 14) before clearing the
relevant FCCU_RF_S1[RFS21] bit.

3.14.4

Frequency out of range (fault #54)

Using the IRCOSC frequency as monitor references, the CMU_6 monitors the clock frequency used by the
SARADCs and the CMU_12 monitors the clock frequency used by the eMIOS. If one of the monitored frequencies
is above or below the relevant monitoring thresholds, the relevant CMU detects this fault and forwards it to the
FCCU. The FCCU receives the signal in OR from these CMU modules.The user can inject this fault by a SW
procedure that sets a misconfigured value for one of the monitoring thresholds, for example, the user can set the
CMU_y_HFREFR[HFREF] field (with y = 6, 12) to a value lower than the correct one. The FCCU error reaction
path is verified if the FCCU_RF_S1[RFS22] and the CMU_y_ISR[FHHI] status bits (with y = 6, 12) are set. The
user must clear CMU_y_ISR[FHHI] status bit (with y = 6, 12) before clearing the relevant FCCU_RF_S1[RFS22]
bit.

3.15

XBIC fault

The XBIC verifies the integrity of each XBAR transfer. The XBAR transfer attribute information for all master and
slave ports is routed to the XBIC that verifies the coherence between input and output signals of the XBAR. For
further details on the XBIC, refer to SPC582Bx microcontroller reference manual 

RM0403

.

Figure 16. 

XBIC fault

  RGM

Error out

Reset request

reset

XBIC

FCCU

INTC

Interrupt request

Interrupt

Fault #56

XBAR_1

3.15.1

XBIC error detected (fault #56)

In case of corrupted transaction through the XBAR, the XBIC detects this event and forwards it to the FCCU.
The user can inject this fault by a SW procedure that uses the XBIC error injection feature through the XBIC_EIR
register. The user can select the system RAM as target (XBIC_1_EIR[SLV] = 2) and the Core_2 as master
(XBIC_1_EIR[MST] = 2), can set the syndrome (for example, setting XBIC_1_EIR[SYN] = 0x80, the bit 7
is modified to inject the fault), can enable the fault injection (XBIC_1_EIR[EIE] = 1) and can access to the
system RAM by the Core_2. The FCCU error reaction path is verified if the FCCU_RF_S1[RFS24] status bit
is set after the system RAM access. The user must clear the XBIC_EIR register before clearing the relevant
FCCU_RF_S1[RFS24] bit.

AN5752

XBIC fault

AN5752

 - 

Rev 1

page 20/35

Содержание SPC582B Series

Страница 1: ...utomotive MCUs Before reading this document the reader should have a clear understanding about the usage of FCCU For further details on this module refer to Fault Collection and Control Unit FCCU chap...

Страница 2: ...whole error reaction path are prone to latent failures the safety concept requires the execution of a software test to verify the integrity of the error reaction The user shall run this software test...

Страница 3: ...8 MEMU Flash ECC uncorrectable error Testable 29 MEMU Flash ECC overflow error Testable 30 IMA IMA activation Testable 32 PLATFORM SMPU SMPU XBAR 1 monitor incorrectly refuses an access Not testable 3...

Страница 4: ...CMU_1 CMU_2 CMU_3 CMU_11 CMU_14 5 FHH or FLL event from CMU_6 CMU_12 Before the safety application starts the user shall configure a proper reaction for each FCCU failure input source See FCCU regist...

Страница 5: ...SET CLEAR Mon 2 Fault Mon 3 Fault FCCU_RF_Sn register Mon 2 Register FSM The FCCU can trigger a fault event directly in the monitor even if no real failure is occurred through the fake fault interface...

Страница 6: ...a fault as HW recoverable fault that is the fault status within the FCCU remains asserted until the monitor keeps the fault indication asserted As soon as the monitor clears the fault indication it al...

Страница 7: ...temperature detector detects if the temperature exceeds the defined thresholds and the PMC_DIG forwards this fault to the FCCU There are three thresholds TS0 TS1 and TS2 Temperature detector threshold...

Страница 8: ...the Flash memory and pushes it to the various clients inside the microcontroller Note System configuration is mainly saved as DCF records that are located either in the test or UTest sectors of the Fl...

Страница 9: ...that is configured as recoverable fault the STCU forwards this fault to the FCCU Note The user shall configure the STCU to trigger either a recoverable or an unrecoverable fault if the BIST fails This...

Страница 10: ...a dedicated glue logic forwards this fault to the FCCU The two error signals are put in OR before arriving at the FCCU failure input 9 The user can inject this fault by the FCCU fake fault interface...

Страница 11: ...aults RGM Error out Reset request reset EDC after ECC FCCU INTC Interrupt request Interrupt Fault 15 Set Clear TCD RAM Fault 48 Fault 10 Fault 14 3 5 1 DMA_1 gasket monitor fault 10 In case of hardwar...

Страница 12: ...ions For further details on Flash and PFLASHC refer to the device SPC582Bx reference manual RM0403 Figure 9 Flash PFLASHC faults RGM Error out Reset request reset Memory Interface FCCU INTC Interrupt...

Страница 13: ...user test FLASH_0_UT0 UTE 0x1 6 Disabling the customer programmable EDC after ECC detection FLASH_0_UT0 CPE 0x0 7 Disabling the user test FLASH_0_UT0 UTE 0x0 8 Clear the relevant FLASH error flag FLAS...

Страница 14: ...such as software getting trapped in a loop or if a bus transaction fails to terminate When enabled the SWT requires periodic execution of a watchdog servicing operation The servicing operation resets...

Страница 15: ...relevant FCCU_RF_S0 RFS21 bit Alternatively the user can use the IMA to inject a correctable error in the system RAM location and cause the detection of this correctable error accessing to this syste...

Страница 16: ...on path is verified if the FCCU_RF_S0 RFS26 status bit is set The user must clear the relevant bit MEMU_DEBUG FR_PR_CEO or MEMU_DEBUG FR_PR_UCO or MEMU_DEBUG FR_PR_EBO before clearing the relevant FCC...

Страница 17: ...relevant FCCU_RF_S0 RFS30 bit 3 11 SMPU faults The SMPU provides hardware access control for system bus memory references The SMPU concurrently monitors and evaluates system bus transactions using pr...

Страница 18: ...ne check condition the Core_2 forwards this fault to the FCCU The user can inject this fault by a SW procedure that accesses to a not existing address The machine check interrupt IVOR1 must be handled...

Страница 19: ...CMU faults RGM Error out Reset request reset CMU_0 Fault 51 FCCU INTC Interrupt request Interrupt CMU_14 CMU_2 CMU_11 CMU_3 CMU_1 CMU_12 CMU_6 Fault 53 Fault 54 Fault 52 3 14 1 CMU_0 error fault 51 Th...

Страница 20: ...er can inject this fault by a SW procedure that sets a misconfigured value for one of the monitoring thresholds for example the user can set the CMU_y_HFREFR HFREF field with y 6 12 to a value lower t...

Страница 21: ...error for example a write error in the RAM controller resulting in corrupted RAM access the PRAM controller detects this fault and it forwards it to the FCCU The user cannot inject this fault 3 16 2...

Страница 22: ...ult 3 17 3 Test circuitry group 3 activation fault 80 In case of unwanted activation of the test circuitry in the related diagnostic function test domain the event is detected and forwarded to the FCC...

Страница 23: ...ause a corrupted ECC correction The EDC after ECC can detect this fault and forward it to the FCCU The user cannot inject this fault 3 19 MC_RGM fault The MC_RGM centralizes the different reset source...

Страница 24: ...O buffers over temperature pressure and voltage Figure 21 Compensation cell fault RGM Error out Reset request reset Compensation Cell FCCU INTC Interrupt request Interrupt Fault 95 Set Clear 3 20 1 Pa...

Страница 25: ...of fault Enable output pins For each fault identified as testable the software Verify the FCCU status before injection If it is in normal state proceed otherwise if it is in alarm or fault state stop...

Страница 26: ...d lower than the trip time for example 12 hours The methodology for these tests is based on fault injection and verification whether the FCCU correctly receives it and depends on the specific FCCU inp...

Страница 27: ...nterrupt request JTAG NPC Joint Test Action Group Nexus debug port LBIST Logic Built in self test LVD Low voltage detector MC_ME Mode entry module MCU Microcontroller Unit NMI Non maskable interrupt N...

Страница 28: ...rystal Table 3 Reference documents Document name Document title RM0403 SPC58 2B Line 32 bit Power Architecture automotive MCU z2 core 80 MHz 1 MByte Flash ASIL B ES0413 SPC582Bx devices errata JTAG_ID...

Страница 29: ...Revision history Table 4 Document revision history Date Revision Changes 26 Nov 2021 1 Initial release AN5752 AN5752 Rev 1 page 29 35...

Страница 30: ...fault 6 9 3 3 2 BIST result wrong signature STCU recoverable fault fault 7 9 3 3 3 MBIST control activation fault 8 9 3 4 Glue logic faults 10 3 4 1 JTAG NPC or debug functionality out of reset or SS...

Страница 31: ...erflow error fault 29 16 3 10 IMA fault 16 3 10 1 IMA activation fault 30 17 3 11 SMPU faults 17 3 11 1 SMPU XBAR 1 monitor incorrectly refuses an access fault 32 17 3 11 2 SMPU XBAR 1 monitor correct...

Страница 32: ...3 17 3 Test circuitry group 3 activation fault 80 22 3 17 4 Test circuitry group 4 activation fault 81 22 3 18 PBRIDGE faults 22 3 18 1 PBRIDGE_1 e2eEDC error fault 89 23 3 18 2 PBRIDGE_1 e2eEDC error...

Страница 33: ...List of tables Table 1 FCCU failure inputs 2 Table 2 Acronyms and abbreviations 27 Table 3 Reference documents 28 Table 4 Document revision history 29 AN5752 List of tables AN5752 Rev 1 page 33 35...

Страница 34: ...96 10 Figure 8 DMA faults 11 Figure 9 Flash PFLASHC faults 12 Figure 10 SWT faults 14 Figure 11 MEMU faults 15 Figure 12 IMA fault 17 Figure 13 SMPU faults 17 Figure 14 PLL DIG faults 18 Figure 15 CM...

Страница 35: ...ts and ST assumes no liability for application assistance or the design of Purchasers products No license express or implied to any intellectual property right is granted by ST herein Resale of ST pro...

Отзывы:

Нет отзывов