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

Subversion Repositories neorv32

[/] [neorv32/] [trunk/] [docs/] [userguide/] [content.adoc] - Diff between revs 66 and 68

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 66 Rev 68
Line 145... Line 145...
. Create a new project with your FPGA EDA tool of choice.
. Create a new project with your FPGA EDA tool of choice.
. Add all VHDL files from the project's `rtl/core` folder to your project.
. Add all VHDL files from the project's `rtl/core` folder to your project.
 
 
.Internal Memories
.Internal Memories
[IMPORTANT]
[IMPORTANT]
For a _general_ first setup (technology-independent) use the _default_ memory architectures for the internal memories
For a _general_ first setup (technology-independent) use the `*.default.vhd` memory architectures for the internal memories
(IMEM and DMEM). These are located in `rtl/core/mem`, so **make sure to add the files from `rtl/core/mem` to your project, too**. +
(IMEM and DMEM). These are located in `rtl/core/mem` so make sure to add the files to your project, too. +
 +
 +
If synthesis cannot efficiently map those default memory descriptions to the available memory resources, you can later replace the
If synthesis cannot efficiently map those default memory descriptions to the available memory resources, you can later replace the
default memory architectures by optimized platform-specific memory architectures. **Example:** The `setups/radiant/UPduino_v3`
default memory architectures by optimized platform-specific memory architectures. **Example:** The `setups/radiant/UPduino_v3`
example setup uses optimized memory primitives. Hence, it does not include the default memory architectures from
example setup uses optimized memory primitives. Hence, it does not include the default memory architectures from
`rtl/core/mem` as these are replaced by device-specific implementations. However, it still has to include the entity
`rtl/core/mem` as these are replaced by device-specific implementations. However, it still has to include the entity
Line 378... Line 378...
Section <<_installing_an_executable_directly_into_memory>> shows how to
Section <<_installing_an_executable_directly_into_memory>> shows how to
run custom programs on your FPGA setup without having a UART.
run custom programs on your FPGA setup without having a UART.
 
 
[start=1]
[start=1]
. Connect the primary UART (UART0) interface of your FPGA board to a serial port of your host computer.
. Connect the primary UART (UART0) interface of your FPGA board to a serial port of your host computer.
. Start a terminal program. In this tutorial, I am using TeraTerm for Windows. You can download it fore free
. Start a terminal program. In this tutorial, I am using TeraTerm for Windows. You can download it for free
from https://ttssh2.osdn.jp/index.html.en
from https://ttssh2.osdn.jp/index.html.en . On Linux you could use GTKTerm, which you can get here
 
https://github.com/Jeija/gtkterm.git (or install via your package manager).
 
 
 
 
[NOTE]
[NOTE]
_Any_ terminal program that can connect to a serial port should work. However, make sure the program
_Any_ terminal program that can connect to a serial port should work. However, make sure the program
can transfer data in _raw_ byte mode without any protocol overhead around it.
can transfer data in _raw_ byte mode without any protocol overhead around it.
 
 

powered by: WebSVN 2.1.0

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