Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
NanoSoC Tech
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SoCLabs
NanoSoC Tech
Commits
188d6660
Commit
188d6660
authored
5 months ago
by
Daniel Newbrook
Browse files
Options
Downloads
Patches
Plain Diff
Update docs for EXP Sram preload
parent
3bd655ad
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
doc/nanosoc_configuration_manual.pdf
+0
-0
0 additions, 0 deletions
doc/nanosoc_configuration_manual.pdf
doc/nanosoc_datasheet.pdf
+0
-0
0 additions, 0 deletions
doc/nanosoc_datasheet.pdf
doc/tex/nanosoc_configuration_manual.tex
+13
-0
13 additions, 0 deletions
doc/tex/nanosoc_configuration_manual.tex
with
13 additions
and
0 deletions
doc/nanosoc_configuration_manual.pdf
+
0
−
0
View file @
188d6660
No preview for this file type
This diff is collapsed.
Click to expand it.
doc/nanosoc_datasheet.pdf
+
0
−
0
View file @
188d6660
No preview for this file type
This diff is collapsed.
Click to expand it.
doc/tex/nanosoc_configuration_manual.tex
+
13
−
0
View file @
188d6660
...
@@ -220,6 +220,7 @@ To add your own testcodes to run on nanosoc in the simulation environment, you c
...
@@ -220,6 +220,7 @@ To add your own testcodes to run on nanosoc in the simulation environment, you c
\item
Copy the makefile from one of the example testcodes to your test code directory
\item
Copy the makefile from one of the example testcodes to your test code directory
\item
Edit the TESTNAME variable in the new makefile to the name of your test
\item
Edit the TESTNAME variable in the new makefile to the name of your test
\item
If you want to run any ADP code before your test, add an adp.cmp file (example in the adp
\_
v4
\_
cmd
\_
tests)
\item
If you want to run any ADP code before your test, add an adp.cmp file (example in the adp
\_
v4
\_
cmd
\_
tests)
\item
If you want to preload expansion memories, add an expram
\_
l.hex and/or expram
\_
h.hex
\item
Add the name of your test to the accelerator-project/system/software
\_
list.txt file
\item
Add the name of your test to the accelerator-project/system/software
\_
list.txt file
\end{enumerate}
\end{enumerate}
...
@@ -252,6 +253,18 @@ For more detailed C code templates, please see the firmware in the
...
@@ -252,6 +253,18 @@ For more detailed C code templates, please see the firmware in the
accelerator-project/nanosoc
\_
tech/software/common/validation.
accelerator-project/nanosoc
\_
tech/software/common/validation.
These are also the testcodes used for validating nanoSoC.
These are also the testcodes used for validating nanoSoC.
\subsection
{
Preloading expansion memories
}
You may want to load test vectors directly into the expansion memories to run your tests. Doing this can save space in the
instruction memory space as you then don't have to load data in as arrays or vectors in your testcode. Instead you can use the simulator
to automatically load these memories at the start of simulation.
To do this, simply add an "expram
\_
l.hex" file and/or "expram
\_
h.hex" file to your testcode directory. These files will then
be loaded to the EXPRAM
\_
L or EXPRAM
\_
H region repectively. These can then be addressed in your testcode from 0x80000000 for EXPRAM
\_
L
and 0x90000000 for EXPRAM
\_
H.
The expram
\_
l.hex files must be ASCII text files with a single byte per line. They will look very similar to the .hex files that are used
to preload the instruction memory.
\chapter
{
FPGA Flow
}
\chapter
{
FPGA Flow
}
\section
{
Summary
}
\section
{
Summary
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment