Skip to content
Snippets Groups Projects
Commit e8d1e10c authored by antoo98's avatar antoo98
Browse files

Cleanup of internal/personal/outdated files

parent ea535349
No related branches found
No related tags found
No related merge requests found
......@@ -40,7 +40,7 @@ Here is a small overview about our repository structure, to brief which files yo
- _tools/_ - external tools needed for this project, i. e. the CD contents from our development board
- _wiki/_ - wiki for further documentation, i. e. Sancus architecture overview, Sancus repositories overview, ...
- _wiki/_ - not used, contains only a link list to documentation documents in the main repository)
## Installing the toolchain
......@@ -48,18 +48,4 @@ For ArchLinux see [build_documentation_arch.md](Repos/build_documentation_arch.m
## Links
* [Sancus](https://distrinet.cs.kuleuven.be/software/sancus/ "KU Leuven Sancus")
## TODO for README.md / Wiki
- [X] introduction sentences for this README.md / Repo
- [X] own repo structure/overview in wiki or README.md
- [X] reference from README.md to docker/README.md at docker installation section
- [X] update (or remove) 'from source' section from README.md (reference to Repos/README.md or Wiki or so..)
- [X] wiki: installation from source and docker
- [X] docker readme: further documentation on the hello-world example project
- [X] indicate what was written by you and what is taken 1:1 from other sources (e.g. /Repos/overview.md?)
- [X] move 'source' subsection from the 'from source' section to end of this file and list all external sources
- [ ] TODO list in wiki/main.md
* [Sancus Website](https://distrinet.cs.kuleuven.be/software/sancus/ "KU Leuven Sancus")
Mail to OpenMSP430:
lvd.mhm@gmail.com
This is OpenMSP430 core+peripherals implementation adapted for Altera DE1 board.
It is based on original Olivier's adaptation for Diligent S3 board, but has following distinctions:
1. Fixed 7segment core, since DE1 has non-muxed digits.
2. It is adapted for MegaWizard-generated 16-bit wide on-chip ROMs and RAMs.
3. Debug ROM write is removed (although it shouldn't be a problem to return it back).
Anyway I haven't used any debug features.
4. As an alternative to the embedded synchronous RAM, there is ext_de1_sram module that
allows core to access external on-board static RAM.
5. Core is configured to have non-standard ROM and RAM sizes (4kB and 1kB), so make
sure the OpenMSP430_defines.v file is properly updated
6. There is new software project that uses custom linker script to compile for non-standard
ROM and RAM sizes.
Hey,
for an academic software project we want to implement the OpenMSP430 on the Cyclone V FPGA.
We are currently working with the Altera DE10 Standard board instead of the older Altera DE1.
We noticed in your repository that the Altera DE1 board was marked as obselete.
Why did you mark this board as obsolete? Is it just the reason that there are newer revisions of this board available?
Now we're at the point to implement the OpenMSP430 architecture onto the Cyclone V FPGA and already worked on adjusting the local assignments.
Can you provide us any tips on how to proceed and on how we have to further adjust the openMsp verilog files?
We already compared the different boards that you provided in the repo, but it is difficult for us to comprehend the changes that you made.
And in case that we'd manage to get the architecture working, we were wondering whether you would be interested in including our DE10 implementations in your repository?
=============================================================================================================
Issue to Sancus developer on:
https://github.com/sancus-pma/sancus-core/issues/16
Hey,
for an academic software project we want to implement Sancus on the Cyclone V FPGA.
We are working with the Altera DE10 Standard board instead of the older Altera DE1 that you've already provided in your repository.
At the OpenMSP430 github repository, we noticed that the DE1 board is moved to obsolete directory.
Now we're at the point to implement the OpenMSP430 architecture onto the Cyclone V FPGA and already worked on adjusting the local assignments.
Here comes the question: Are you also working on the implementation of the Sancus architecture on
the Altera DE10 Standard board? If so, there is no need for doing redundant parallel work and we'd prefer to support you instead and maybe continue from your current status.
If not: Would you be interested in including our DE10 results in your repository, if we'd manage to get the architecture working?
We've also contacted the OpenMSP430 developers for including the Altera DE10 in their repository.
Apart from that, we would also like to know whether you have any older documentation which you used when you started creating the example project for the different boards, or if there might be anything that is not provided in the repository that we need.
# Quartus rant
* 1 Build => 20 files + 2 directories in main project directory
* Unterschiedliche Tastenkombinationen für jedes Tool
* Platform Designer/ Qsys kann zwar komponenten generieren und vernetzen, Einbinden von bestehendem ist aber nicht gelungen
* IP Catalog (anscheinend früher MegaFunction Wizard) kann manche komponenten generieren (RAM/ROM), andere nicht
* Tools: 33 different tools, no centralized documentation
* No file hirarchy view in Quartus (only _Hierarchy_ which shows modules included in our main module, but most was outside)
*
## Folien
* Sancus (Alpha)
* Milestones ohne Farben (Anton)
* Unsere Arbeit: Sancus (Alpha)
* Unsere Arbeit: Openmsp
- Unsere Anpassungen (Elena)
- Repo (Anton)
* Milestones mit Farben (nur kurz einfärben)
* Difficulties (Anton)
* Lessons Learned (Elena)
* Nutzen unsere Arbeit (Elena)
# Collection of questions to the Sancus team
* Running Sancus on Cyclone 5/ Altera DE10-Standard board
* Documentation of changes to OpenMSP430?
*
# Email draft
Dear Jan Tobias Mühlberg,
as part of our software project at Freie Universiät Berlin we are trying to run
Sancus on an Altera DE10-Standard board, equipped with a Cyclone V FPGA.
Do you have any experience on using this board/ fpga with Sancus?
While reading the modified OpenMSP430 Verilog files, we've had some difficulties
understanding everything that's going on. Is there any documentation on the
changes you have made to the processor? In your repositories we couldn't really
find any, unfortunately.
Subproject commit b3b603219dfcbcb281789b49defbcfd4dda516d6
Subproject commit ccaebb09e3f101f3b94704ac176543cc5004dfc0
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment