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 recently was able to achieve flashing a bootloader / minimal image in main memory flash, along with another main application image, using UNIFLASH, while being able to use interrupts in main memory as well as the main application to implement USB.
To do this, I used the utilities provided by TI to generate a main memory bootloader project, modified the projects accordingly, and then used UNIFLASH to flash both the main application image and the bootloader images (OUT files generated by CCS). But in order for this to work I had to check the option "Replace written memory locations, retain unwritten memory locations" so that the main application image would stay flashed when I flash the bootloader (I also had to make sure to flash the bootloader last, so that the PC entry point started at the bootloader location).
However, I plan on uploading the OUT files to a cloud server and having the server flash the devices on the field remotely, so the cloud needs to be able to decode the OUT file to know what addresses need to be written to and what value needs to be written.
How is the OUT file formatted such that the UNIFLASH tool knows what memory locations to write to? I would like to decode the OUT file using Javascript or Python, for example, but I can't find details on the format of the OUT file.
Thank you!
Nicolas
Hello,
TI-TXT format output is what you are looking for. You can generate this from CCS for both your project. You just have to enable the MSP HEX Utility inside Project -> Properties, then select your output format in the MSP430 Hex Utility sub-menus.
Did you know that the MSP430F5529 comes with a BSL (Bootloader) by default? and that is can be customized as the BSL is written to a special area of Flash? If your bootloader is <2K then you could potentially place it in this area to simplify what you are doing. You can find more information under "STEP #: Customizing your BSL" on www.ti.com/tool/MSPBSL
Otherwise, if you want to continue down the current path, refer to the MSPBoot solution on the same MSPBSL page above. This is a main memory bootloader solution, so it will have some information that you may find helpful.
Oh ok so the TI-TXT hex file contains the actual instructions / op code that can be written to the beginning of FLASH region? I don't have to do any decoding?
Thanks
Nicolas,
TI-TXT file has a LOCATION address followed by data. It is assumed the data is sequential. If there is a jump, then a another LOCATION address is done. Take a look at the binaries included in CUSTOMBSL SW download for an example.
**Attention** This is a public forum