This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.


Part Number: MSP430F5340

Tool/software: Code Composer Studio

Dear All,

I would use the vector remapping in RAM for a product develop with
msp430F5342 and compiled with MSPGCC.

Is clear that SYSRIVECT enable remapping RAM at the top and seems correct my
assigment in RAM of address of interrupt procedure.

But when I try to debug, the appliction goes immediatly in crash; I suppose
becuase the heap/stack used by processor overlap the top RAM area (where
remapping vector are stored).

If is true, I'm in trouble to define in linker file (and source file) how to
redefine the stack area and reserve a RAM area for vector remapping.

Can someonelse help me ?

Thanks, Daniele Banfi
  • When posting, please include the following:

    • Version of the host OS (ex: Windows 7 64-bit, Service Pack 1)
    • Provide exact version number of CCS
    • If applicable, exact device/board (include the board revision number) and debug probe used
    • A detailed and reproducible test case. Be as descriptive as possible. Providing an executable + project/source (if applicable and possible) is also very useful. If it is not feasible to attach the test case on the forum because of IP issues, state that a test case is available upon request if someone from TI wishes to contact you for it
    • Diagnostic logs (if available)

  • Hello Daniele,

    For more information about ISR redirecting, please refer to the following post.
  • Dear All, Thanks fro answer
    I've solve the issue in this way:

    MSPGCC , linker, standard definition:

    .stack (ORIGIN (RAM) + (LENGTH(RAM)) :

    MSPGCC, linker, use SYSRIVECT

    .stack (ORIGIN (RAM) + (LENGTH(RAM)-0x80)) :

    where 0x80 is the vector table size

  • Daniele,
    glad you did.
    I am sorry for my initial response.
    most of beginners come saying: nothing changed and has crashed.
    I misinterpreted your statement: But when I try to debug, the appliction goes immediatly in crash.