MSP430FR2355: Problems with I2c BSL and msp430 bsl tool

XXXAAAMMM

Part Number: MSP430FR2355

Hello,

I am trying to get the i2c BSL on the MSP430FR2355 to work. My plan is to update it's firmware via i2c from a raspberry pi.

i installed the msp430 i2cbsl tool on the pi and connected it's i2c bus to pin P1.2 and P1.3 on the MSP. In the MSP Firmware I am invoking the

BSL via software as stated in the datasheet.

This is my code for the BSL invocation. I also made sure that the MSP runs at 8MHz.

            WDTCTL = WDTPW | WDTHOLD;

            TB3CCR0 = 0x00;         // clear Timer B
            TB3CCTL1 = 0x00;
            TB3CTL = 0x00;

            // Disable all interrupts
            __disable_interrupt();

            FRCTL0 = FRCTLPW | NWAITS_1;
            __bis_SR_register(SCG0);                           // disable FLL
            CSCTL1 = DCORSEL_3;                                // DCO Range = 8MHz
            CSCTL2 = FLLD_0 + 243;                             // DCOCLKDIV = 8MHz
            __delay_cycles(3);
            __bic_SR_register(SCG0);                           // enable FLL

            // Delay after setting clock to invoke BSL
            __delay_cycles(3);

            // Invoke BSL
            ((void (*)() )0x1000)();

After the invocation the BSL is visible on the i2c bus.

But when trying to flash a new firmware it always results in following error:

Any help would be appreciated.

Best regards

Max

over 3 years ago

0 Luke Ledbetter over 3 years ago

TI__Mastermind 19980 points

Hello Max,

It looks to be a password error, after looking at the MSP430 FRAM Devices Bootloader User Guide section 4.1.5.2, it seems that if you want to load a fresh application you can mass erase it then enter the password which will be 0xFF for all bytes.

Regards,

Luke

0 XXXAAAMMM over 3 years ago in reply to Luke Ledbetter

Prodigy 30 points

Hi,

I know but acording to the datasheet it should automatically reset to 0xFF after writing a wrong password. I checked with my oscilloscope and the MSP doens't even respond to any commands. Not even the ones which aren't password protected, like mass erase.

Regards

Max

0 Luke Ledbetter over 3 years ago in reply to XXXAAAMMM

TI__Mastermind 19980 points

Hi Max,

Looking through the MSP430 Flash Devices Bootloader User's Guide again, there are a couple things we can test. In section 1.3.2 the sample code provided uses the BSL address for the MSP430F5xx and MSP430F6xx devices. Whereas for the device you're using, MSP430FR2355, the BSL vector is at 0C00h(cold start) or 0C02h(warm start). I see in your code you still have the 0x1000 address. Section 5.3 also includes some known issues which concerns the MSP430FR2355 device commands "Erase Main or Info" and "Erase Segment".

Keep us updated,

Luke

0 XXXAAAMMM over 3 years ago in reply to Luke Ledbetter

Prodigy 30 points

Hi Luke,

sadly this didn't work. If I call vector 0x0c00 the device wont even show up on the i2c bus. Also in section 1.2 (Overview of BSL Features) it states that the fr2355 uses the 5xx, 6xx' protocol.

0 Luke Ledbetter over 3 years ago in reply to XXXAAAMMM

TI__Mastermind 19980 points

Hi Max,

You are correct, the address is 0x1000 for this device. I will be testing this to see if I can replicate the password error you are getting, but will require some time. In the mean time, there are similar threads that may offer additional ideas to try Thread 1 and Thread 2.

Regards,

Luke

0 XXXAAAMMM over 3 years ago in reply to Luke Ledbetter

Prodigy 30 points

Hi Luke,

I could narrow down the problem. It seems like the linux tool does not send the correct password. it aborts after sending 24 bytes 0xFF. Therefore the device cant be unlocked. I wrote a short script which send the password in the correct 32byte format. This way I was able to successfully unlock the device.

So there seems to be a problem with the TI provided tool

Regards

Max

0 Luke Ledbetter over 3 years ago in reply to XXXAAAMMM

TI__Mastermind 19980 points

Hi Max,

I'm glad you were able to solve the problem and responded with a solution to unlocking the device by sending the 32-byte password. Thank you for the information on the specific byte amount you saw being sent from the tool. The feedback you provided will be valuable for a future release of the Linux BSL tool.

Sincerely,

Luke

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430FR2355: Problems with I2c BSL and msp430 bsl tool