Appendix VII Test Results
6. Subsystems – JTAG calibration test results
Aim
The aim of the JTAG calibration test plan is to check if the data can be transmitted between the PC and MCUs and be transmitted between the PC and SMU. And check if the MCUs can select the channels. Last, check if users can use GUI to achieve the calibration functions.
Functionality to be tested
• The data can be transferred between the PC and the MCUs.
• The data can be transferred between the PC and the SMU, and the SMU can work based on the commands from PC.
• The MCUs can select the target channel, including TDI, TCK, TMS and TDO channels.
• The SMU can input the correct voltage to the JTAG board and measure the output voltage from it.
• The users can use GUI to achieve the calibration functions.
Hypothesis
All the hardware of the JTAG calibration subsystem can work and cooperate well. The data communication between the PC and MCUs and between the PC and the SMU is working.
Furthermore, the subsystem can test each channel and all the test results can be shown in the GUI.
Target group & Measuring tools - Target groups
3) JTAG calibration hardware integration.
4) JTAG calibration subsystem’s GUI.
- Measuring tools 3) Multimeter 4) SMU
Actions
1. Power on the EVA2 setup and use a multimeter to check if all the power supplies are correct.
21 2. Connect the SMU with the motherboard via Banana chassis.
3. Insert the EVA2 calibration board into motherboard via six connectors with 96 pins.
4. Open the Delphi project and program to active one channel and input the proper value in to the Edit box and click one ‘calibration’ button.
5. Read the measured value from SMU.
6. Measure the corresponding pins in MCUs and multiplexers.
7. Check the results in the GUI.
8. Click the ‘clear all’ button.
9. Repeat 4-8 steps when all channels have been checked (TDI, TCK, TMS and TDO).
10. Close the Delphi project and end the test.
Average bandwidth of reactions
Table 1-6 JTAG calibration subsystem's average bandwidth of reactions
JTAG calibration
Action Reaction Bandwidth
of reactions
Possible causes of failure
The results of active one of TDI,
Succuss 1. Wrong programming code for activating the symbol.
2. Wrong codes for showing the results in a new window.
controlling the SMU is wrong.
2. Wrong code for setting the input value to JTAG modules. in DAC modules are damaged. sending data to Fail
22 activate the pins of PCA9555. in DAC modules are damaged.
2. The wrong code in JTAG driver.
3. Wrong code for setting the input value to DAC modules.
4. Wrong code about sending data to activate the pins of PCA9555 which take charge of activating the pins of the multiplexer.
Fail
The results of selecting TDO channel and click TDO ‘calibration’
Succuss 1. Wrong programming codes for activating the symbol.
2. Wrong codes for showing the results in a new window.
controlling the SMU is wrong.
2. Wrong code for setting the input value to JTAG modules.
3. The wrong code in JTAG driver.
4. The input voltage of DAC modules is too low to activate the DAC modules Fail
23 in DAC modules are damaged.
2. Wrong code about the PCA9555 address.
3. Wrong code about sending data to activate the pins of PCA9555.
4. The input voltage of DAC modules is too low to activate the DAC modules in DAC modules are damaged.
2. Wrong code for setting the input value to DAC modules.
3. Wrong code about sending data to activate the pins of PCA9555 which take charge of activating the pins of the multiplexer.
4. The input voltage of DAC modules is too low to activate the DAC modules
Predicted conclusions
If all the reactions corresponding to the actions are successful, then the JTAG calibration
subsystem is functional. If there are some failed reactions, then the JTAG calibration subsystem should still be modified based on the possible causes in the table above.
7. Subsystem – Oscilloscope calibration
Aim
The aim of the Oscilloscope calibration test plan is to check if the data can be transmitted between the PC and MCUs. And check if the MCUs can select the channels. Last, check if users can use GUI to achieve the calibration functions.
24 Functionality to be tested
• The data can be transferred between the PC and the MCUs.
• The MCUs can select the target channel.
• The DC signals can be provided by SMU.
• The oscillator’s output square signal can be measured via the test point.
• The GUI can open the Picoscope software.
• The users can use GUI to achieve the calibration functions.
Hypothesis
All the hardware of the Oscilloscope calibration subsystem can work and cooperate well. The data communication between the PC and MCUs. Furthermore, the oscillator’s output square signal can be measured via the test point. Last, the subsystem can test each channel and all the test results can be shown in the Picoscope software.
Target group & Measuring tools - Target groups
1) Oscilloscope calibration hardware integration.
2) Oscilloscope calibration subsystem’s GUI.
- Measuring tools 1) Multimeter
2) Calibrated oscilloscope 3) Calibrated AFG
Actions
1. Power on the EVA2 setup and use a multimeter to check if all the power supplies are correct.
2. Insert the EVA2 calibration board into motherboard via six connectors with 96 pins.
3. Connect two oscilloscopes with the EVA2 calibration board via BNC connectors.
4. Open the Delphi project and program to active one channel and input the square signal with a calibrated AFG into the input pins of multiplexer.
5. Measure the output value of signal from multiplexer’s output pins with calibrated oscilloscope.
6. Measure the signal via the test point.
7. Select the square signal and one frequency.
8. Select one channel and click ‘calibration’ button.
9. Measure the corresponding pins in MCUs and multiplexers.
10. Open the Picoscope software by clicking the ‘Open Picoscope’ button.
11. Check the results in the Picoscope.
12. Repeat 7-11 steps when all channels have been checked with all different frequency selections.
25 13. Close the Picoscope software.
14. Select the DC signal.
15. Set the input value of DC signal by writing to the edit box.
16. Select one channel and click ‘calibration’ button.
17. Measure the corresponding pins in MCUs and multiplexers.
18. Open the Picoscope software by clicking the ‘Open Picoscope’ button.
19. Repeat 14-18 steps when all channels have been checked with different DC signals.
20. Close the Picoscope software.
21. Close the Delphi project and end the test.
Average bandwidth of reactions
Table 1-7 Oscilloscope calibration subsystem's average bandwidth of reactions
Oscilloscope calibration
Action Reaction Bandwidth
of
reactions
Possible causes of failure
The results of the output signals of the oscillator
The results of the output signals of the oscillator is same as the 0.625Mhz(or in the error range)
Succuss 1. The binary ripple counter is broken.
2. The oscillator is broken.
3. Wrong code about sending data to activate the pins of PCA9555 which take charge of activating the enable pins of the counter.
Fail
The results of the output values of the SMU
The results of the output values of the SMU is same as the input value in the edit box.
Succuss 1. The driver for activating and
controlling the SMU is wrong.
2. Wrong code for setting the output value of SMU.
Fail
The results of clicking the
‘Open Picoscope’
button.
The Picoscope software can be open
Succuss 1. Wrong code for activating the Picoscope software.
Fail
26 The results of
active one of four channels of oscilloscope 1 and click the in DAC modules are damaged.
2. Wrong code about the PCA9555 address.
3. Wrong code about sending data to activate the pins of PCA9555.
4. Insert the connectors of oscilloscope into wrong BNC
connectors of EVA2 calibration board.
Fail
The results of active one of four channels of oscilloscope 2 and click the in DAC modules are damaged.
2. Wrong code about the PCA9555 address.
3. Wrong code about sending data to activate the pins of PCA9555.
4. Insert the connectors of oscilloscope into wrong BNC
connectors of EVA2 calibration board.
Fail
Predicted conclusions
If all the reactions corresponding to the actions are successful, then the oscilloscope calibration subsystem is functional. If there are some failed reactions, then the oscilloscope calibration subsystem should still be modified based on the possible causes in the table above.
8. Subsystem – AFG calibration
Aim
The aim of the AFG calibration test plan is to check if the data can be transmitted between the PC and MCUs. And check if the MCUs can select the channels. Last, check if users can use GUI to achieve the calibration functions.
27 Functionality to be tested
• The data can be transferred between the PC and the MCUs.
• The MCUs can select the target channel.
• The GUI can open the Picoscope software.
Hypothesis
All the hardware of the AFG calibration subsystem can work and cooperate well. The data communication between the PC and MCUs. Furthermore, the GUI can open the Picoscope software.
Target group & Measuring tools - Target groups
1) AFG calibration hardware integration.
2) AFG calibration subsystem’s GUI.
- Measuring tools 1) Multimeter
2) Calibrated oscilloscope Actions
1. Power on the EVA2 setup and use a multimeter to check if all the power supplies are correct.
2. Insert the EVA2 calibration board into motherboard via six connectors with 96 pins.
3. Connect one oscilloscope with the EVA2 calibration board via BNC connectors.
4. Connect the AFG with the EVA2 calibration board via BNC connectors.
5. Open the Delphi project and input the signal by setting AFG manually.
6. Select one channel and click ‘calibration’ button.
7. Measure the corresponding pins in MCUs and multiplexers.
8. Open the Picoscope software by clicking the ‘Open Picoscope’ button.
9. Check the results in the Picoscope.
10. Repeat 5-9 steps when all channels have been checked with all different input signals of AFG.
11. Close the Delphi project and end the test.
Average bandwidth of reactions
Table 1-8 AFG calibration subsystem's average bandwidth of reactions AFG calibration Action Reaction Bandwidth
of reactions
Possible causes of failure
The results of clicking the
‘Open
The Picoscope software can be open
Succuss 1.Wrong code for activating the Picoscope software.
28 Picoscope’
button.
Fail
The results of active one of two channels of AFG and click in DAC modules are damaged.
2. Wrong code about the PCA9555 address.
3. Wrong code about sending data to activate the pins of PCA9555.
4. Insert the connectors of oscilloscope1 into wrong BNC connectors of EVA2 calibration board.
5. Insert the connectors of AFG into wrong BNC connectors of EVA2 calibration board Fail
Predicted conclusions
If all the reactions corresponding to the actions are successful, then the AFG calibration
subsystem is functional. If there are some failed reactions, then the AFG calibration subsystem should still be modified based on the possible causes in the table above.
29
Appendix II PCB Schematics
In this appendix, the integration sheet will be first shown. Then, as mentioned in Chapter 4 Results, the ADC, DAC and Power IO modules are connecting to the EVA2 calibration device with six 96 channels connectors including connector A to F, so the PCB schematics for ADC, DAC and PowerIO subsystems are designed in same six schematics which will be demonstrated in the schematics of connector A to F. Next will be the schematic of JTAG subsystem and the final will be the schematic of oscilloscope and AFG subsystems.
1. Integration sheet
Figure 2-1 schematic of integration sheet
30
2. Connector A
3. Connector B
Figure 2-2 schematic of connector A
Figure 2-3 schematic of connector B
31
4. Connector C
5. Connector D
Figure 2-4 schematic of connector C
Figure 2-5 schematic of connector D
32
6. Connector E
7. Connector F
Figure 2-6 schematic of connector E
Figure 2-7 schematic of connector F
33
8. JTAG subsystem
Figure 2-8 schematic of JTAG subsystem
34
9. Oscilloscope and AFG subsystems
Figure 2-9 Schematic of oscilloscope and AFG subsystems
35
Appendix III The logic table for multiplexers
1. 74HC4067DB
2. 74HC4066
Figure 3-1 Logic table of 74HC4067DB (Nexperia, 74HC4067DB, 2021)
Figure 3-2 Logic table of 74HC4066 (Nexperia, 74HC4066; 74HCT4066, 2020)
36
3. 74HC4051D
4. MAX14757EUET
Figure 3-3 Logic table of 74HC4051 (Nexpiria, 2017)
Figure 3-4 Logic table of MAX14757EUET (Maximintegrated, 2021)
37
Appendix IV PCB layout
Figure 4-1 PCB layout- 3D version
Figure 4-2 PCB layout- 2D version
38
Appendix V The logic diagrams for GUI design
1.
Logic diagram for ADC subsystem
Figure 5-1Logic diagram of ADC subsystem
39 2.
Logic diagram of DAC subsystem
Figure 5-2 Logic diagram of DAC subsystems
40 3.
Logic diagram of PowerIO subsystem
Figure 5-3 Logic diagram of PowerIO subsystem
41 4.
Logic diagram of JTAG subsystem
Figure 5-4 Logic diagram of JTAG subsystem
42 5.
Logic diagram of AFG subsystem
6.
Logic diagram of Oscilloscope subsystem
Figure 5-5 Logic diagram of AFG subsystem
Figure 5-6 Logic diagram of Oscilloscope subsystem
43 7.
Logic diagram of main GUI design
Figure 5-7 The logic diagram of the main GUI design
44
Appendix VI User Manual (GUI design)
1. ADC and DAC subsystems
The hardware must be used with the software which is combined with both GUI and codes parts. The GUI of the ADC and DAC subsystems are shown in the Figure 6-1 and 6-2.
The two GUI are quite similar and the only one difference is the input value. When user has determined the input value and pressed the all channel ‘calibration’ button, the software will calibrate all the channel automatically and record the failed channels’ value. During this period, the success channels will have green symbols while the failed will have the red. After calibrating all the channel and pressing ‘read failed value’ button, all the failed channel’s result will be
Figure 6-1 GUI for DAC subsystem
Figure 6-2 GUI for ADC subsystem
45 shown in a new window. Furthermore, when setting to calibrate any one channel and pressing the ‘calibration’ button, the target channel’s test result will be shown in a new window
automatically and the ‘read failed value’ bottom cannot be pressed. Last, when pressing the
‘Clear All’ button, all the results will be reset, and the green & red symbol will disappear.
2. PowerIO subsystem
The GUI design as shown in the Figure 6-3 is introduced below.
First, when the all channel ‘calibration’ button is pressed, the software will calibrate all the channel automatically and record the failed channels’ value and the corresponding red or green images will show. Also, all the failed channel’s result will be shown in a new window when pressing ‘read failed value’ button. Similarly, after user determine which channel to be
calibrated and press the ‘calibration’ button, the red or green symbol will appear, and the test result will be shown in a new window. Additionally, when clicking the ‘Clear all’ button, all the images about the test result will disappear.
Figure 6-3 GUI for PowerIO subsystem
46
3. JTAG subsystem
The GUI design as shown in the Figure 6-4 is expounded below.
At the beginning, the user can determine the input voltage among the range of VCCB supply voltage from 1.5 to 5.5 V and choose the ‘calibration’ button in the ‘Channel selection’ group box. If the user pressed the calibration button for single channel, then the program will calibrate the chosen channel and if it was failed, the red symbol will show with a measured value in a new window, whereas, if the measured result was same as the input, the green symbol will show. Last, when the ‘Clear all’ button be pressed, all the green and red symbols will disapeared.
Figure 6-4 GUI design of JTAG subsystem
47
4. Oscilloscope and AFG subsystems
The GUI designs for the oscilloscope and AFG subsystems are shown in the Figure 6-5 and 6-6.
Figure 6-6 GUI for AFG subsystem Figure 6-5 GUI for oscilloscope subsystem
48 The oscillator should be calibrated first before calibrating the Pico5444D and Pico2406B. It is required the user to use the calibrated oscilloscope to measure the output frequency of the oscillator via J13 and click the ‘Oscillator is calibrated’ check box after writing the value into the edit box. If the input value was not 0, the software will show a message as shown in the Figure 6-7, and if the input value of the edit box was 0, then the software will show another window as shown in the Figure 6-8. Besides, if the oscillator is not calibrated first, the three ‘Calibration’
buttons are not available to be pressed as the orange box shown in Figure 6-5.
After that, user can choose only one desired signal type on the green box in Figure 6-5. If user click both two checkboxes, the window shown in Figure 6-9.
When user choosing one type of the signal the value choosing box will appear as the figure demonstrating below and the user can select or write the input desired value.
After that, the user is required to click the ‘Open Picoscope’ button to execute the Picoscope software and all the ‘calibration’ buttons are available for pressing. The user can choose to calibrate all the channels from the Pico5444D or the Pico2406B or any one channel from them.
The value input to the oscilloscope will be shown in the blue box of Figure 6-5 which is designed for users to compare it with the value in the Picoscope more conveniently. Last, when clicking the ‘Reset’ button, the whole program will be reset.
Figure 6-8 Window2 (Oscilloscope subsystem) Figure 6-7 Window1 (Oscilloscope subsystem)
Figure 6-9 Window3 (Oscilloscope subsystem)
Figure 6-10 The input signal selection box of oscilloscope subsystem
49 As what shown in the Figure 6-5, the GUI designed for the AFG subsystem is only for selecting the target channel and open the Picoscope software. The user can calibrate the AFG following by the steps in the ‘Calibration process’.
50
Appendix VII Test Results
1. EVA2’s function check results
- ADC modules 1) 1.25V
2) 4V
Figure 7-1 ADC modules 1.25 V test results
Figure 7-2 ADC modules 4 V test results
51 - DAC modules
1) 1V
2) 4V
- PowerIO modules
Figure 7-5 PowerIO modules test results Figure 7-3 DAC modules 1 V test results
Figure 7-4 DAC modules 4 V test results
52 - Power supply
2. System verification test results
Table 7-1 System verification test results
Test GUI Results
ADC calibration GUI Can be opened
DAC calibration GUI Can be opened
JTAG calibration GUI Can be opened
PowerIO calibration GUI Can be opened
Oscilloscope calibration GUI Can be opened
AFG calibration GUI Can be opened
3. Subsystems – ADC calibration test results
- All channels calibration (input 0.5V)
Figure 7-6 Power supply test results
Figure 7-7 ADC calibration all channels test results
53 - One channel calibration (input 2V)
4. Subsystems – DAC calibration test results
- All channels calibration (Input 2.5V)
- One channel calibration (Input 1V)
Figure 7-8 ADC calibration one channel test result
Figure 7-9 DAC calibration all channels test results
Figure 7-10 DAC calibration one channel test result
54
5. Subsystems – PowerIO calibration test results
- All channels calibration
- One channel calibration
Figure 7-11 PowerIO calibration all channels test results
Figure 7-12 PowerIO calibration one channel test result
55
6. Subsystems – JTAG calibration test results
- TDI channel
- TCK channel
- TMS channel
Figure 7-13 JTAG calibration TDI channel test result
Figure 7-14 JTAG calibration TCK channel test result
Figure 7-15 JTAG calibration TMS channel test result
56 - TDO channel