• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/MSP430FR5964: Debugger Remapping In Memory

Garret Holt
Intellectual 1050 points

Part Number: MSP430FR5964

Tool/software: Code Composer Studio

Hi,

We are working with MSP430FR5964 and want to split the memory into roughly 3 distinct chunks and run separate applications out of each chunk.  One application image starts at 0x004000 and the others are moved to 0x10000 and 0x22000 respectively. A few questions:

  1. How can I change the CCS debugger settings to properly connect to the application that is linked to a different address space than default?
  2. Does the interrupt vector table need to be moved to ram?  Or relocated to the proper address space for the application?

Thanks for your help!

Regards,


Garret

  • 0
    TI__Guru**** 482131 points

    Hi Garret,

    Garret Holt said:
    We are working with MSP430FR5964 and want to split the memory into roughly 3 distinct chunks and run separate applications out of each chunk.  One application image starts at 0x004000 and the others are moved to 0x10000 and 0x22000 respectively.

    I assume you already updated your linker command file to built the application to support this. If so, you shouldn't have to do anything special to the CCS debugger to support debugging of the application. The only exception is if you are using a GEL startup file which configures the debugger memory map. You just want to make sure that any changes made to the linker command file align with the GEL startup file.

    Garret Holt said:
    Does the interrupt vector table need to be moved to ram?  Or relocated to the proper address space for the application?

    This question is best answered by the device experts. I will bring it to their attention.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Mastermind 41850 points

    Hi Garret

    Very curious about why you do this to split the memory into three parts.

    For the three parts of the codes, do you want to to jump from one to the other when meet some conditions?

    Not very clear about the relation ship between the three parts of the code, could you tell more details about them?

    We have a demo code of the custom BSL that split the memory into three parts: bootloader code part, application code part and down load area part. I don't know that will be help for you. http://www.ti.com/lit/an/slaa721c/slaa721c.pdf

    Best regards

    Gary