Here's a hard learned tip... when purchasing electronic devices for these types of projects, *always* ensure that you have a datasheet up front that you can review to ensure that it seems reasonably sane, and that you can understand at least the core information it contains.
I have written software across several languages for over a hundred random ICs and devices, and the only thing worse than no documentation, is poorly written documentation that is incorrect (nothing like the fun of debugging an IC to learn after three days of head-desking that the damned documentation failed to mention overlapping registers!).
Hopefully this device comes with proper docs, but in the future, solidify that fact up front if you carry on doing projects like this.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
