Using Validation view

Validation tab has embedded multiple tabs, with different functionalities:

Init - offers possibility to initialize DDR subsystem without any additional memory tests.
Diags - offers TxEye and RxEye diagnostic tests. TxEye and RxEye will run Firmware Init automatically and will output eye diagrams. For more information please refer to Diag margin test
Operational - offers a suite of operational tests that will run Firmware Init and then perform basic operations like writing logical '1' and reading for given DDR memory ranges or stress testing a DDR region. For more information please refer to Operational Tests
Shmoo - contains a suite of tests designed to experiment with different Initial Board Setting values and display a map of the results. For more information please refer to Shmoo Tests

To begin testing please configure in DDR View the required settings, select and configure the test to be performed and configure the desired connection by choosing connection type and connection settings.

Connection type can be one of the following:

Serial connection – COM port must be specified. Clicking on the COM port scanning button populates the combo selection options with all the available COM ports while displaying live scanning process progress.


Figure 1. COM port scanning

S32 Debug Probe - USB device or IP/Hostname must be specified in order to connect, depending on the selected protocol.

For USB connection clicking on "Scan for available USB device" button will populate the USB device selection combo with all S32Probe MAC addrsses that are available. Also the MAC address can be filled manually in the selection combo.


Figure 2. Validation View

After selecting a MAC address the connection with the board can be tested by clicking the "Test connection" button that is gonna show a popup with the result after checking the communication between S32Probe and the board.


Figure 3. Validation View

Note Before starting the Validation, the ddr agent application needs to be running on the target. Flash the binary image from ...\installation_folder\eclipse\mcu_data\processors\PlatformSDK..\scripts\ddrv\binaries\xspi_boot_ddr_agent.bin, change the boot mode and reset the board.

After flashing the ddr agent image, configuring the connection, press Start Validation button and training will begin.

Current progress can be viewed in Summary tab. After test is finished Fail or Pass will be displayed in Result column. For Fail a status will be displayed in Fail reason column. For current progress and more details on execution of tests script consider opening Logs tab.


Figure 4. Validation View

For failing tests, Logs tab displays a Failed Test Report providing additional information about the failure like memory address, expected value, found value, etc. Please see below examples of failed reports for Write Read Compare and Stress tests.


Figure 5. Failed WRC Test Report


Figure 6. Failed Stress Test Report

Decode messages – allows the user to select and decode a binary dump file that contains debug messages logged during training. The decoded messages can be exported in a text file.

Note: The binary file used as input must result from dumping memory after executing DDR training using DDR Tool code generated with Save debug messages option enabled. User should create a memory dump of size PHY_LOG_SIZE (see ddr_utils.h), starting with the first selected address in DDR View.