OpenCores
URL https://opencores.org/ocsvn/mips32r1/mips32r1/trunk

Subversion Repositories mips32r1

[/] [mips32r1/] [trunk/] [Hardware/] [XUPV5-LX110T_SoC/] [HOWTO] - Diff between revs 8 and 12

Show entire file | Details | Blame | View Log

Rev 8 Rev 12
Line 13... Line 13...
 
 
    2. Open the project file "MIPS32-Pipelined-Hw.xise" located in the
    2. Open the project file "MIPS32-Pipelined-Hw.xise" located in the
       "Hardware/XUPV5-LX110T_SoC/MIPS32-Pipelined-Hw" directory. This is
       "Hardware/XUPV5-LX110T_SoC/MIPS32-Pipelined-Hw" directory. This is
       a Xilinx ISE 14.1 project file.
       a Xilinx ISE 14.1 project file.
 
 
    3. Build the hardware project and generate the programming .bit file.
    3. Build the Block RAM core by using the Block Memory Generator in
 
       the Core Generator. See details below.
 
 
 
    4. Build the hardware project and generate the programming .bit file.
       Send the programming file to the board through Impact (you may need
       Send the programming file to the board through Impact (you may need
       to create a new Impact project file for your system, but no options
       to create a new Impact project file for your system, but no options
       are needed other than the configuration .bit file targeted for the
       are needed other than the configuration .bit file targeted for the
       Virtex-5 device). A default program built into the BRAM will print
       Virtex-5 device). A default program built into the BRAM will print
       a hello message to the LCD screen.
       a hello message to the LCD screen.
 
 
       Alternatively, a pre-built .bit file is located in the
       Alternatively, a pre-built .bit file is located in the
       "Hardware/XUPV5-LX110T_SoC" directory.
       "Hardware/XUPV5-LX110T_SoC" directory. It is timed conservatively
 
       at 33 MHz (66 MHz bus).
 
 
    4. Compile any of the software demos located in "Software/demos" using
    5. Compile any of the software demos located in "Software/demos" using
       the Makefile included with the demo. One of the output files from
       the Makefile included with the demo. One of the output files from
       the compilation will have a .xum extension. This is a binary file that
       the compilation will have a .xum extension. This is a binary file that
       contains the code and data for the program. Use the XUM Bootloader
       contains the code and data for the program. Use the XUM Bootloader
       software (Windows) to send the .xum file over a serial port to the
       software (Windows) to send the .xum file over a serial port to the
       FPGA. When the program is sent, the CPU will reset and run it.
       FPGA. When the program is sent, the CPU will reset and run it.
 
 
Rebuilding the Block RAM
Rebuilding the Block RAM
------------------------
------------------------
    If you need to recreate the Block RAM core for any reason, the following
    The following settings will allow you to build the Block RAM module
    settings will allow you to do it (assuming Xilinx Block Memory Generator
    and add a default program to it assuming Xilinx Block Memory Generator
    version 7.1): True Dual Port RAM, Common Clock, Byte Write Enable of 8
    version 7.1): True Dual Port RAM, Common Clock, Byte Write Enable of 8
    bits, Write/Read width of 32 bits, Write depth of 151552 (for full
    bits, Write/Read width of 32 bits, Write depth of 151552 (for full
    592 KB), Always Enabled, same options for port B, Register Port A Output
    592 KB), Always Enabled, same options for port B, Register Port A Output
    of Memory Primitives AND Memory Core (for 2R version, this can be
    of Memory Primitives AND Memory Core (for 2R version, this can be
    customized), same settings for Port B, fill remaining locations with
    customized), same settings for Port B, fill remaining locations with

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.