MSPBSL: UART Programming does not seem to be according to documentation

As promised, here are some other captures of commands:

• Change Baudrate, No response
• TX BSL Version, No response
• TX Data Block, Wrong header
• Load PC, Wrong header

These captures are all taken from the MSP430's side, so I know the bytes are arriving correctly and we can also communicate perfectly fine with the user application in the MSP430, so I'm pretty sure the communication lines are working correctly.

Change baudrate:

TX BSL Version:

TX Data Block:

Load PC:

Bas,
is the device blank means do you use the blank device detection described in chapter 3.3.3. of SLAU550P?
If not can you please provide the BSL entry sequence?

Hello Dietmar,

No, I did not mean the blank device detection. By sending a command to our firmware on the MSP430 we can enter the BSL. I've taken a look at the sources of the firmware of the MSP430 and I've found that the command we send from the STM32 invokes the following asm code:

__disable_interrupt(); // disable interrupts

set_error_led( TRUE );

// start BSL
__asm("        MOV.W  #1,           R12");
__asm("        MOV.W  #0xDEAD,      R13");
__asm("        MOV.W  #0xBEEF,      R14");
__asm("        MOV.W  #__BSL_START, R15");
__asm("        MOVX.A R15,          PC");

I'm not very familiar with programming MSP430's (I'm not the programmer of the firmware on our MSP430 either), so if this is not what you meant I'd gladly hear it.

Regards,

Bas

Hi Bas,

no problem I also asked our BSL expert to check this case. In the meantime I'm still not sure if you really invoked the BSL.
Please take a look to

and here focus on chapter 1.3.1 Hardware BSL Invocation.

If you can show me the BSL entry sequence on a scope shot it would help to know if it was invoked correclty.

Hello Dietmar,

The problem here is that we're not using the hardware BSL invocation, but the software BSL invocation as described in 3.3.1.1 of SLAU550P. We can program the MSP430 through an MSP430FET just fine, I'm not sure if this uses the BSL or not, we just have issues with the software BSL invocation.

On another note, the SLAU319T documentation I think is meant for Flash based devices. We're using an FRAM device (MSP430FR2422). That's why I've been using the SLAU550P documentation.

I'll try to use the hardware BSL invocation with UART and come back to you with data on that.

Kind regards,

Bas

Hi Bas,

sorry my fault the document you're using is correct. So based on what you said you mean that via the STM32 you trigger the invoke function correct? How this is done over a UART command or over port interrupt?
Can you show the function which invokes the BSL?
The BSL guide describes how to call the BSL
__disable_interrupt(); // disable interrupts ((void (*)())0x1000)(); // jump to BSL

I would assume you have implemented this as well correct? The commands above will not jump to address 0x1000 where the BSL starts

Hello Dietmar,

So far I have been unable to start the BSL through the hardware sequence, but that's because of the hardware we're using. This is still ongoing.

Concerning the function to invoke the BSL is as the commands above. The jump to address 0x1000 is done by the asm commands:

It could be that we have to jump to address 0x1000 before changing R12-R14, is this needed?

What we find weird though, if we're not correctly entering the BSL, why is it responding with 0x51?

Bas,
no that's fine I think will discuss further with our BSL expert and come back to you.

Hi Bas,

thank you for your input. We are going to update the document about parity information for SLAU550.