#define FIRST_PAGE_ADDR 0x10000
#define NVIC_VectTab_FLASH           (0x00000000)

// код вызова приложения

volatile unsigned long    *p = (volatile unsigned long*)NVIC_VECT_TABLE;
*p = NVIC_VectTab_FLASH | (USER_FLASH_START & 0x1FFFFF80);

void (*App)() =  (void(*)())(FIRST_PAGE_ADDR + 1);
App();            // уходим в прикладную программу

void execute_user_code(void)
{
    void (*user_code_entry)(void);
    
    /* Change the Vector Table to the USER_FLASH_START
    in case the user application uses interrupts */
    NVIC_SetVectorTable(NVIC_VectTab_FLASH, USER_FLASH_START);

      user_code_entry = (void (*)(void))((USER_FLASH_START)+1);
    user_code_entry();

}

        EXTERN  __iar_program_start
        PUBLIC  __vector_table
        PUBLIC  __vector_table_0x1c

        DATA
__vector_table
        DCD     sfe(CSTACK)            ; Top of Stack
        DCD     __iar_program_start    ; Reset Handler
        DCD     NMI_Handler            ; NMI Handler
        DCD     HardFault_Handler         ; Hard Fault Handler
        DCD     MemManage_Handler         ; MPU Fault Handler
        DCD     BusFault_Handler          ; Bus Fault Handler
        DCD     UsageFault_Handler        ; Usage Fault Handler
__vector_table_0x1c
        DCD     0                         ; Reserved
        DCD     0                         ; Reserved
        DCD     0                         ; Reserved
        DCD     0                         ; Reserved
        DCD     SVC_Handler            ; SVCall Handler
        DCD     DebugMon_Handler          ; Debug Monitor Handler
        DCD     0                         ; Reserved
        DCD     PendSV_Handler            ; PendSV Handler
        DCD     SysTick_Handler        ; SysTick Handler
        DCD     WDT_IRQHandler            ; Watchdog Handler
        DCD     TMR0_IRQHandler        ; TIMER0 Handler
        DCD     TMR1_IRQHandler        ; TIMER1 Handler
        DCD     TMR2_IRQHandler        ; TIMER2 Handler
        DCD     TMR3_IRQHandler        ; TIMER3 Handler
        DCD     UART0_IRQHandler          ; UART0 Handler
        DCD     UART1_IRQHandler          ; UART1 Handler
        DCD     UART2_IRQHandler          ; UART2 Handler
        DCD     UART3_IRQHandler          ; UART3 Handler
        DCD     PWM1_IRQHandler        ; PWM1 Handler
        DCD     I2C0_IRQHandler        ; I2C0 Handler
        DCD     I2C1_IRQHandler        ; I2C1 Handler
        DCD     I2C2_IRQHandler        ; I2C2 Handler
        DCD     SPI_IRQHandler            ; SPI Handler
        DCD     SSP0_IRQHandler        ; SSP0 Handler
        DCD     SSP1_IRQHandler        ; SSP1 Handler
        DCD     PLL0_IRQHandler        ; PLL0 Handler
        DCD     RTC_IRQHandler            ; RTC Handler
        DCD     EINT0_IRQHandler          ; EXT Interupt 0 Handler
        DCD     EINT1_IRQHandler          ; EXT Interupt 1 Handler
        DCD     EINT2_IRQHandler          ; EXT Interupt 2 Handler
        DCD     EINT3_IRQHandler          ; EXT Interupt 3 Handler
        DCD     ADC_IRQHandler            ; ADC Handler
        DCD     BOD_IRQHandler            ; BOD Handler
        DCD     USB_IRQHandler            ; USB Handler
        DCD     CAN_IRQHandler            ; CAN Handler
        DCD     GPDMA_IRQHandler          ; General Purpose DMA Handler
        DCD     I2S_IRQHandler            ; I2S Handler
        DCD     Ethernet_IRQHandler    ; Ethernet Handler
        DCD     RIT_IRQHandler            ; Repetitive Interrupt Timer Handler
        DCD     MotorControlPWM_IRQHandler; Motor Control PWM Handler
        DCD     QE_IRQHandler             ; Quadrature Encoder Handler
        DCD     PLL1_IRQHandler        ; PLL1 Handler

        DCD     __iar_program_start; Reset Handler

Following chip reset, a portion of the Boot ROM is mapped to address 0 so that it will be
automatically executed. The Boot ROM switches the map to point to Flash memory prior
to user code being executed. In this way a user normally does not need to know that this
re-mapping occurs.

However, when a debugger halts CPU execution immediately following reset, the Boot
ROM is still mapped to address 0 and can cause confusion. Ideally, the debugger should
correct the mapping automatically in this case, so that a user does not need to deal with it.