SPRZ488E March   2022  – May 2024 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1

 

  1.   1
  2. 1Usage Notes and Advisories Matrices
  3. 2Silicon Usage Notes
    1.     i2324
    2.     i2348
    3.     i2364
  4. 3Silicon Advisories
    1.     i2310
    2.     i2311
    3.     i2313
    4.     i2329
    5.     i2345
    6.     i2346
    7.     i2347
    8.     i2349
    9.     i2350
    10.     i2352
    11.     i2353
    12.     i2354
    13.     i2355
    14.     i2356
    15.     i2357
    16.     i2358
    17.     i2359
    18.     i2374
    19.     i2375
    20.     i2386
    21.     i2392
    22.     i2393
    23.     i2394
    24.     i2395
    25.     i2401
    26.     i2402
    27.     i2403
    28.     i2404
    29.     i2405
    30.     i2427
    31.     i2428
    32.     i2433
    33.     i2438
    34.     i2439
  5.   Trademarks
  6. 4Revision History

i2393

Granular error status not logged in BUS_SAFETY_ERR registers for the detected faults

Details:

Granular error status not logged correctly for detected faults in COMP_CHECK and COMP_ERR fields of MSS_CRTL:*_BUS_SAFETY_ERR registers.

The error signal err_comp and err_comp_signals are used to detect any faults on the diagnostic circuit. The AND'ed output of these two signals are used to report the fault. However they are sampled at different edges of the clocks resulting in loss of the error signal getting generated. and hence is not getting logged in the MSS_CTRL MMRs.

There are two possible scenario:

Case 1: Log registers have non-zero values

Here the granular logs are captured correctly and appropriate action can be taken for a given fault.

Case 2: Log Registers have all zeros

Here the granular logs are not captured correctly and possible entities affected are R5F and L2 memory.

 Figure 3-2

Workaround(s):

No Workaround.

As Granular Error Status is not logged, the bus safety fault is detected only as an aggregated error event and the Granularity of diagnostics information will not be captured correctly.

Case 1: In the case where the logs are captured correctly the log results can be used to take appropriate action.

Case 2: In the case where the logs are not captured correctly then for a) diagnostics no action needed and b) in case of actual failure in the application WarmResetn should be used.