MSP430FR2353: MSP430 Bootloader - BSL User configurations

Akash Kalaria

Part Number: MSP430FR2353

I am developing the MSP430FR2353 firmware update from another MPU over I2C bus using MSP430 BSL.

For the same, I want to make BSL user configuration specifically to change I2C communication from the default I2C bus eUSCI_B0 (pins P1.2 & P1.3) to eUSCI_B1 (pins P4.6 & P4.7).

I am referring to the slau550aa.pdf. It provides two tables - "Table 3-1. BSL Device Descriptor" and "Table 3-2. BSL User Configuration Structure".

However, it seems the "Table 3-1" details does not fit into the "Table 3-2" Structure as per the required bytes.

Could anyone please help me how I can map these two tables details to get the correct BSL user configurations?

Will BSL signature and config field will replace the BSL tag/length and timer base address field or what?

BSL Device descriptor BSL User config structure

over 3 years ago

+1 Gary Gao over 3 years ago

TI__Mastermind 39710 points

Hi For 3-1 is the data located at ROM that is the the default configuration of the BSL. For the 3-2 is the information can be re-configured by user it is located at FRAM.

0 Akash Kalaria over 3 years ago in reply to Gary Gao

Prodigy 10 points

Thanks for the response Gary.

Could you please confirm my understanding on the same?

Offset 0x0,0x1,0x3 must be set as 0x5a, 0x69, 0x5a respectively to enable the user config.
Offset 0x2 will be as per requirement.
From offset 0x4 to 0x18, we can set as required as per the table 3.1 parameters.

0 Gary Gao over 3 years ago in reply to Akash Kalaria

TI__Mastermind 39710 points

Yes, you are right.

0 Akash Kalaria over 3 years ago in reply to Gary Gao

Prodigy 10 points

Thanks for the confirmation Gary.

Also do we need to add the "Address of BSL user configuration data" parameter at 0x1c and 0x1d offset? (As per table 3.1) ?

I want to confirm because, “3.6.1.1 Example of BSL User Configuration” does not showcase that information in sample example.

Also, if I calculate the actual location of “BSL user configuration data”, then it will be 0xFFA4 [ 0xFF88 (base address) + 0x1C (offset) ]. That overwrites the other important addresses of the linker file. Please check the below attached screenshot. Here, I have added BSL config (0 to 10) parameters to fill up the details as per Table 3.1. Now if I want to add 0x1c and 0x1d offset parameters, then it will overwrites the INT00 and INT01 address locations.