ECEN 390 - Laser Tag Project

The ZED board does no active processing of signal data in this milestone. For this milestone the ZED board acquires signal data from the A/D and copies it to the D/A. It must do this 100,000 times per second (1kHz). The timing must be precise. You must ensure that the A/D is sampled at 100 kHz and that the D/A generates data at that same rate. We didn't build a sampled-data system in ECEN 330 but you should have all of the necessary tools to achieve this milestone. Here is how to go about accomplishing the software part of this milestone.

1. A/D and D/A PMods . The A/D and D/A devices are mounted on PMods, small boards that connect to the black connectors located on the periphery of the ZED board. To keep things simple, let's use exactly the same pin assignments for these modules as was used in ECEN 330. That way, you don't need to learn how to use Xilinx Platform Studio for now. This also means that you can simply use the same bit-stream as you used in ECEN 330. We can change these pin assignments later if necessary. This means that you will use the same cables that connecting these A/D and D/A PMods in ECEN 330. In your ZED kit, you will find that the D/A and A/D PMods are attached to a single cable. Plug the other end of this cable into JA1 of the ZED board as shown in the accompanying photo. Ignore the cable attached to JB1 shown in the figure.

1. Go to digilentinc.com and find the schematics for the PMods you are using. You will need this information so that you can connect the analog inputs and outputs to the PMods. WATCH THE VOLTAGE RANGE FOR THE SIGNAL THAT YOU SEND TO THE A/D. DO NOT EXCEED THE SPECIFICATION LISTED IN THE MILESTONE DESCRIPTION.
2. Configure the timer interrupt so that it fires at the 100 kHz rate on the ZYNQ processor on the ZED board.
3. Write a state machine that acquires data from the A/D and another state machine that pushes that data to the D/A. It might make sense to use a shared variable here (hint, hint). You can use a task scheduler but you don't have to for this lab.
4. Determine how much jitter (if any) that the resulting system has.