rusefi
/
rusefi
mirror of https://github.com/rusefi/rusefi.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs

This commit is contained in:
rusEfi 2017-04-21 19:05:02 -04:00
parent bf172e65ff
commit 3229924e5e
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
firmware/config/engines/mazda_miata_vvt.cpp
View File

@ -17,6 +17,7 @@
* *
* Crank primary trigger PA5 (3E in Miata board) white * Crank primary trigger PA5 (3E in Miata board) white
* Cam vvt input PC6 (3G in Miata board) blue * Cam vvt input PC6 (3G in Miata board) blue
* Wideband input PA3 (3J in Miata board)
* *
* coil1/4 (p1 +5 VP) PE14 * coil1/4 (p1 +5 VP) PE14
* coil2/2 (p1 +5 VP) PC7 * coil2/2 (p1 +5 VP) PC7
@ -27,6 +28,7 @@
* *
* VVT solenoid on aux PID#1 PE3 * VVT solenoid on aux PID#1 PE3
* *
*
*/ */
#include "mazda_miata_vvt.h" #include "mazda_miata_vvt.h"

9
unit_tests/readme.txt
View File

@ -1,6 +1,7 @@
In this folder we have a naive test set. I am not sure what is the best approach to tests in C (someone can educate me), but my approach is: In this folder we have a naive test suite.
1) with a symlink linking some (only some, not all) folders of the firmware implementation, we can compile some files of the firmware as win32 code. I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:
Please execute the 'makelinks.bat' file to get the links. On XP you might need to execute 'junction.exe' before exuting the .bat file.
2) we then compile & run the .exe, which is expected to say SUCCESS and not fail :) Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU.
Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :)