Part Number: MSP432P401R
Tool/software: Code Composer Studio
Apologies in advance for this being sort of a multi-topic question but I think all the steps relate to each other.
Currently we are using a MSP432 Launchpad board as a daughterboard on our system (it will eventually just get the processor and a JTAG header on the board when the next generation project starts). While this allows reprogramming of the firmware as well as debugging via the USB port, it is desirable to be able to allow field updates to be done over a serial port that is also used to communicate operating data when the system is running. We are using EUSCI_A2 as our system serial port.
From what I have found it seems that the CUSTOM-BSL432 package (found here: http://www.ti.com/tool/mspbsl ) needs to be customized to specify the desired UART port, compiled and loaded first; then my application is loaded after that and then using the BSL-SCRIPTER (from previous link) there is a way to set things up to automate the process of updating my application via the serial port. Unfortunately while there seems to be lots of details in the BSL User’s Guide (http://www.ti.com/lit/ug/slau622e/slau622e.pdf ) I cannot find any simple examples of how to accomplish all of this. There are a couple of threads on the forum including this one (https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/535669?tisearch=e2e-sitesearch&keymatch=MSP432%20bootloader ) that indicate (as I suspected) that properly setting up the linker files is some of what needs to be done, but for those of us who are hardware guys at our core and not software wizards it is still rather confusing.
Perhaps I have missed finding a tutorial or example somewhere that someone can point me to?
In the same vein I am also looking for a way to reserve a block of Flash for control parameters and be able to download or program that via the serial port (I can always do this in my code but it seems that the BSL-SCRIPTER might allow this to be easily done). And to support debugging I assume that part of the linker file setup mentioned above would be involved with allowing the control parameters NOT to be touched when reprogramming the application over USB?
Some details: Using CCS 7.1.0.00016 and have the simplelink msp432 sdk v 1.40.00.28 included in our code (that was current when I started and we won’t be changing during development unless absolutely necessary).
Any suggestions, pointers, links to a tutorial, etc. would be greatly appreciated.