• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 80 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2433: Bootloader affecting I/O lines

JDJ
Expert 4756 points
Part Number: MSP430FR2433


Hello, 

There is currently an STM micro on our project to help control power, but when we need to provide an update to the system, I/O lines go in a default condition. Since the micro I/Os helps controls the power and the I/Os go in a uknown default position this is results in the power resetting and a loop. 

When using the MSP430FR2433 or another MSP430 micro, is it possible to rewrite blocks/provide an update without I/O lines being affected? 

Thanks! 

  • 0
    TI__Mastermind 29105 points

    Hello, 

    This is an interesting question.  We do have a GPIO lock available on our MSP430FRxxx devices, but let me see if I can find out their behavior during BSL update.  I'll get back to you tomorrow. 

    JD  

  • 0 in reply to JD Crutchfield
    TI__Expert 4756 points

    Thanks for looking into this JD. Please let me know if other non-FR devices have a GPIO lock available as well. 

  • +1
    TI__Guru 56685 points

    Hey JDJ,

    If you invoke the BSL via normal means, then the MSP430 goes through a  reset and your pins will end up in default state.  You could possibly do a SW invoked BSL start, but then you are still at the mercy of the BSL code that may or may not configure pins. The BSL will definitely configure the pins it needs to work with the interface it uses (typically UART). the bSL usually assumed default setting son the MSP as it assumes you just went through a reset to get to the BSL. This is why when you do a SW invoke, you must ensure that every module the BSL uses is set to default configuration, or the BSL may not work properly.

    So in theory, with a SW invoke, your pins won't change as long as you don't reset when coming out of the BSL as well.

    The safest bet though, would be to do an application side BSL or FW updater. That way you know exactly what's going on, ensure critical functions stay up, and would never have to go through a reset. 

**Attention** This is a public forum