Tinkering TI MSP430F5529


My journey with MSP430F5529 has been a mixture of success and failure. It is successful in terms of being able to apply driverlib successfully while being able to master a mid-range high performance TI microcontroller. Most of the hardware is similar to other MSP430 micros and so I had little or no issues understanding them. This is for the first time I got to get myself introduced with a TI micro that has USB hardware as well as other advanced hardware like DMA, RTC, hardware multiplier, etc that are typically found in ARM microcontrollers. Previously, I have seen similar microcontrollers like PIC18F4550 and ATMega32U4 but none of them were as rich as MSP430F5529 when it comes to both hardware and software suites.

The failure part is the time it took for me to get all these things together because on the internet I didn’t find much support for most of the stuffs I needed to know quickly. I had to read lot of docs and try out several things before I could make a solid conclusion. However, after completing this tutorial doc, I believe no one will have issues as I had. I also believe that it will pave way for developing stuffs with TI’s Tiva C ARM microcontrollers as working with Tiva micros need knowledge of TivaWare – a software suite from TI that is similar to MSP430Ware.

To summarize, this MSP430 beast packs a good punch that can help us avoid investing on an ARM overkill or on other expensive platforms. It has everything to make devices like a datalogger, a USB power meter, an advanced MPPT solar charge controller, a balancing robot, etc. In fact, in my professional career, I have seen several control systems that host TI microcontrollers like the MSP430F5529. MSP430F5529 is like an ARM micro in 16-bit disguise. I would strongly urge readers to explore this microcontroller family and beyond. Last but not least, TI microcontroller portfolio has microcontrollers for various application-specific purpose but compared to other manufacturers TI’s microcontrollers are smart and well-designed in terms of hardware management. TI also manufactures other digital and analogue components. This allows us to design a complete board with all-TI components while making TI a good component partner.  

The PDF version of this post and the code examples can be found here.

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

Related Posts


  • Hi,
    Im interfacing MSP430F5529 with MAX17055 fuel guage. while reading 16 bit value, the first byte im receiving is 0. so while reading multiple registers continuously the data exchange is happening, but im getting the correct data. Can anyone suggest me what will be the issue? why im getting 0 in first byte?

    read16_bit data code:

    uint16_t value = 0;
    USCI_B_I2C_setslaveaddress(USCI_B1_BASE, slave_address);
    while (!USCI_B_I2C_masterSendStart(USCI_B1_BASE));

    USCI_B_I2C_mastterSendSingleByte(USCI_B1_BASE, reg_address);

    USCI_B_I2C_setslaveaddress(USCI_B1_BASE, slave_address);

    uint8_t lb = USCI_B_I2C_masterReceiveMultiByteNext(USCI_B1_BASE);
    uint8_t hb = USCI_B_I2C_masterReceiveMultiByteFinish(USCI_B1_BASE);

    while (USCI_B_I2C_isBusBusy(USCI_B_BASE));

    value = lb << 8;
    value |= hb;
    return value;

  • Hi, im trying to send the command from the terminal view. i can able to send the command and tried to blink p1.0 led in msp430f5529 controller, its working fine. And im using led driver IS31FL3236A interfaced with msp430f5529 controller, i can able to interface im getting the expected output.

    now i need to send the command from seriak monitor based on that command i2c communication need to start. both communication are working fine, when it runs separately. its not working when i tried to combine.

    any one had any idea, why it is happening or what will be the issue?

    • It could be due to:

      1. conflicts in clock settings
      2. hardware conflict like pin mapping
      3. code is getting stuck or waiting for one communication line to finish
      4. use of polling method instead of interrupt-driven coding

      • Hi, thank you for the respose.
        Do I need to use different clock initialization for I2C and UART communication? if YES, can you explain how to do that?

      • Is there any example on how to implement polling method in uart?

        • Why go for polling method when it is a blocking method of coding? It is better to use interrupts instead at least for UART receive.

          • yes!! currently in my code, only for uart im using interrupts to recieve command from serial monitor. Im not using interrupt for I2C communication.

          • so the issue is must be in clock initialization. right?

            For UART, im using USCI_A1_BASE. and for I2C, im using USCI_B1_BASE.

            And another thing i need to ask is, in uart when i tried blink led(p1.0) in msp430f5529 by passing command. here, without clock I’m getting output. how it is possible?

            And for both i2c and uart i gave SMCLK with 1Mhz

  • I am surprised and happy to find this tutorial on the F5529 as TI makes a lot of different devices.
    Thank you very much for putting in the extra knowledge in each segment, made reading worthwhile.
    Good Work!

  • lovely tutorial but to be honest I don’t think I’d be investing my time on this board to start with it’s not cheap and readily available as the stm32 boards can you please do more tutorials on stm32 board’s and the stc micros thanks

  • Hello, I try to program MSP430FR6047 but i get error “the debug interface to the device has been secured”. when flashing using uniflash and when program using CCS this happen. can you help me to solve this problem

  • Pingback: Tinkering TI MSP430F5529 – gStore

  • Hello
    I am doing project of msp430g2553 interface(using i2c communication) with temp 100(temperature sensor) and try to read the temperature in dispaly(16*2) but didn’t get the out put (using code composer studio) can u share me any example code for this project

    Thank you sir,

  • Where is lcd_print.h?

  • You want the truth? TI makes and sell “underpowered micros”, you know? Low everything, not only the power but also peripherals. So the price is not justified.

    Otherwise, if I’ll move there, I’ll introduce them to my small hobby projects – there are still some advantages.

Leave a Reply

Your email address will not be published. Required fields are marked *