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

Update README.md

This commit is contained in:
killinen 2023-01-07 07:06:43 +02:00 committed by GitHub
parent 5675a8f402
commit 2a5aa5d98f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Safety/README.md
View File

@ -4,9 +4,7 @@ In critical systems, it is important to adhere to the principle of rigorous code
Cppcheck is a static analysis tool for C/C++ code that is designed to detect bugs and undefined behavior. It has been used to check the BrakeModule code for any issues. Cppcheck is a static analysis tool for C/C++ code that is designed to detect bugs and undefined behavior. It has been used to check the BrakeModule code for any issues.
The Misra addon is a layer on top of Cppcheck that performs rule checking according to the MISRA-C:2012 standard. The Misra addon is a layer on top of Cppcheck that performs rule checking according to the MISRA-C:2012 standard. The BrakeModule code has passed the Cppcheck test and is currently being checked for MISRA compliance. MISRA violations can be seen on misra/misra_violations_output.txt. For making those tests there is shell script code_tests.sh in misra folder.
<!---The BrakeModule code has passed the Cppcheck test and is currently being checked for MISRA compliance.--->
A shell script is available in the BrakeModule software folder to run both tests.
During compilation, the ```-warnings=all``` flag is also set to highlight any potential problems. During compilation, the ```-warnings=all``` flag is also set to highlight any potential problems.
@ -16,8 +14,14 @@ The BrakeModule aims to minimize the impact on the original ABS/DSC system's fun
TODO: Conduct a systematic analysis of logic or component failures and their effect on the BrakeModule and the rest of the system. TODO: Conduct a systematic analysis of logic or component failures and their effect on the BrakeModule and the rest of the system.
### Software design ### Software design
Here text what safety has tried to be implemented in software Some of the funtional safety stuff that has been implemented in software:
- STM32F1 internal temperature monitoring and and OP disengaged if temperature above certain threshold.
- POWER MOSFET temperature monitoring and and OP disengaged if temperature above certain threshold.
- Check for freezed ADC values.
- IDWG for restarting the program if chip freezes.
- CAN bus failure detection.
- Check that OP related CAN BUS msg is present in the BUS.
- Lock pin configuration after initialization.
### Hardware design ### Hardware design
Here text what safety has tried to be implemented in hardware Here text what safety has tried to be implemented in hardware