Meaning
Memory-mapped dispatch tables hold the initial stack pointers and handler entry addresses for application-level execution in partitioned processors. Under hardware architectures equipped with security extensions, the non-secure vector table defines the exception addresses for non-secure code, distinct from the secure vector table. The table governs entry point resolution for non-secure interrupts and system calls, stopping short of secure fault handling or trusted execution control.
Vector Relocation
Dynamic base register configuration allows system software to position the dispatch table within non-secure random access memory or flash storage. Firmware boot sequences configure the non-secure vector table offset register after secure boot validation finishes. When an unprivileged operating system initiates a task switch or peripheral event, the processor fetches the corresponding entry pointer from this designated table.
Operating systems in cellular IoT terminals frequently relocate the table to RAM to enable fast dynamic patching of peripheral drivers. Memory alignment constraints require the base address to align to powers of two matching the total table size. Hardware rejects unaligned table offsets to prevent unpredictable instruction fetching.
Fault Escalation
Invalid handler addresses located in unprivileged dispatch entries trigger instant fault escalation. If an entry pointer references secure memory space, the hardware security unit intercepts the fetch and generates a secure hard fault. Security compartmentalization remains uncompromised.
Production Audit
Firmware certification requires static and dynamic analysis of dispatch table placement. Test benches verify that the non-secure vector table resides strictly within non-secure memory boundaries before factory imaging. Memory map inspection tools cross-reference link scripts against device allocation tables.
Delivery sign-off requires verified isolation between secure and non-secure exception handlers.