Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • REF
  • OVER FIBER
  • OVER JTAG (joint test action group) (USING QUADS AS NORMALLY DONE THIS WAY)

    • Ref
    • Difference are: eProms and firmware image
    • Cloning repo
      • $ cd ~/IC_projects/ 
      • $ git clone --recursive git@github.com:slaclab/epix-quad

    • Does not mater if fiber or sensor is plugged in, working under assumption it is bare board

    • In the case of the Quad, can power digital board by itself
    • Power on the board–wait till current stabilizes 
    • $ cd epix-quad/firmware/
    • $ source setup_env.sh
      • Sets up Vivado – dev env for Xlinks (full integrated dev env)
    • $ vivado &
    • In Vivado
    • Flow → Hardware Manger
    • Image Removed
    • Auto Connect
      • Should see a green light on the Xilnx box
    • What it found as connected device
      • Image Removed
    • Image Removed
      • Program Device... → Specifies the bit file for programing the FPGA ← can just be doing this one only
        • volitile program, so will need to reprogram after powercycle
      • Configuration... → Specifies the ePROM that your writing the image too
        • So don't have to reprogram after power cycle
    • FLOW FOR ePROM → Select ADD Configuration Memory Device...
    • Image Removed
    • Image Removed
    • Search
    • TypeSearchSinglemt25ql256QuadS25FL512
    • Image Removed
    • Look in target/<what ever device and rate>/image/<some mcs file>
    • MAKE SURE YOU HAVE IMAGE FILES *.mcs in /firmware/.../image/*.mcs
    • Image Removed
    • Image RemovedInstalling firmware via JTAG (Slower... more involved...)