• State Accepted Answer
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Subscribers 143 subscribers
  • Views 15202 views
  • Users 0 members are here
Options
Related
How was your experience today?

remapping the interrupt vector table to alternate locations in the memory map

Ras Sharif

dear All,

in nxp lpc 1768 i read "remapping the interrupt vector table to alternate locations in the memory map".

for which reason one should to remap the interrupt vector table?

regards,
Ras

  • +1
    Hi,
    it would be useful to remap the vector table.
    For example, each task or thread can have a different vector table.
    If the remap target is SRAM, a specific interrupt handler can be changed.
    From a power consumption aspect, less power is consumed if the vector is in SRAM than in Flash.
    Best regards,
    Yasuhiko Koumoto.
  • 0 in reply to Yasuhiko Koumoto

    Hi Sir,

    I have a doubt, about Interrupt Vector Table (IVT) location as follows.

    • Whether the Interrupt vector table remains in lowest address (0x00000000) irrespective of what memory mapping is used? As the RST  in IVT in Boot mode, must point to Boot block address (with instruction JMP 0x7FFFD000 in LPC2148).So IVT is always at 0x00000000 location and only Program Counter is moved to Boot block.
    • Whether IVT is writable based on MEMMAP register (which decides the Memory Mapping source for Active IVT)? As for Boot mode, its JMP 0x7FFFD000 and for SDRAM mode, RST must point to SDRAM address (like JMP 0x40000000) 

    Also, if IVT is at 0x0, then the user coding starts after that IVT from 0x00000000 (i.e ) after 64bytes from 0x0 since IVT is of 64bytes. Am I right?