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.

MSP430F5308: Selecting i2c bootloader and porting from MSP430F5308

Part Number: MSP430F5308

Hi,

I have a codebase on a MSP430F5308 that I want to port over to a part that is as close as possible but has an i2c bootloader.

I have been looking at the MSP430F525x series parts with the split voltage rail, but since all my IO is 3.3v, the 1.8v IO could prove to be a problem.  I guess from looking at the datasheet these HAVE to be 1.8 and can't be 3.3 correct?

At first we considered only having I2c coming into the part for reprogramming, but then we couldn't control the TST and RST pins to initiate the factory BSL correct?

Then we thought about watching for a "magic" I2c command from our main() drop us into the actual TI BSL, but then this could be a problem if the main code became corrupt during a download as there would be no way to recover on a power cycle as our main code to listen for the "magic" command could be overwritten.

Some of the FR parts look interesting, but they seem to all be limited to 16mhz and the application requires 20mhz.

Any suggestions on:

1) Better non-split rail part with i2c bootloader than the 525x series

2) Doing a bootloader from i2c that could be salvaged by a power cycle in the middle of a download.

3) Maybe an I2c to USB dedicated transceiver that could then do USB bootload on the 430 instead of I2c?

Best Regards,

Blake

  • Hi Blake,

    The DVIO rail can only support a maximum of 2 V so you should not look at the split-rail devices for this design. You will require either the TST/RST pins or a software solution for invoking the factory BSL. Using an I2C command from the main function could work if you used MSPBoot (SLAA600) in dual-image mode for recovery from corruption or a power cycle, but this will only work if the application image requires less than half of the memory (the other half is used for the download image, which is verified before being copied into the active space).

    Since the F5308 is a non-USB F5xx device then it should be possible to create a custom flash-based BSL, please refer the customer to the corresponding App Report (SLAA450) and CUSTOM-BSL430 software package:

    www.ti.com/.../slaa450d.pdf
    software-dl.ti.com/.../index_FDS.html

    Unfortunately a turn-key solution is not provided for the F5308 so the customer will have to further develop the custom BSL, however it remains the best option for their application.

    Regards,
    Ryan
  • thanks Ryan!  Great info...

    Best Regards, Blake

**Attention** This is a public forum