Example Code ... Msp430f552c C Code

Go to the specific device Product Folder.
Navigate to the Software category.
If necessary, select Show More, to reveal the software C examples.

It would be nice if the rev number were appended to the subdir ... helps customers know if the website has the same version the customer already has.  The ReadMe does not have a rev either.

I just noticed.  The example code I have is labeled MSP430F552x ... the example code I downloaded is MSP430F55xx.  What's the scoop?

I don't see any example code for the DAC. 

In addition if you are using CCS v5, all of the code examples are already included there. Just go to TI Resource Explorer window in CCS (if not already open you can find this window under View > TI Resource Explorer) then navigate to the F552x code examples (MSP430Ware > Devices > MSP430F5xx/6xx > Code Examples > MSP430F552x). You can open one of the code examples there into your workspace just by clicking on it.

If you are using IAR the code examples are still included in the standalone MSP430Ware: http://www.ti.com/tool/msp430ware

Regards,

Katie

Still waiting.  Forget the DAC ... error on my part ... the example code numbers are a valid question.

Hi,

The F5529 device does not have a DAC - please see the datasheet: http://www.ti.com/lit/gpn/msp430f5529

You can either choose a different part (you can filter for different characteristics like the DAC) on this page: http://www.ti.com/lsds/ti/microcontroller/16-bit_msp430/product_search.page

Or you can implement a PWM DAC on the F5529 Timer B module like in this app note: www.ti.com/lit/pdf/slaa116

And if you need a higher resolution PWM DAC you can use a part with Timer D and use this app note and example code: www.ti.com/lit/pdf/slaa497 www.ti.com/lit/zip/slaa497

Hope this helps!

Regards,

Katie

460822 said:

It would be nice if the rev number were appended to the subdir ... helps customers know if the website has the same version the customer already has.  The ReadMe does not have a rev either.

If you look at the zip file name it will have a revision letter on it that tells what revision it is. For example, the latest version of the F55xx code examples on the web is rev. d and the zip file is "slac300d.zip". So when you extract it if you kept the same folder name you can tell what revision it is. This is the same way document lit numbers are handled - there is a revision letter at the end of the lit number. Whatever version is on the web is the most current one. You can also subscribe to be email alerted when documents for a particular device change by clicking the "Alert me about changes" in the upper right hand corner of the product page.

460822 said:

I just noticed.  The example code I have is labeled MSP430F552x ... the example code I downloaded is MSP430F55xx.  What's the scoop?

 The web code is the latest one. When the F5529 first came out, there were only F552x parts, but now that we have other F55xx parts like the F5510 I suspect we wanted to make it clear that these code examples include these newer parts.

Regards,

Katie

It would be nice to have TI also append the rev number to the subdir name.  I doubt many people keep the zip file once the files have been extracted.

Thanks for the clarification on the example code names. 

Thanks for the feedback, I'll pass it along.

Regards,

Katie

I just noticed ... the !ReadMe.txt  contains the old names. 

Katie Enderle said:

When the F5529 first came out, there were only F552x parts, but now that we have other F55xx parts like the F5510 I suspect we wanted to make it clear that these code examples include these newer parts.

Well, it's surprising anyway that the 551x/552x datasheet is not for the 5510 (the 5510 belongs to the 550x sub-family). The naming of new MSP devices gets more and more inconsistent. It may work if you use only one MSP and download the one datasheet you need, but when you work with multiple devices (or build-up a library like I did, for reference), you often open the wrong datasheet.

There is a problem with your website.  The example code zip file I downloaded from the Msp430f5529 website contained files labeled MSP430F55xx ... but the !ReadMe.txt file contains files labeled MSP430F552x.

Which is correct?  When will the website be fixed?

Which is correct?

As stated above, the code included in the online zip file download here is the most current code examples for the part you are using (whatever version is on the product page will always be the latest one). This code is what you should use. The 55xx naming convention vs. 552x in the readme is just a name change and does not affect the contents or functionality of the files. Alternately, you can use the code examples found in MSP430ware.

-Katie

Looking back at previous posts ... if I understand correctly, the 55xx is for 552x parts ... but not for 551x parts.  The 550x is for 550x parts and 551x parts.  Correct?

I'm not using CCSv5.  Thanks for the clarification ... clear and concise.

One more suggestion.  It would be good if this info were included in the ReadMe.txt file.  That would be very helpful for customers.  Will this be forwarded to the appropriate people?

I suppose I need to un-check "answered" for TI folks to see this message.