Tinkering TI MSP430F5529

|
Digital Input-Output – DIO
Digital Input-Output (DIO) a.k.a General-Purpose Input-Output (GPIO) coding is the basic and simplest requirement for any microcontroller. This is one area where a microcontroller (MCU) differs from a microprocessor (MPU).
MSP430F5529LP Launchpad comes with 40-pin dual-in-line headers. Of these 40 pins, 35 pin headers are connected to DIO pins. There seven DIO ports but they are not evenly divided, i.e. not all ports are 8-bit wide as one would typically expect. Most of the DIOs have more than one functionality, i.e. timer, ADC, communication, etc. DIO pins can be individually programmed as either inputs or outputs. There are independent input-output data registers. In input mode, DIOs can be pulled up or pulled down using internal pull resistors just like other MSP430s. To take care of Electromagnetic Interference (EMI) issues, output drive strength can be altered in output mode, adding incredible robustness. Additionally, pins can operate at high frequency (25MHz) conditions.

Note in the diagram above that ports are grouped as PA, PB, PC and PD. Ports are usually 8-bit wide but after adjacently grouping them as such, they become 16-bit wide. PA port pins additionally have interrupt capability unlike other ports. PA port consists of P1 and P2, PB port consists of P3 and P4 and so forth. Port grouping is helpful when we need to drive parallel port interfaces like TFT displays.
It is advised not to exceed output drive current or input voltage ranges/polarity. Best practices are to avoid driving loads directly via output pins and using buffer ICs or isolation for input pins. We must check that whether we are not overloading the microcontroller pins any how because this may have undesired consequences. Try to keep MCU’s total current consumption as low as possible. Any device is more stable at low power and optimum temperature conditions than otherwise. Remember MSP430s are low-power device.
Code Example
#include "driverlib.h" void GPIO_init(void); void main(void) { WDT_A_hold(WDT_A_BASE); GPIO_init(); while(1) { if(GPIO_getInputPinValue(GPIO_PORT_P1, GPIO_PIN1) == 0) { GPIO_setOutputHighOnPin(GPIO_PORT_P4, GPIO_PIN7); GPIO_setOutputLowOnPin(GPIO_PORT_P1, GPIO_PIN0); } if(GPIO_getInputPinValue(GPIO_PORT_P2, GPIO_PIN1) == 0) { GPIO_setOutputHighOnPin(GPIO_PORT_P1, GPIO_PIN0); GPIO_setOutputLowOnPin(GPIO_PORT_P4, GPIO_PIN7); } }; } void GPIO_init(void) { GPIO_setAsInputPinWithPullUpResistor(GPIO_PORT_P1, GPIO_PIN1); GPIO_setAsInputPinWithPullUpResistor(GPIO_PORT_P2, GPIO_PIN1); GPIO_setAsOutputPin(GPIO_PORT_P1, GPIO_PIN0); GPIO_setDriveStrength(GPIO_PORT_P1, GPIO_PIN0, GPIO_FULL_OUTPUT_DRIVE_STRENGTH); GPIO_setAsOutputPin(GPIO_PORT_P4, GPIO_PIN7); GPIO_setDriveStrength(GPIO_PORT_P4, GPIO_PIN7, GPIO_FULL_OUTPUT_DRIVE_STRENGTH); }
Hardware Setup

Explanation
The demo here alternatively turns on/off the pair of on-board LEDs with on-board button presses. Since this is the first example, I did not configure clocks and so the default clock settings are used. There is nothing dependent on timing.
Inputs are configured as inputs with internal pull-up resistor. This is so because the on-board buttons are directly connected the GPIO pins without any pull resistor.
GPIO_setAsInputPinWithPullUpResistor(GPIO_PORT_P1, GPIO_PIN1);
Outputs are configured full output drive output pins.
GPIO_setAsOutputPin(GPIO_PORT_P4, GPIO_PIN7); GPIO_setDriveStrength(GPIO_PORT_P4, GPIO_PIN7, GPIO_FULL_OUTPUT_DRIVE_STRENGTH);
In the main loop, the LED pins are toggle alternatively with button presses.
if(GPIO_getInputPinValue(GPIO_PORT_P1, GPIO_PIN1) == 0) { GPIO_setOutputHighOnPin(GPIO_PORT_P4, GPIO_PIN7); GPIO_setOutputLowOnPin(GPIO_PORT_P1, GPIO_PIN0); } if(GPIO_getInputPinValue(GPIO_PORT_P2, GPIO_PIN1) == 0) { GPIO_setOutputHighOnPin(GPIO_PORT_P1, GPIO_PIN0); GPIO_setOutputLowOnPin(GPIO_PORT_P4, GPIO_PIN7); }
Demo


|
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
You can try “On connect, erase user code and unlock the device” option.
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,
Which sensor? Did you use pullup resistors for SDA-SCL pins?
Where is lcd_print.h?
All files and docs are here:
https://libstock.mikroe.com/projects/view/3233/tinkering-ti-msp430f5529
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.
I may even make a visual configuration tool of my own for them…
Yeah the prices of TI products are higher than other manufacturers but I don’t think the hardware peripherals are inferior.
Not inferior but in not enough numbers compared to STM32.
True