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.

OTAP and MSP430...

Other Parts Discussed in Thread: MSP430WARE

Hi - I'm just getting started with MSP430s - long background with Atmel & Microchip etc. and C/C++ programming, but now have a remote, low-power, sensor network to build...

As many of the nodes will be remote (very very remote), OTAP (over the air programming) has great attraction - I will have a GSM modem so SMS & GPRS (hopefully!) available.

As I know very little at the moment about the MSP430 ()that will change over the next few weeks), I was wondering if there is any exemplar code out there for OTAP - even just some pointers as to a good approach would be appreciated - remember, I'm new to MSP430s (and Ti in general)...

Also open to recommendations regarding dev environments - I naturally prefer free if at all possible, but functionality & ease of use is the premier requirement.

Many thanks

Nick

  • Nick de Smith said:
    As I know very little at the moment about the MSP430 ()that will change over the next few weeks), I was wondering if there is any exemplar code out there for OTAP - even just some pointers as to a good approach would be appreciated - remember, I'm new to MSP430s (and Ti in general)...

    Msp430 does not differ much from programming point of view. So basic ideas are the same here - if you know how to do OTAP on Atmel and Microchip then you know how to do it on msp430. Do you plan communication full-duplex with some kind of ARQ protocol?

    Basic idea is that wireless sensors which supposedly can have communication problems shall have flash memory for complete two copies of both - flash update code and application. So you can run application during flash update (receive process) in parallel, also update flash update code if needed. All this shall have good roll-back policies - if new code repeatedly fail to do it's job then sensor try to use previous version, maybe asking permission of controller - if full duplex comms. Also you shall think about comms protocol so new functions call be added still having compatibility with older versions. Think that your sensor network can have some nodes running v3 firmware while rest of it runs v2 and some nodes for some reason stuck in v1 because fail to do firmware update.

  • Nick de Smith said:
    I was wondering if there is any exemplar code out there for OTAP - even just some pointers as to a good approach would be appreciated - remember, I'm new to MSP430s (and Ti in general)...

    The eZ430-Chronos watch has a Wireless Update (RF BSL).

    See the examples\boards\eZ430-Chronos\Software Projects\Chronos Watch\eZ430-Chronos v1.0 - black PCB\IAR\Wireless Update directory in MSP430ware for the source code.

**Attention** This is a public forum