Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
resources:eval:user-guides:pzsdr:testing [16 Jun 2022 14:15] – [Power Sequencer] Monica Constandachiresources:eval:user-guides:pzsdr:testing [20 Feb 2023 13:57] (current) – updated fmc carrier sd card image Monica Constandachi
Line 20: Line 20:
    * The instructions regarding the setup and how to program the sequencer can be found by clicking on the link below.    * The instructions regarding the setup and how to program the sequencer can be found by clicking on the link below.
    * After opening the link, follow the steps that use the **USB-SDP-CABLEZ serial I/O Interface**.    * After opening the link, follow the steps that use the **USB-SDP-CABLEZ serial I/O Interface**.
-   * Make sure the sequencer is programmed before starting the production testing+ 
  
  
Line 31: Line 31:
  
 <WRAP lo round download 80%> <WRAP lo round download 80%>
-  * **January 2016 release **+* **22 June 2022 release ** 
 +  * [[https://swdownloads.analog.com/cse/prod_test_rel/adrv9361_bob/adrv9361_brk_production.zip|Actual file for SOM2 Testing]] 
 +  * **22 January 2016 release **
   * [[http://swdownloads.analog.com/cse/picozed/picozed-sdr2-brk-test-2016_01_05.img.xz|Actual file for SOM2 Testing]]   * [[http://swdownloads.analog.com/cse/picozed/picozed-sdr2-brk-test-2016_01_05.img.xz|Actual file for SOM2 Testing]]
   * Checksum picozed-sdr2-brk-test-2016_01_05.img.xz ''f070bb467a23d42f3bebe25f70876ed2''   * Checksum picozed-sdr2-brk-test-2016_01_05.img.xz ''f070bb467a23d42f3bebe25f70876ed2''
Line 44: Line 46:
  
 <WRAP lo round download 80%> <WRAP lo round download 80%>
 +  * **27 July 2022 release **
 +  * [[https://swdownloads.analog.com/cse/prod_test_rel/adrv9364_bob/adrv9364_bob_production.zip|Actual file for SOM1 Testing]]
   * **14 August 2020 release **   * **14 August 2020 release **
   * [[https://swdownloads.analog.com/cse/prod_test_rel/picozed_test/picozed-sdr1-brk-test-2020_14_08.img.tar.xz|Actual file for SOM1 Testing]]   * [[https://swdownloads.analog.com/cse/prod_test_rel/picozed_test/picozed-sdr1-brk-test-2020_14_08.img.tar.xz|Actual file for SOM1 Testing]]
 </WRAP> </WRAP>
  
 +<WRAP lo round download 80%>
 +  * **27 July 2022 release **
 +  * [[https://swdownloads.analog.com/cse/prod_test_rel/adrv9364_bob/rpi_adrv9364_production.zip|Raspberry Pi file for SOM1 Testing]]
 +  * **22 June 2022 release **
 +  * [[https://swdownloads.analog.com/cse/prod_test_rel/adrv9361_bob/raspberry_pi_som2_test.zip|Raspberry Pi file for SOM2 Testing]]
 +</WRAP>
 <WRAP center round important 60%> <WRAP center round important 60%>
 It is also possible to manually create one using [[/resources/eval/user-guides/pzsdr/testing/sd-cards#som1|these instructions]]. It is also possible to manually create one using [[/resources/eval/user-guides/pzsdr/testing/sd-cards#som1|these instructions]].
Line 59: Line 69:
 ==== Required hardware ==== ==== Required hardware ====
  
-  * Frequency counter with a USB-GPIB port (tested with an [[https://www.rohde-schwarz.com/fi/product/hm8123-productstartpage_63493-44102.html|Hameg HM8123]]) with dual-probe attachment;+  * Frequency counter with a USB-GPIB port (tested with an [[https://www.rohde-schwarz.com/fi/product/hm8123-productstartpage_63493-44102.html|Hameg HM8123]]) with BNC to dual-probe minigraber;
   * Raspberry Pi 4 with provided Linux image, keyboard, mouse, micro-HDMI cable, and a monitor with HDMI input;   * Raspberry Pi 4 with provided Linux image, keyboard, mouse, micro-HDMI cable, and a monitor with HDMI input;
   * 1 adrv936x_rfsom breakout board and loopback test fixture;   * 1 adrv936x_rfsom breakout board and loopback test fixture;
Line 83: Line 93:
   * Insert the flash drive into the OTG port on the breakout board. Make sure the USB jumper is set to OTG mode on the breakout board, see the image below for confirmation of correct positioning.   * Insert the flash drive into the OTG port on the breakout board. Make sure the USB jumper is set to OTG mode on the breakout board, see the image below for confirmation of correct positioning.
   * Insert the frequency counter USB into the Raspberry Pi.   * Insert the frequency counter USB into the Raspberry Pi.
-  * The probes of the frequency counter should be attached to the pin on the fan plugin nearest to the power switch on the breakout board and to a ground location such as the pin accessible through the cutout on the side of the JTAG header. Below there's a view of the probe locations. Also, note the labels on the USB ports in order to plug them in the right locations for the media drive and UART connection to the Raspberry Pi.+  * The "INPUT A" of the frequency counter should be attached to the pin on the fan plugin nearest to the power switch on the breakout board and to a ground location such as the pin accessible through the cutout on the side of the JTAG header. Below there's a view of the probe locations. Also, note the labels on the USB ports in order to plug them in the right locations for the media drive and UART connection to the Raspberry Pi.
  
  
Line 100: Line 110:
 {{ :resources:eval:user-guides:pzsdr:mac_address.png | &400}} {{ :resources:eval:user-guides:pzsdr:mac_address.png | &400}}
  
-Make sure all the required setup explained above is completed and the frequency counter is turned on in addition to the Raspberry Pi running the test script. Once the test setup is ready, SOM testing should be done using the following steps:+  * Make sure the sequencer is programmed before starting the production testing. 
 +  * Make sure all the required setup explained above is completed and the frequency counter is turned on in addition to the Raspberry Pi running the test script. Once the test setup is ready, SOM testing should be done using the following steps:
  
 <note important>If it is the first time you run a test on your setup, there will be a prompt asking you to input the password for uploading test logs remotely. Type in the password provided and press enter. The password is then stored locally and there will be no need to this further.</note> <note important>If it is the first time you run a test on your setup, there will be a prompt asking you to input the password for uploading test logs remotely. Type in the password provided and press enter. The password is then stored locally and there will be no need to this further.</note>
Line 134: Line 145:
   * USB host mode: a Micro USB (male) an adapter to type A (female) is used to connect a usb flash, lsusb linux command is run on carrier to see if host mode is enabled and flash is detected, check speed with hdparm, check that partition is mounted   * USB host mode: a Micro USB (male) an adapter to type A (female) is used to connect a usb flash, lsusb linux command is run on carrier to see if host mode is enabled and flash is detected, check speed with hdparm, check that partition is mounted
   * Ethernet: A cable is connected between the board's Ethernet ports and a ping between them is forced over the wire. The test passes if a response is received, otherwise it fails   * Ethernet: A cable is connected between the board's Ethernet ports and a ping between them is forced over the wire. The test passes if a response is received, otherwise it fails
-  * Audio: Audio loopback cables plugged into horizontal sets of output/input jacks. Using Advanced Linux Sound Architecture(ALSA) commands like speaker-test and arecord, a sine signal is sent, recorded back. Then the recorded file is analyzed to determine the frequency of the recorded tone matches the input frequency+  * Audio: Audio loopback cables plugged into horizontal sets of output/input jacks. Using Advanced Linux Sound Architecture (ALSA) commands like speaker-test and arecord, a sine signal is sent, recorded back. Then the recorded file is analyzed to determine the frequency of the recorded tone matches the input frequency
   * HDMI: Monitor connectivity is checked through physical displaying output on the attached monitor   * HDMI: Monitor connectivity is checked through physical displaying output on the attached monitor
   * Clocks: he clock monitor IP (axi_clock_monitor) is used to test several clock signal paths. The IP features a mechanism which measures the input clock frequency relative to the system clock and stores the result in an internal register. By checking if the measured clock signal is within an expected range the path is validated. 4 clock signals are measured, 3 of them generated by the FMC loopback at the same frequency of 156MHz and one is generated by the AD9517 PLL   * Clocks: he clock monitor IP (axi_clock_monitor) is used to test several clock signal paths. The IP features a mechanism which measures the input clock frequency relative to the system clock and stores the result in an internal register. By checking if the measured clock signal is within an expected range the path is validated. 4 clock signals are measured, 3 of them generated by the FMC loopback at the same frequency of 156MHz and one is generated by the AD9517 PLL
Line 147: Line 158:
 <WRAP hi round download 80%> <WRAP hi round download 80%>
   * **20 Dec 2021 release **   * **20 Dec 2021 release **
-  *  [[https://swdownloads.analog.com/cse/prod_test_rel/adrv1crr_test/adrv1crr_fmc_production_image.zip |Actual file]] +  *  [[https://swdownloads.analog.com/cse/prod_test_rel/adrv1crr_test/adrv1_carrier_14_02_2023.zip |Actual file]] 
-  * Checksum ''8bae66480dc95e09932355bc4f1aa87c''+  * Checksum ''d2c1ad4dfd4d91c5601be28a7d227c9c''
 </WRAP> </WRAP>
  
Line 179: Line 190:
   * 1 adrv9361_rfsom module   * 1 adrv9361_rfsom module
   * 1 adrv9361_rfsom FMC carrier board (ADRV1CRR)   * 1 adrv9361_rfsom FMC carrier board (ADRV1CRR)
-  * 1 microSD card and SD adapter with the latest test image ([[resources/tools-software/linux-software/embedded_arm_images|or manually create one]])+  * 1 microSD card and SD adapter with the latest test image ([[:resources:tools-software:linux-software:kuiper-linux|or manually create one]])
   * 1 External monitor with HDMI input   * 1 External monitor with HDMI input
   * 1 Scanner   * 1 Scanner
Line 285: Line 296:
 === Test image === === Test image ===
  
-The production test software running on the target device is the [[/resources/tools-software/linux-software/zynq_images#download_linux_image|standard ADI Zynq image]] modified slightly to run the [[https://github.com/analogdevicesinc/board-tests/tree/master/picozed-brk|test suite]].+The production test software running on the target device is the [[:resources:tools-software:linux-software:kuiper-linux|standard ADI Zynq image]] modified slightly to run the [[https://github.com/analogdevicesinc/board-tests/tree/master/picozed-brk|test suite]].
  
 === Required hardware === === Required hardware ===
Line 296: Line 307:
   * 1 adrv9361_rfsom module   * 1 adrv9361_rfsom module
   * 1 adrv936x_rfsom breakout board and power adapter   * 1 adrv936x_rfsom breakout board and power adapter
-  * 1 microSD card using the latest [[/resources/tools-software/linux-software/zynq_images#download_linux_image|ADI Zynq image]] configured to run the [[https://github.com/analogdevicesinc/board-tests/tree/master/picozed-brk|test suite]]+  * 1 microSD card using the latest [[:resources:tools-software:linux-software:kuiper-linux|ADI Zynq image]] configured to run the [[https://github.com/analogdevicesinc/board-tests/tree/master/picozed-brk|test suite]]
   * 1 External computer set up to monitor the serial connection   * 1 External computer set up to monitor the serial connection
  
resources/eval/user-guides/pzsdr/testing.1655381705.txt.gz · Last modified: 16 Jun 2022 14:15 by Monica Constandachi