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.
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
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.
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