MSP430F5436A crystal clock

So you run ACLK from 32 KHz crystal and run USCI peripheral in I2C mode from ACLK. Besides reading x5xx series User's Manual you would want to check source code examples

Hi,

Source code examples would be great...where can I find them?

I can't imagine that I'm the first one facing this challenge as a new MSP430 programmer :)

Regards,

Hamed

Hamed Ebrahimmalek said:

Source code examples would be great...where can I find them?

Did you try to look into product page of chip you use?

http://www.ti.com/product/MSP430F5436A

I already looked at the product page. That was the first place I looked for information.

I really don't mind finding information, I was hoping that some MSP430 guru will help me.

My question isn't yet answered, TI experts please help.

Hamed Ebrahimmalek said:

I was hoping that some MSP430 guru will help me.

You was hoping that someone will do your job for you?

Here you go:

in product page you can find User's Guide: http://www.ti.com/lit/pdf/slau208

And source code examples: http://www.ti.com/lit/zip/slac375

Hamed Ebrahimmalek said:

My question isn't yet answered,

You actually got answer:

Ilmars said:

So you run ACLK from 32 KHz crystal and run USCI peripheral in I2C mode from ACLK.

You just completely ignored it

look, I don't want anyone to do the job for me! I just want some guidance through this jungle of documentation. I expected from TI community to be more challenging. Just like the competitors ;)  the MSP430 is just new to me, just give me some information how to realize this! Or just say nothing. Information you gave can interpreted and implemented completely wrong and since I'm new here don't treat me like that. I'm not a school boy.

Just give me links with more implementation information, not a link to a complete documentation, that's all.

llmar, please waste your time on other members. have a nice evening.

what you 

Ilmars said:

I was hoping that some MSP430 guru will help me.

You was hoping that someone will do your job for you?

Here you go:

in product page you can find User's Guide: http://www.ti.com/lit/pdf/slau208

And source code examples: http://www.ti.com/lit/zip/slac375

Hamed Ebrahimmalek said:

My question isn't yet answered,

You actually got answer:

Ilmars said:

So you run ACLK from 32 KHz crystal and run USCI peripheral in I2C mode from ACLK.

You just completely ignored it

[/quote]

-- For the new guys who want to see some examples --

To find some useful source code, don't look in the documentation, of course read that on a rainy Sunday....

There are examples made by TI and these examples can be found in the TI directory. Of course, you'll probably find somewhere a reference to this folder and sub-folder...

Ok, path to the examples is:

C:\ti\ccsv5\ccs_base\msp430\msp430ware_1_40_01_44\examples\driverlib\MSP430F5xx_6xx\ucs\CCS\ucs_ex3_XT1SourcesACLK

Hopefully, I receive for my next post more useful replies....

Hamed Ebrahimmalek said:

To find some useful source code, don't look in the documentation, of course read that on a rainy Sunday....

Well, sure! To find some useful source code you shall read forum posts (instead of blaming others not helping you):

Ilmars said:

And source code examples: http://www.ti.com/lit/zip/slac375

switching LFXT1 on & configuring ACLK to run from LFXT1:

msp430x54xA_UCS_6.c

various clock-related code:

msp430x54xA_UCS_?.c

using USCI in i2c mode:

msp430x54xA_uscib0_i2c_??.c

running USCI from ACLK:

msp430x54xA_uscia0_uart_02.c

Hi Hamed,

You may find this MSP430 Tutorial useful.

Hamed Ebrahimmalek said:

To find some useful source code, don't look in the documentation, of course read that on a rainy Sunday....

Actually, I would recommend read (or at least peruse) that first! Then you know what information is available when you need it later on.

And llmars initially pointed you to the product page. There are several sections on that page, including one towards the bottom labeled "Software". MSP430Ware is included in that section which has all the example code. Note that you didn't specify toolchain, so there was no way for us to know that you already had it on your PC (you have to download/install manually if using IAR or gcc).

As far as forum etiquette, we get a lot of what I would term "lazy students" here, so understand that we tend to reply "RTFM" when that seems the case, though I try to give a gently nudge towards the correct manual.

Hamed Ebrahimmalek said:

I just want some guidance through this jungle of documentation

It’s not a jungle, only a tiny forest. (But of course sometimes one doesn't see the forest because of all the trees)

You only need three documents: the datasheet, which covers all device-specific information such as features, electrical parameters and mappings, the users guide which covers the functionality of all parts found in any MSP of a family, and the errata sheet that tells where the real behavior differs from the expected.

All three documents are available right on the beginning of each MSPs product page.

Any additional documentation might be helpful but isn't really needed. It is usually found further down the page and you might need to clock on the 'more' tabs to expand the lists.

My last post on this subject, and my post is for the forest, the Robin hood, the Tarzan, who see the forest...

I've thought  about this conversation and it's funny to me, this is what happened:

person a, b and c...

a: I've read the documentation and need some examples...

b: read the doc

a: I've read it

b: you want me to do the job?!

a: no, need only examples

b: read the doc

this is my favorite part...

c: jungle forest, read the doc, product page

Guys come on, I asked for examples and not philosophical talk.

Ok, now serious, llmar did gave me the right information and Gustavo answered my question. I thank you both for that. By the way, Brian I think in daily life you're a nice guy. I really liked your reply.

I think that the TI community got a lot to learn from Stack Overflow an other forums...

Thank you all hope to see you on my next post :) Don't worry it's another subject.

Kind regards,

Hamed

Hamed Ebrahimmalek said:

this is what happened:

Really?

You got generic hint as answer to quite generic question in first reply: "So you run ACLK from 32 KHz crystal and run USCI peripheral in I2C mode from ACLK. "

Did not even noticed.

In next answer I pointed you to product page where you can find source code examples. It's easy - you just look for word "example" in particular page!!!

Still requesting examples.

Then I gave direct download link of example .zip file. Your answer: 

I just want some guidance through this jungle of documentation

I don't even want to comment this. Except that I do not represent whole TI e2e community.

Regards,

Hamed Ebrahimmalek said:

I think that the TI community got a lot to learn from Stack Overflow an other forums...

I don't think so. S/O is a much bigger community with the ability to spread the "workload" over a larger volunteer group. You had some of the best people on this forum reply to your post, some of whom English is not their first language.

Just keep in mind that we generally expect that you 1) can show you've tried to find the information (perhaps you just don't understand it if you did find it) and 2) provide all the pertinent details for us to best help you (device type, if using experimenter board - which one, any scope/logic captures, relevant source, etc).

this is what happened:[...] I asked for examples and not philosophical talk.

There is a difference between looking into the docs, reading it and understanding it.

And the course of the discussion indicates that b thinks that you might have looked into the docs but did not really read and by no way understood the content, or you wouldn't have asked.

I never had any different source than the same docs everyone else can download. So in theory, I cannot give any advice that someone couldn't get directly from the docs too. Except for things based on my personal experience, independent of any documentation or information from TI or the forum.

So if I see a question that can be answered without the experience part, straight from the docs, I can understand why someone gives the advice to read the docs. Would be my first advice too - and what I would do myself, if I had this question.

After all, this forum is called e2e: engineer-to-engineer. And from an engineer one would except that he knows how to read a datasheet. Or to locate a download link after he has been pointed to the page and told "it's there".

I admit that there are concepts that are not easily understood. The mass of configuration options allows for a vast number of possible applications but also makes it a bit difficult to get the whole picture. And I'm glad if I can help in these cases. But if I just have to open the users guide and cite an emphasized note to answer the question, then 'read the docs' is as good an advice. Or even a better one, as it might have some educational effect (e.g. noticing some more information for future use while searching for the answer)

Jens-Michael Gross said:

And the course of the discussion indicates that b thinks that you might have looked into the docs but did not really read and by no way understood the content, or you wouldn't have asked.

Point is that sometimes it's irrelevant what b thinks because a wants just to prove his own truth

Ilmars said:

sometimes it's irrelevant what b thinks because a wants just to prove his own truth

Sometimes, yes. And sometimes it is a language issue. Not regarding being a native speaker but regarding what this or that will mean technically. If you have a different idea about what a thing means technically, both sides may use the same words but don't really understand what the other one is talking about - without even noticing.

I have this happening a low with a colleague: I talk, he nods, and 10 minutes of nodding later, it turns out that he totally missed the point and didn't even notice it. Usually, I then wonder why he's saying something that totally contradicts what I was talking about. And then I have to go back and find the place where our mental images of the topic begun to drift apart.

I must admit that I'm not always patient, especially if he could have much sooner noticed that what I'm saying doesn't fit into his picture of the situation.