Rei Vilo

Information to Provide When Asking for Help

6 posts in this topic

When you post a question asking for help, please provide minimal information about your configuration, both hardware and software, including:

  • model of LaunchPad used and revision number
  • model of the MCU used
  • model of BoosterPack used or model of the sensor or actuator or screen
  • optionally, links to the sensor or actuator or screen data sheet
  • name and version of the IDE used 
  • OS the IDE is running on
  • whenever possible, minimal code to replicate the issue
  • optionally, all kinds of measures that may be useful, like logic analyser trace, oscilloscope screen-shots, ...
Example:

  • LaunchPad MSP430G2 revision 1.5
grahamf72 and abecedarian like this

Share this post


Link to post
Share on other sites

Yes, intelligence dictates that for one to receive the most intelligent answers, one must ask questions in the most intelligent manner, providing as much information as possible.

Otherwise, answers will likely be just as vague as the question.

Share this post


Link to post
Share on other sites

Add to that, if you are using the MSP430G2 launchpad, indicate which mcu you have plugged in. There is a world of difference between the capabilities of the 2231, 2452 & 2553.

 

 

Sent from my iPad using Tapatalk

Rei Vilo likes this

Share this post


Link to post
Share on other sites

Add to that, if you are using the MSP430G2 launchpad, indicate which mcu you have plugged in. There is a world of difference between the capabilities of the 2231, 2452 & 2553.

 

 

Sent from my iPad using Tapatalk

 

Thanks, added!

Share this post


Link to post
Share on other sites

 

Nice!

 

 

 

Before You Ask

Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following:

  1. Try to find an answer by searching the archives of the forum you plan to post to.

  2. Try to find an answer by searching the Web.

  3. Try to find an answer by reading the manual.

  4. Try to find an answer by reading a FAQ.

  5. Try to find an answer by inspection or experimentation.

  6. Try to find an answer by asking a skilled friend.

  7. If you're a programmer, try to find an answer by reading the source code.

Copyright

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now