OVER JTAG (joint test action group) (USING QUADS AS NORMALLY DONE THIS WAY)
- Ref
- ePix Generation 2 bring up and testing
- Line 5 has eProms
- Quad bring-up and testing (pgp3)
- Line 7 has eProms
- ePix Generation 2 bring up and testing
- 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
- Auto Connect
- Should see a green light on the Xilnx box
- What it found as connected device
- 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
- Program Device... → Specifies the bit file for programing the FPGA ← can just be doing this one only
- FLOW FOR ePROM → Select ADD Configuration Memory Device...
- Search...
Type Searcj Single mt25ql256 Quad S25FL512
- Look in target/<what ever device and rate>/image/<some mcs file>
- MAKE SURE YOU HAVE IMAGE FILES *.mcs in /firmware/.../image/*.mcs
- Flow → Hardware Manger