zephyr

History

Anas Nashif 0ec3774bde userspace: rename _is_user_context -> k_is_user_context This functions is being called across the tree, no reason why it should not be a public API. The current usage violates a few MISRA rules. Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2021-04-01 05:34:17 -04:00
..
src	userspace: rename _is_user_context -> k_is_user_context	2021-04-01 05:34:17 -04:00
CMakeLists.txt	edac: Add error data information to callback parameter	2021-01-21 08:34:07 -05:00
README.rst	edac: ibecc: Add testing README	2021-03-24 05:43:17 -04:00
prj.conf	…
testcase.yaml	tests: edac: Add test for user thread communication	2021-02-19 16:06:29 +02:00

README.rst

.. _edac_ibecc_tests:

Testing Error Detection and Correction
######################################
Tests verify API and use error injection method to inject
errors.

Prerequisites
*************
IBECC should be enabled in BIOS. This is usually enabled in the default
BIOS configuration. Verify following:
Intel Advanced Menu -> Memory Configuration -> In-Band ECC ->  <Enabled>.
Verify also operational mode with:
Intel Advanced Menu -> Memory Configuration -> In-Band ECC Operation Mode -> 2

For injection test Error Injection should be enabled.

Error Injection
===============
IBECC includes a feature to ease the verification effort such as Error
Injection capability. This helps to test the error checking, logging and
reporting mechanism within IBECC.

In order to use Error Injection user need to use BIOS Boot Guard 0 profile.

Additionally Error Injection need to be enabled in the following BIOS menu:
Intel Advanced Menu -> Memory Configuration -> In-Band ECC Error -> <Enabled>.

Configurations
**************
Due to high security risk Error Injection capability should not be
enabled for production. Due to this reason test has production configuration
and debug configuration. The main difference is that debug configuration
includes Error Injection.