Open main menu

DAVE Developer's Wiki β

Changes

no edit summary
{{InfoBoxTop}}
{{Applies To BoraX}}
{{AppliesToBORA_Xpress_TN}}
{{InfoBoxBottom}}
== History ==
The ATE tests the functionalities of the product–also known as device under test (DUT)–by exchanging data over its numerous interfaces. In this case, the DUT integrates some video outputs (namely HDMI, LVDS0, and LVDS1) that consist of differential pairs. These outputs usually drive LCD screens or HDMI monitors. In order to test them, the easiest solution is to connect such displays and to verify that the test images are visualized properly. Even though this approach is straightforward, it is very economically inefficient from the economic standpoint because it is slow and error-prone, as it requires a human operator to visually inspect the displays.
The solution described in this technical note addresses this issue. By implementing an automatic test system, it fully releases the operator from this task. Also, the test is much quicker and much more reliable, as it implements a 100% coverage of the pixels the test frames are composed of.
===Programmable Logic===
The PL integrates the actual test logic, which is depicted in the following image.
 
[[File:Borax_DMTRGB_block_design.png|thumb|center|600px|Video Test PL Block Diagram]]
TBD
mettere On this specific implementation, the DUT has 3 video output interfaces: HDMI, LVDS0, and LVDS1. The VTM is able to verify all the video interfaces at the same time thanks to the BoraX SOM resources availability, in evidenza l'accessibilità ai registri da PS e da I2Cterms of PL logic resources and pinout. The high pin count permits to connect 3 RGB parallel video streams with 24 bit of data.
There are two ways The Checksum/CRC test logic can elaborate up to access 60 frames per second on a Full-HD video stream. This reduces the PL logic register, from ATE test time because on a time windows of few seconds the VTM can elaborate several hundreds of video frames.
This allows All the VTM PL logic blocks are connected to works as:the AXI bus. Also, an I2C slave to AXI bridge was implemented.
1) stand-alone device - a dedicated sw (bare metal or linux OS) that runs on PS can setup This allows the PL logic and verify the video streamsVTM to work as:
2#Stand-alone device - a dedicated software (bare metal or Linux OS based) slave running on the PS can setup the PL logic and verify the video streams. In this case, the PS access the configurations register through the AXI bus.#Slave device of the ATE - an external I2C master I2C can setup set up the PL logic and verify the video streams through a the I2C -to-AXI bridge (implemented on PL logic).
This is possible with a single PL configuration bitstream thanks to use using of Xilinx® LogiCORE™ IP AXI Interconnect core. It permits to connect which allows connecting one or more AXI memory-mapped master devices to one or more memory-mapped slave devices.
===The automatic test procedure===
8,186
edits