MSP430F5234: Upgrade Firmware Failed

Hi Bryant

I can see you are programming F5234 through BSL.

May I know which PC sides software and what kind of board you are using?

On BSL programming board setting: please refer to MSP-BSL Bootloader (BSL) Programmer for MSP430 and SimpleLink MSP432 MCUs (Rev. C)

On command line tool: please refer to Bootloader (BSL) Scripter User's Guide (Rev. G)

Thanks

Hi Li,

The board is designed by us, and we run msp430-i2cbsl which is downloaed form TI below.

https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/i2c_bsl_linux_tools/latest/index_FDS.html

We also tried to add -n to skip BSL invoking, but still can see the same failure.

msp430-i2cbsl-tool -i /dev/i2c-1 -f /mnt/usb1/24_PSE_Manager_v211104.txt -n

Thanks,

-bryant

Hi Cheng,

For MSP430F5234 it can just support UART BSL by default 

Hi Gary,

The communcation interface betweeh host and MCU is I2C bus.

The failed message occurred when updating MCU by msp430-i2cbsl in embedded Linux.

So, do you mean we need to assert TEST/SBWTCK before launching msp430-i2cbs to update MCU?

-bryant

Cheng Shian Yan said:

do you mean we need to assert TEST/SBWTCK before launching msp430-i2cbs to update MCU?

No, the device can just support UART interface if you want to use our default BSL. For the host side, you need to use Linux right?

Yes.

You can refer to this demo https://www.ti.com/lit/an/slaa760/slaa760.pdf?ts=1653574690387&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FMSPBSL%253FkeyMatch%253D%2526tisearch%253Dsearch-everything%2526usecase%253Dsoftware 

Gary,

We have two build for our MSP430 board, including EVT1 and EVT2.

For EVT1, all boards can be updated successfully.

For EVT2, all board cannot be updated, and the failed message is shown as above.

The major difference is

EVT1: use empty MSP430 MCU to do offline program.

EVT2: use programmed MSP430 MCU to do offline program again.

Regarding these EVT2 boards, all can work normally no matter output POE power, run SIFOS test and make MCU/PSE configuration change via I2C, it all works well besides update MCU. After programming MCU via JTAG with the same configuration file, it can be updated successfully via I2C.

Can you advise how to debug it? The trouble we get into is we have delivered these boards to our cutomer, and these boards can;t be updated via I2C. So, we need to find out the root cause and know how to fix this issue.

Thanks,

-bryant

Hi Bryant,

As I mentioned before MSP430F5234 it can just support UART interface BSL. If you can update it with I2C interface that means you have create custom I2C BSL, that depends on what's your custom I2C look like. Do you know more details about that?

Hi Gary,

The problems we did not know why EVT1 can be updated, but EVT2 can't.

EVT2 can not be updated until re-programmed with the same code by JTAG.

Maybe we can find out the root cause, but I'd like to know if any possible way to update MCU via I2C. Because we've delivered a few EVT2 board to customer, we need to provide some workaround for them to update MCU.

I need your support and should include the following items,

1. How to debug why these EVT2 board can't support update via I2C

2. If item 1 is hard to achieve, how to udpate these MCU via I2C although it is terminated during update process. Any command can be workaround? 

Thanks,

-bryant

That depends how do you implemented with the your custom I2C bootloader. It is better to get your bootloader source code I can help to debug.

For EVT1, could you provide step by step program details and  the source code?

For EVT2, could you provide step by step program details and  the source code?

Gary,

We got the code from another project, and modify it for our application.

Both EVT1 and EVT2 are offline programmed by a programmer. Besides different image, there is a little difference at MCU. 

For EVT1, MCU is empty.

For EVt2, MCU has been programmed before shipping to our warehouse. So, we need to erase and re-program it with our code. I think it may be some problem here, I also check our program engineer and pthey siad this two programming procedure are the same. But it is very wierd, it can be programmed via I2C after programming by JTAG with EVT2 image.

Please note above MCU are the same part number.

I uploaded the code for reference.

48_PSE_Manager_v210901_out.txt

EVT2_24_PSE_Manager_v211104.txt

-bryant

I can't do any debug with firmware txt file. By the way why there are two firmware here? One for EVT1 and the other for EVT2?

I think should be a problem with your application source code, you can check with your software engineer first to see if any software difference between EVT1 and EVT2.

Gary,

Yes, one for EVT1 and the other one for EVT2.

Actually, we got one image which included the BSL and application code.

The major difference is configuration setting, such as power bank, port limitaion and class/port limit  mode, etc.

For EVT1, that's initial version taht we modified port map. For EVT2, we used EVT1 image to modify based on the test result on EVT1.

So, I think the code base is the same between EVT1 and EVT2. 

I did not know if we can get the application source code from our colleague because he has resigned. 

Thanks,

-bryant