Skip to content

Latest commit

 

History

History
60 lines (46 loc) · 2.21 KB

README.md

File metadata and controls

60 lines (46 loc) · 2.21 KB
Raw

CVRA NIOS 2 Code & libraries

To build on Linux (should work on any UNIX, but not tested) :

cd /path/to/repos/
mkdir build
cd build && cmake ..
make

To build just for a single robot :

make debra
make nastya

Cross compiling for the robot is more complicated, as for now we dont have any standard makefiles to cross compile. For now you should create a blank project in Nios II SBT, and then add all the C files to the build by right clicking them and choosing "Add to NIOS II build...". Then you can add the subfolders of modules to the include path (look in the Makefile for ALT_INCLUDE_DIRS). In the long run we will probably setup our own system to be able to cross compile with nios2-gcc only, without using any other Altera tools.

Organisation of the source code

The source code is organised like this :

nios2
|-- debra
|-- doc
|-- include
|-- modules
|-- nastya
|-- nios_files
|-- tools
  • The debra folder contains all the source specific to our first robot (the one with the arms).
  • The nastya folder contains all the source for our holonomic robot.
  • The include folder contains a few generic includes.
  • The modules folder contains all generic modules and a lot of code taken from Aversive.
  • The tools folder contains various tools for developpers.
  • The nios_files folder contains all the binary files generated by Quartus II from VHDL.

Useful warnings

  • When building for the NIOS 2 system, do not assume that the compiler will zero out memory before giving it to you. It won't.
  • Do not do any rebase / rollback of already pushed commits.
  • The NIOS 2 compiler hates you. Really.

Contributing

If you are from CVRA, ask Antoine to give you commiter access. If you come from an external club (omg a contributor, welcome!), please open a pull request.

In both cases, it is really important that you configure your Mercurial client to have the right user setting. We want your user settings to look like this : FirstName LastName <[email protected]>. The < and the > must be in the username. This is required by Bitbucket to properly match your account to your commits.