zephyr

History

Torsten Rasmussen 407b49b35c cmake: use find_package to locate Zephyr Using find_package to locate Zephyr. Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate code. Whenever an automatic run of CMake happend by the build system / IDE then it was required that ZEPHYR_BASE was defined. Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to cache the base variable and thus allowing subsequent invocation even if ZEPHYR_BASE is not set in the environment. It also removes the risk of strange build results if a user switchs between different Zephyr based project folders and forgetting to reset ZEPHYR_BASE before running ninja / make. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>		2020-03-27 16:23:46 +01:00
..
src	…
CMakeLists.txt	cmake: use find_package to locate Zephyr	2020-03-27 16:23:46 +01:00
README.txt	…
prj.conf	…
testcase.yaml	test: static_idt: skip for 64-bit	2020-02-06 23:07:37 -05:00

README.txt

Title: Static IDT Support

Description:

This test verifies that the static IDT feature operates as expected.

--------------------------------------------------------------------------------

Building and Running Project:

This project outputs to the console.  It can be built and executed
on QEMU as follows:

    make run


Sample Output:

tc_start() - Starting static IDT tests
Testing to see if IDT has address of test stubs()
Testing to see interrupt handler executes properly
Testing to see exception handler executes properly
Testing to see spurious handler executes properly
- Expect to see unhandled interrupt/exception message
***** Unhandled interrupt vector *****
Current thread ID = 0x001028e0
Faulting segment:address = 0x8:0x1001c9
eax: 0xa, ebx: 0x0, ecx: 0x1018e0, edx: 0xa
esi: 0x0, edi: 0x0, ebp: 01030b4, esp: 0x1030b4
eflags: 0x202
Fatal fault in thread 0x001028e0! Aborting.
PASS - main.
===================================================================
PROJECT EXECUTION SUCCESSFUL