We should have a common format for describing tunes (series of beeps) across the different implementations in this repository. Extensive searching was done, a simple widespread standard was not found.

Following is proposed:

1. Simple text file
2. Each line represents a beep or a pause
   1. Column one is a positive integer number of milliseconds
   2. Column two is a positive integer freque

Collect coverage information at end of tests.

https://www.veripool.org/projects/verilator/wiki/Manual-verilator

1. Pass --coverage option to verilator in makefile
2. Modify c++ test harness to VerilatedCov::write into an output file. There will be one file per test, which should be collected somewhere (this probably needs to be done by test_harness.py)
3. Run verilator_coverage executable,

Hi!

The documentation how to flash an application on the hyperflash on the gap8 with openocd seems to be a bit outdated (https://github.com/GreenWaves-Technologies/gap_sdk/tree/master/tools/gap8-openocd-tools).

• tcl_scripts folder doesn't exist (is now /tcl since dev 3.2)
• gap_flasher_ctrl is not there anymore. (should be gap_flash_raw?)
• if the application is made with make all, there