1. M3: ProDiver 525 *Kavita Arora (M3-1) Lisa Gentry (M3-2) Steven Wasik (M3-3) Karolina Werner (M3-4) Stage : 9 Mar 29 Chip Level Simulation Overall Project Objective: To design a chip for a SCUBA diver that does real-time calculations to warn the diver of safety concerns including decompressions sickness and lung overexpansion. Design Manager: Steven Beigelmacher

2. M3: ProDiver 525 Status Schematic Verification (done) Schematic Verification (done) LVS LVS –PressureCalc(done) –timetoflight (done) –timeleft (done) –ascensionWatch (done) –getK (done) –safetyWatch (done) –maxDepth (done) –bottomTime (done) –Top (done) Spice Entire Chip (6 out of 8 modules) Spice Entire Chip (6 out of 8 modules)

3. M3: ProDiver 525 Verilog Verification (gate level) MATLAB: depthvector = [80*ones(1,60*35) 40*ones(1,60*20) 0*ones(1,60*40)]; [bodyvector,out]=pressurecalculator(depthvector); bodyvector(60*35): ans = 25.5304 bodyvector(60*55): ans = 28.3850 bodyvector(60*95): ans = 18.2900 SCENERIO: diver goes 80 feet for 35 min, 40 feet for 20 min, 0 feet for 40 min VERILOG: time= 2,safetywatch = 0 Test where the user will go down to 80 feet for 35 minutes, then 40 feet for 20 minutes, then 0 feet 40 minutes time= 6090,safetywatch = 1 time = 6305,pres=25,depth= 80 time= 9054,safetywatch = 2 time = 9908,pres=28,depth= 40 time= 10272,safetywatch = 1 time= 12165,safetywatch = 0 time = 17110, pres=18,depth= 0

4. M3: ProDiver 525 Top Level Schematic

5. M3: ProDiver 525 Internal Routing

6. M3: ProDiver 525 Top Layout

7. M3: ProDiver 525 Summary of Design Characteristics Final area203*151=30653 Transistor Count10110 Transistor Density0.329820898 Aspect Ratio1.344370861

8. M3: ProDiver 525 Why Modular Spice Simulation Strategy ? Due to the large no. of edge cases, this simulation strategy gives us greater accuracy than a single global vector set would Due to the large no. of edge cases, this simulation strategy gives us greater accuracy than a single global vector set would Testing time for global testing is unfeasible because it takes on the order of 150 clock cycles to cause some outputs to change Testing time for global testing is unfeasible because it takes on the order of 150 clock cycles to cause some outputs to change This is quicker and allows us to better focus our energies This is quicker and allows us to better focus our energies

9. M3: ProDiver 525 Spice Simulation Strategy Used vector sets from the verilog verification Used vector sets from the verilog verification Tested the edge cases Tested the edge cases In order to decrease testing time, we brought lower order bits out of the modules (shows seconds as well as minutes, and uses fractions of a pressure unit) In order to decrease testing time, we brought lower order bits out of the modules (shows seconds as well as minutes, and uses fractions of a pressure unit)

10. M3: ProDiver 525 Bottom Time Inputs

11. M3: ProDiver 525 Bottom Time Outputs

12. M3: ProDiver 525 Get K Inputs

13. M3: ProDiver 525 Get K Outputs

14. M3: ProDiver 525 Max Depth1 Inputs

15. M3: ProDiver 525 Max Depth1 Outputs

16. M3: ProDiver 525 Max Depth2 Inputs

17. M3: ProDiver 525 Max Depth2 Outputs

18. M3: ProDiver 525 PressureCalc: case X=0; Y=0

19. M3: ProDiver 525 PressureCalc: 2 nd set of inputs x=0,y=0

20. M3: ProDiver 525 PressureCalc outputs: x=0, y=0

21. M3: ProDiver 525 PressureCalc 2 nd set of outputs: x=0, y=0

22. M3: ProDiver 525 PressureCalc: x=0 y=1

23. M3: ProDiver 525 PressureCalc: 2 nd set of inputs - x=0 y=1

24. M3: ProDiver 525 PressureCalc Outputs: x=0, y=1

25. M3: ProDiver 525 PressureCalc 2 nd set of Outputs: x=0, y=1

26. M3: ProDiver 525 PressureCalc: x=1, y=0

27. M3: ProDiver 525 PressureCalc: 2 nd set of x=1, y=0

28. M3: ProDiver 525 PressureCalc Outputs: x=1,y=0

29. M3: ProDiver 525 PressureCalc 2 nd set of Outputs: x=1,y=0

30. M3: ProDiver 525 PressureCalc: x=1,y=1

31. M3: ProDiver 525 PressureCalc: 2 nd set of inputs x=1,y=1

32. M3: ProDiver 525 PressureCalc Outputs: x=1,y=1

33. M3: ProDiver 525 PressureCalc 2 nd set of Outputs: x=1,y=1

34. M3: ProDiver 525 SafetyWatch

35. Clock Speed Critical Path – From the depth input through pressureCalc, then through safetywatch, and out to the safetywatch output signal Critical Path – From the depth input through pressureCalc, then through safetywatch, and out to the safetywatch output signal Estimated Final Clock Speed 1Hz Estimated Final Clock Speed 1Hz

36. M3: ProDiver 525 Critical Path Layout

37. M3: ProDiver 525 Spice glitch **error**: only 1 connection at node 29:318 **error**: only 1 connection at node 29:318 Correction: a floating unconnected wire in the design Correction: a floating unconnected wire in the design

38. M3: ProDiver 525 Power Consumption Strategy to test power consumption – test the effects of several different power levels on the module in order to find the lowest at which it still works. Strategy to test power consumption – test the effects of several different power levels on the module in order to find the lowest at which it still works. Also, we want to see if making any optimizations to the layout to decrease power consumption Also, we want to see if making any optimizations to the layout to decrease power consumption

39. M3: ProDiver 525 Questions?