Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

How to work with MSP-EXP430F5438 Experimenter Board

Status
Not open for further replies.

sunil880089

Full Member level 2
Full Member level 2
Joined
Aug 24, 2011
Messages
125
Helped
3
Reputation
6
Reaction score
3
Trophy points
1,298
Activity points
2,031
Hi everyone,

I have one MSP-EXP430F5438 Experimenter Board,but i don't know how to start operation and how to work..
So please anyone help me to start work from the beginning with MSP-EXP430F5438 Experimenter Board.

Please help me...
Thank you.
 

Thank you sir.

If You have more information's then please tel me...
 

Can anyone please help me to find sample code for MSP-EXP430F5438 Experimenter Board..
 

The TI MSP430F5438 Experimenter Board Product Page has several example programs available for downloading:

**broken link removed**

**broken link removed**

**broken link removed**

You can also adapt several of the examples in the follow text to the MSP430F5438 Experimenter Board:

MSP430 Microcontroller Basics

Don't be mislead by the title, the text covers far more than the "Basics" and is actually one of the only texts available which covers the MSP430 in excellent fashion.

Do you have a MSP430FETUIF or similar programmer?

BigDog
 
Thank you sir. but i am facing problem to download the code to the Board.
In code examples i am confusing that which program i have to build..
please help me..

---------- Post added at 16:00 ---------- Previous post was at 15:59 ----------

The TI MSP430F5438 Experimenter Board Product Page has several example programs available for downloading:

**broken link removed**

**broken link removed**

**broken link removed**

You can also adapt several of the examples in the follow text to the MSP430F5438 Experimenter Board:

MSP430 Microcontroller Basics

Don't be mislead by the title, the text covers far more than the "Basics" and is actually one of the only texts available which covers the MSP430 in excellent fashion.

Do you have a MSP430FETUIF or similar programmer?

BigDog


Thank you sir.
i am using CCS v5 programmer.
 

Hello!

What kind of emulation interface are you using?
MSP-FET430USB?
As for the examples, we cannot decide for you which program you want to build.
Choose one, compile it and try to verify that it works on the board, that would be
a good first step. I guess there is a LED blinker. Choose it, compile it and try
to load it to the board. What happens?

Dora.
 
Hello!

What kind of emulation interface are you using?
MSP-FET430USB?
As for the examples, we cannot decide for you which program you want to build.
Choose one, compile it and try to verify that it works on the board, that would be
a good first step. I guess there is a LED blinker. Choose it, compile it and try
to load it to the board. What happens?

Dora.

thank You sir,
i am using MSP-FET430USB emulation interface.

i downloaded program from this link
**broken link removed**

In this zip folder many programs are there. i don't know which one i have to use. please help me.

and as you told i didn't get LED blinker program.

please help me.
 

Hello everyone , i am facing This following problem while Building the program. please tel me the solution

"unresolved symbol SELECT_ACLK, first referenced in ./UserExperienceDemo/LPM.obj"


please
 

Hello!

As far as I remember, UserExpreienceDemo is a program involving a large set of files,
not a beginner program. Usually, when you are a beginner in C, you try "Hello World",
you don't try to compile the Linux kernel.

Blinking a LED is simple.
- Find on which port it is. On many TI boards, you have a LED on P1.0, so let's assume
it's P1.0 (but please verify on your board).
- Write a program like this:

Code:
#include <msp430F5438.h>

int main(void) {
    // Disable the watch dog timer. I never remember this line, I always copy it from another program
    WDTCTL = WDTPW+WDTHOLD; 
    P1DIR = 0x01;
    P1OUT ^= 0x01; // Set a breakpoint at this line.
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
}

Compile, load, run, and advance step by step. The LED should alternate on and off.

Try this, report your results and we'll see what we can do in case it doesn't work.

Dora.
 
After reviewing your sample program, it appears you have forgotten to include a Super Loop.

In an Embedded System you should never allow the code execution to exit main().

The same effect can be safely achieved with the following code which utilizes a Super Loop:

Code:
#include <msp430F5438.h>

int main(void) {

    // Disable the watch dog timer. I never remember this line, I always copy it from another program
    WDTCTL = WDTPW+WDTHOLD; 
    P1DIR = 0x01;

    while(1)  //Super Loop prevents code execution form exiting main()
    {
        P1OUT ^= 0x01; // Set a breakpoint at this line.
    }
}

BigDog
 
Hello!

After reviewing your sample program, it appears you have forgotten to include a Super Loop.
In an Embedded System you should never allow the code execution to exit main().

That's true, I should have added __bis_SR_register(LPM0_bits + GIE); at the end.
The purpose of this "program" was only to verify that code is downloaded and works.
In the case of MSP 430, I never put a loop inside of main, because there is an implicit
hardware loop when entering low power mode. A possible MSP430 program may look like this:

Code:
void main(void) {
    WDTCTL = WDTPW+WDTHOLD;
    [ Add program initializations here ]
    __bis_SR_register(LPM0_bits + GIE);
}

And nothing more. That's the beauty of interrupt-only code. And if there are no interrupts,
it simply does nothing at the end.

Dora.
 
Hello!

As far as I remember, UserExpreienceDemo is a program involving a large set of files,
not a beginner program. Usually, when you are a beginner in C, you try "Hello World",
you don't try to compile the Linux kernel.

Blinking a LED is simple.
- Find on which port it is. On many TI boards, you have a LED on P1.0, so let's assume
it's P1.0 (but please verify on your board).
- Write a program like this:

Code:
#include <msp430F5438.h>

int main(void) {
    // Disable the watch dog timer. I never remember this line, I always copy it from another program
    WDTCTL = WDTPW+WDTHOLD; 
    P1DIR = 0x01;
    P1OUT ^= 0x01; // Set a breakpoint at this line.
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
}

Compile, load, run, and advance step by step. The LED should alternate on and off.

Try this, report your results and we'll see what we can do in case it doesn't work.

Dora.

K sir thank you.. i will try.

---------- Post added at 10:07 ---------- Previous post was at 10:06 ----------

After reviewing your sample program, it appears you have forgotten to include a Super Loop.

In an Embedded System you should never allow the code execution to exit main().

The same effect can be safely achieved with the following code which utilizes a Super Loop:

Code:
#include <msp430F5438.h>

int main(void) {

    // Disable the watch dog timer. I never remember this line, I always copy it from another program
    WDTCTL = WDTPW+WDTHOLD; 
    P1DIR = 0x01;

    while(1)  //Super Loop prevents code execution form exiting main()
    {
        P1OUT ^= 0x01; // Set a breakpoint at this line.
    }
}

BigDog

K sir. thank you...

---------- Post added at 12:01 ---------- Previous post was at 10:07 ----------

Hello!

As far as I remember, UserExpreienceDemo is a program involving a large set of files,
not a beginner program. Usually, when you are a beginner in C, you try "Hello World",
you don't try to compile the Linux kernel.

Blinking a LED is simple.
- Find on which port it is. On many TI boards, you have a LED on P1.0, so let's assume
it's P1.0 (but please verify on your board).
- Write a program like this:

Code:
#include <msp430F5438.h>

int main(void) {
    // Disable the watch dog timer. I never remember this line, I always copy it from another program
    WDTCTL = WDTPW+WDTHOLD; 
    P1DIR = 0x01;
    P1OUT ^= 0x01; // Set a breakpoint at this line.
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
    P1OUT ^= 0x01;
}

Compile, load, run, and advance step by step. The LED should alternate on and off.

Try this, report your results and we'll see what we can do in case it doesn't work.

Dora.

Ya sir.. thank you.. this program works...
 

In the case of MSP 430, I never put a loop inside of main, because there is an implicit
hardware loop when entering low power mode.

And nothing more. That's the beauty of interrupt-only code. And if there are no interrupts,
it simply does nothing at the end.

While that is case with the MSP430 under those circumstances, it is clearly not the case for the vast majority of other microcontrollers and processors, as such the lack of a Super Loop in a non RTOS code design can only be described as a poor programming practice.

And the sheer number of threads posted in this forum dealing with that specific issue is testament to the fact.

Besides, a Super Loop typically compiles to a single branch instruction, therefore code efficiency in not a valid argument.

The moral of the story is -- Always coding to prevent code execution from exiting main() is a good habit and programming practice, while exploiting the exceptions to this rule can result in unexpected results.

BigDog
 
Hello!

While that is case with the MSP430 under those circumstances, it is clearly not the case for the vast majority of other microcontrollers and processors

In this thread, we are talking explicitly about MSP430, aren't we?

And the sheer number of threads posted in this forum dealing with that specific issue is testament to the fact.

And in many cases, it's even a testimony.

The moral of the story is -- Always coding to prevent code execution from exiting main() is a good habit
and programming practice,

I agree. With an explicit loop or with low power mode hard loop.

while exploiting the exceptions to this rule can result in unexpected results.

Do you classify MSP430's hardware loop in those exceptions?
Is there any "danger" or unexpected result in using MSP430's low power mode?
Or are you referring to other kinds of exceptions?

Dora.
 
Hi everyone,
Can anyone please tel me that ,which Graphics LCD is used in MSP-EXP430F5438 DEVELOPMENT BOARD..

please reply.
 

The MSP-EXP430F5438 Development Board has a Hitachi HD66753 Controller based Dot Matrix LCD with a 138 x 110 resolution and 4-level grayscale pixels.

The HD66753 Controller has a SPI/I2C like interface by which to communicate with the MSP430.

**broken link removed**

MSP430F5438A Experimenter Board --LCD Interface

I have also attached the GLCDs datasheet.

BigDog
 

Attachments

  • 5415.51933ace.pdf
    73.2 KB · Views: 136
The MSP-EXP430F5438 Development Board has a Hitachi HD66753 Controller based Dot Matrix LCD with a 138 x 110 resolution and 4-level grayscale pixels.

The HD66753 Controller has a SPI/I2C like interface by which to communicate with the MSP430.

**broken link removed**

MSP430F5438A Experimenter Board --LCD Interface

I have also attached the GLCDs datasheet.

BigDog

Thanks for replying ...
But in MSP-EXP430F5438 Experimenter Board User's Guide they mentioned that The HD66753 is a Hitachi dot-matrix LCD with a resolution of 138 x 110
so i am confusing... please help me.
 

.
But in MSP-EXP430F5438 Experimenter Board User's Guide they mentioned that The HD66753 is a Hitachi dot-matrix LCD with a resolution of 138 x 110
so i am confusing... please help me.

What exactly is confusing you?

The HD66753 is the display controller chipset, much like the popular HD44780 used in the common 16x2, 20x4, etc., LCDs.

The actual display datasheet is the attached file.

BigDog
 
Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top