SPRZ570A November   2023  – May 2024 AM263P4 , AM263P4-Q1

 

  1.   1
  2.   Abstract
  3. 1Usage Notes and Advisories Matrices
  4. 2Silicon Revision 1.0 Usage Notes and Advisories
    1. 2.1 Silicon Revision 1.0 Usage Notes
      1.      i2324
    2. 2.2 Silicon Revision 1.0 Advisories
      1.      i2189
      2.      i2310
      3.      i2374
      4.      i2311
      5.      i2345
      6.      i2351
      7.      i2352
      8.      i2353
      9.      i2354
      10.      i2356
      11.      i2357
      12.      i2358
      13.      i2359
      14.      i2383
      15.      i2392
      16.      i2393
      17.      i2394
      18.      i2401
      19.      i2403
      20.      i2404
      21.      i2405
      22.      i2426
      23.      i2427
      24.      i2428
      25.      i2433
      26.      i2438
      27.      i2439
  5. 3Trademarks
  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.

AM263Px Figure 2-1

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.