• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 78 subscribers
  • Views 949 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Need help porting MSPBoot (w.r.t App Report: SLAA600A) to MSP430F1611

user4195326
Prodigy 50 points
Other Parts Discussed in Thread: MSP430F1611

Hello,

I am working on a project which encompasses upgrading the application image of a wireless sensor node running on MSP430F1611 controller. To facilitate this I decided on using a bootloader to download and manage new application image.

The source code provided under MSPBoot is for different MCUs and hence I want to port it to MSP430F1611. I kindly request the support team to provide me guidelines/suggestions to carryout this procedure.

Regards,

ananth

  • 0
    TI__Expert 4215 points

    Hi Ananth,

    According to the AppNote, the following devices are supported,

    I'm currently looking into the matter and will try to come up with a possible method to port the MSPBoot.

    Sincerely,
    Sean

  • 0 in reply to Sean Huang15
    Prodigy 50 points
    Hi Sean,

    Thanks for the reply. I am pressed for time in my project right now. Is it possible for you to provide me a tentative timeline?
    Using bootloader in my project seems to be an elegant solution. But since I am running out of time I am looking into other quick hacks to achieve the somewhat similar functionality. Any suggestion is much appreciated.

    Regards,
    ananth


    PS: I am used to work on higher level. And hence am finding it a bit difficult to work with assembly related code.
  • 0 in reply to user4195326
    TI__Expert 4215 points

    Hi Ananth,

    The major changes need to be made to port MSPBoot to F1611 are the interface, the memory map, the linker files, and the interrupt vectors. The devices supported by MSPBoot use USCI, while F1611 implements USART according to the block diagram. There is a script included to change the linker files, and instructions are in section 4.2.3 of the app note. 

    As another solution, the default Bootstrap Loader(BSL) can be modified, so MSPBoot may not be required for this specific application. 

  • 0 in reply to Sean Huang15
    Prodigy 50 points
    HI Sean,

    In the App Note they keep mentioning the MSPBoot version 1.2. But in the TI website link the version available for download is MSPBoot 1_01_00_00.

    I am forced to use CrossWorks as the IDE. So again I need to convert the files from other IDEs. I found an article in CrossWorks support page
    "Converting MSP430 projects from IAR Embedded Workbench to CrossWorks". But this article is work in progress. So my work is hampered here too.

    My project involves receiving a packet from the wireless module to initiate download and upgrade of the application. Hence I think using BSL is not going to work for me.

    I will try to work on the clues you have given so far. Thank you.


    Regards,
    Ananth
  • 0 in reply to Sean Huang15
    Prodigy 50 points

    Hi Sean,

    Any updates so far?

    Regards,

    Ananth

  • 0 in reply to user4195326
    TI__Expert 4215 points
    Hi Ananth,

    I think the MSPBoot version may have been wrongly documented, as the version is the current on the download page. However, I don't think it's feasible for me to port the program over to CrossWorks for you, as I don't have any prior experience working with CrossWorks. But I can troubleshoot any problems you may have during the porting process.

    Sincerely,
    Sean
  • 0 in reply to Sean Huang15
    Prodigy 50 points

    Hi Sean,

    As of now I have managed to understand the compiling and linking process in CrossWorks. I am able to control the Memory Map of the compiled code. I have decided to use MSPBoot as only a reference now.

    As you have suggested, I will contact you if I need any troubleshooting.

    Thank you.

    Regards,

    Ananth 

**Attention** This is a public forum