SAF sCheck XRDC test failed

[zyt]

I try to do sCheck XRDC test on S32K3 board, but found it failed.

The direct cause is DMA transfer failed which indicate error in DMA channel after it start.

But the DMA transfer is always success when do EDC and XBIC test.

What's the reason for this failure? How to resolve it?

[jennie258fitz]

When you're experiencing a failure in the sCheck XRDC test on the S32K3 board due to DMA transfer issues, but it works fine during EDC and XBIC tests, there are several potential reasons and solutions to consider:

Possible Causes

1. Configuration Issues:

   • Ensure that the DMA channel configuration for the sCheck XRDC test is correctly set up. Parameters such as source and destination addresses, transfer size, and burst size should match the requirements of the test.

2. Timing and Synchronization:

   • Check if there are timing constraints or synchronization issues between the peripherals involved in the DMA transfer. The DMA might be attempting to access a resource that isn't ready or has been altered.

3. Memory Access Violations:

   • The memory regions involved in the DMA transfer may be restricted or incorrectly mapped. Ensure that the memory addresses being accessed are valid and accessible by the DMA.

4. Peripheral States:

   • Verify that the peripherals involved in the DMA transfer are in the correct state before the transfer begins. If the peripheral isn't ready, it may lead to a DMA error.

5. Interrupt Handling:

   • Ensure that any interrupts related to the DMA transfer are properly configured and enabled. If interrupts are masked or not handled correctly, it could cause DMA failures.

6. Hardware Issues:

   • Check for any physical hardware issues, such as damaged pins or connections, that could affect DMA operation.

Steps to Resolve

1. Review DMA Configuration:

   • Double-check the configuration settings specific to the sCheck Health Insurance Market Place XRDC test, ensuring that they are correctly set up for the transfer.

2. Test with Different Scenarios:

   • Run tests with different configurations, such as varying transfer sizes or addresses, to identify if specific parameters are causing the failure.

3. Monitor Signals:

   • Use an oscilloscope or logic analyzer to monitor the DMA signals during the transfer to see if there are any anomalies or interruptions.

4. Enable Debugging:

   • If available, enable debugging options for the DMA module to provide more detailed error reporting and insights.

5. Validate Memory Regions:

   • Use tools to check that the DMA's source and destination memory regions are accessible and properly aligned.

6. Consult Documentation:

   • Refer to the S32K3 reference manual and DMA controller documentation for any specific notes or guidelines regarding DMA transfers in your testing context.