A Day in the LIfe of a Programmer/Analyst

Tuesday, June 26, 2012

WARP Project: Getting DC Offsets of WARP Radios

This is the workflow for downloading Rice University's WARP board bitstream for calculating DC offsets in their board's radios.  The workflow should be identical for the Virtex II board, but here are the steps known to work for the Virtex4 board.

Hyper Terminal 
  1. Connect the WARP board to the host computer via a comm cable.
  2. Open Hyper Terminal.
  3. Give it some name under the "Name" form.  You can assign it an icon as well.  If you don't care to save this connection, just give it any name with any icon. Click "OK."
  4. In the next dialog, select "COM1" next to the "Connect Using" (or whatever comm port you're using to connect to the board).  Click "OK."
  5. In the COM1 Properties box, select 57600 Bits per second, 8 Data bits, None Parity, 1 Stop bits, and None for Flow Control (the only things to change from default should be the "Bits per second" and "Flow control" settings).  Click "OK."
Hyper Terminal should be up and running, ready for any output the .bit file should produce.  Proceed on to the iMPACT section for the rest.



iMPACT 
  1. Download bitstream for Virtex-4 based boards.
  2. Rename the bitstream download.bit.
  3. Open iMpact (start->All Programs->XilinxISE Design Suite 10.1->ISE->Accessories->iMpact).
  4. Select "create a new project (.ipf)" at the iMACT Project dialog box.  Click "OK."
  5. Select "Configure devices using Boundary-Scan (JTAG) in the next window.  Click "Finish."
  6. The next dialog that pops up requests a configuration file for the Xilinx block.  Click "Bypass."
  7. The next dialog that pops up requests a configuration file for the Vitex-4 chip.  Open your download.bit bitstream.
  8. Click "OK" in the Add Virtex-/II Pro/Virtex4 Object Files dialog (there are no "BMM" or "Power PC Software Files" needed).
  9. Select the device corresponding to your Virtex chip under "Boundary Scan" in the Device Programming Properties dialog.  Click "OK."
  10. Right-click the box that corresponds to your Virtex chip and select "Program."

You should see a blue form that says "Program Succeeded." If everything went smoothly.

NOTE 1: If the Programming Properties dialog opens after you select "Program" in step 11), you screwed up step 10) by not selecting your Virtex chip.  Select it now in this dialog box and click "OK."  Try not to screw up in the future.  It makes you feel stupid.

If everything went correctly, Hyper Terminal should be displaying "WARP Radio Calibration - Main Menu."
  1. Select the radio to test.  In our specific case, the only radios connected are radios 2 and 3.  Radios 1 and 4 are absent.
  2. Select 2 for Tx DC Offset Calibration.
  3. Select "q" to return to the main menu and select another radio to test.
NOTE 2: It's a good idea to test each radio a couple of times, just to make sure you didn't get a sample of data that was far off of what the actual Tx DC offset is.

NOTE 3: In the case of testing absent radios, usually "Best I" and "Best Q" will display nonsensically high or low values, like +/-200.  "Normal" values would be something within the range of +/-100.

For the project at hand, these values are needed in exd_hostname.h under the exa_d2d_lib directory.










Monday, June 25, 2012

SIO Project: Pre-Setup.

One project at hand comes from the Scripps Institution of Oceanography

The guys there are building some kind of laser system that can take depth/distance measurements under water optically, and attached to a UUV.  The details of this part are not important.

The project comes in three phases, the earlier of the two being handled by my coworker.  They would like him to design a data acquisition class in C++ built for a piece of Innovative Integration hardware, the X5-G12.  The details of this part don't really concern me either.  They would just like to sample data to determine distance/depth based on some delays.

I am responsible for phase 3, the hardware programming side.  After the data acquisition class is designed, they will run tests, and get back to me with some optimizations that can take place inside the hardware so that more data can be sampled, given the existing class and hardware restrictions.  This will probably be something like compression and filtering.  The X5-G12 board comes equipped with a Virtex5 (SX95T) FPGA (FAQ, data).  I have decided to stick to a workflow that involves MATLAB and System Generator for the design of the project, as I have no experience in any HDL.


As of now, we are still waiting for the SIO guys to provide a development machine equipped with the software and licenses for us (rather, myself) to begin design.


However, I have been playing with the Xilinx software, and getting everything running together nicely.


Some software requirements:
 
    Innovative Integration Requirements:
        - Windows XP pro / Windows 7
        - Xilinx ISE 12.3
             (More info here)
        - MATLAB R2009a or R2009b (UCSD will provide this)
        - I think ModelSim is an optional piece of hardware, aimed more
            the VHDL developer.

    Xilinx ISE 12.3 Requirements:
        - I can't really find specifics

    Xilinx System Generator Requirements:
        - Windows XP / Windows Vista (I'm sure it supports Windows 7)
        - Xilinx ISE Design Suite 12.3 Logic Edition
        - MATLAB R2009b R2010a, beta support for R2010b

     Innovative Integration Software:
        - An Intel based CPU
        - Windows 2000 or Windows XP

Highlighted in bold is software that seems to be required by all the other software.  The development machine being provided will follow all of these guidelines except the operating system.  It will have Windows 7 Pro 64-bit on it, while the OS dictated by the Innovative Integration software requirements is 2000 or XP.  I guess I'll roll the dice on this, but if this is a setback, this blog will be the only one who knew of my negligence to inform everyone.

I am currently waiting for UCSD to provide access to MATLAB archives so that I can acquire R2009b, as it is the only supported MATLAB platform between all of the other software.  Windows 7 should do the trick for everything, although the 64 bit version might add problems.  Xilinx ISE 12.3 offers a 30 day trial license that I keep renewing without penalty (o_O) and the MATLAB BSP (board support package) provided by Innovative comes along with all of their other software offered by the online downloader.

Friday goal:
    Innovative provides some harware examples that can be co-simulated on the X5-G12 board.  I would like to have something running on the board by Friday.  I would like it to be a modification of something they provide, like if I added a lowpass filter or something.  Either way, I would like to co-simulated something on Friday.

    This will greatly depend on how much time I spend on this particular project (on paper, I shouldn't be spending any time yet, as I am to spend 100% of my time on an Ericsson project ongoing at the moment as well), and also how fast UCSD gets the compatible version of MATLAB available for download.

A Day In the Life of a Programmer Analyst

This is a bookmark, posted on 6/25/12.  I would like to keep a small diary of sorts, if not for my own reference, that will include all ongoing and future projects.  Maybe I'll post little tidbits here accomplishing basic tasks so I can reference them, maybe I'll post details on large projects, I guess we'll see.