Common part in it's own project -> PTS (single project scheme).
Specific test in a sub-project of the board.
-> Automate installation as much as possible -> install
Store testing log files in MTF (CERN specific).
-> Note: A log file must correspond to a serial number (barcode).
Wiki page "How to batch upload files in MTF" (CERN specific).
Write a unique, platform independent
API for testing the
-> single r/w, block r/w, wait irq, sdb, fmc eeprom, flasher
-> C lib + python wrapper
-> part of the fmc-bus?
-> raw backend with direct memory mapped access => for non-fmc
Get rid of rawrabbit/gnurabbit.
-> Requires a replacement first (cf. block read/write support in
About releases (To be discussed)
min/maj (v3.2) or date-based (v02.2014) -> sdb is not foreseen for
wiki release pages
md5sum of binaries
changelog only in one place
automate page creation (Would be nice to have),
to be investigated...
package releases (pcb+hdl+sw ?+test?)
zip/tar of sources+binaries?
non-ohwr projects (CERN specific)
Use official cern git repos.
Page on wikis.cern.ch as the central info point.
One JIRA space per board to gather issues.
-> Issues summary in the wiki.
Official/operational gateware release location is on nfs:
Binary files location: nfs (operational), wiki (public)
Write a "how to migrate a svn repo to git" wiki page.
Update wiki page template.
-> Issues summary
Matthieu Cattin, Erik van der Bij - August 2014
Automatically gathers issues from sub-projects.
Gateware (HDL design) for xx.
Hardware design of xx.
Includes schematics, PCB layout and manufacturing files.
Software to support the xx, including Linux device driver, library
and test program.