zephyr/samples/nanokernel/test/test_static_idt
Sergio Rodriguez 2e2ad8166e qemu: Creation of QEMU specific platforms
Setting up new platforms to handle emulation, and make them the only
ones able to run on QEMU from the Makefile "qemu" target to avoid
confusion with other platforms. We have now platform qemu_x86 and
platform qemu_cortex_m3, also modification to the sanity checks to have
qemu support only on those platforms

Signed-off-by: Sergio Rodriguez <sergio.sf.rodriguez@intel.com>
Change-Id: I9291918a1d58fea4f37750ada78234628f9a5d98
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-02-05 20:24:56 -05:00
..
Makefile qemu: Creation of QEMU specific platforms 2016-02-05 20:24:56 -05:00
README.txt
prj_x86.conf samples: disable exception debug for test_static_idt 2016-02-05 20:24:29 -05:00
testcase.ini samples: use arch_whitelist instead of config_whitelest 2016-02-05 20:24:28 -05:00

README.txt

Title: Static IDT Support

Description:

This test verifies that the static IDT feature operates as expected in a
nanokernel environment.

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

Building and Running Project:

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

    make qemu

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

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

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

Sample Output:

tc_start() - Test Nanokernel 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 exception/interrupt occurred! *****
Current context ID = 0x00102a68
Faulting instruction address = 0x00102c50
Fatal fiber error! Aborting fiber.
PASS - main.
===================================================================
PROJECT EXECUTION SUCCESSFUL