June 20th
Return of the Code Inspector
During my perusal of the basic_wifi_application and other MSP430 examples I have noticed small annotation errors and minor "assumption" errors (some of which I have previously mentioned).
One such example is the standard blink led demonstration. It assumes that there are always LEDs connected to P1.0 and P1.1.
This is not the case with the MSP430 Fraunchpad where the equivalent LEDS are connected to PJ.0
This is minor but could catch a novice out.
More importantly to me is the basic_wifi_application. Apart from misspelling 'the' several times, reference to the LEDs are incorrect. They should be;
| Code Ref | PCB Ref | I/O Pin | Function |
|---|---|---|---|
| LED4 | (In a comment - actually means LED8) | n/a | n/a |
| LED5 | LED6 | P3.5 | WLAN Successful |
| LED6 | LED7 | P3.6 | SMART Config Process active |
| LED7 | LED8 | P3.7 | CC3000 successful connection |
Watch out for Boobie Traps!
The MSP430 contains a number of peripherals that are connected to I/O Pins.
| I/O Pin | Description |
|---|---|
| P2.7 | Enable Accelerometer and Thermistor (and LDR if installed) |
| P3.0 | Accelerometer X Output (Analog) |
| P3.1 | Accelerometer Y Output (Analog) |
| P3.2 | Accelerometer Z Output (Analog) |
| *P3.3 | LDR Output (Analog) [If installed] |
| P1.4 | Thermistor Output (Analog) |
| *PJ.4 | 32.768kHz Crystal [if installed] |
| *PJ.5 | 32.768kHz Crystal [if installed] |
| P2.1 | TXD to USB |
| P2.0 | RXD to USB |
Also watch out for pins connected to WiFi-SL Module when used. Details of this are in a previous blog entry.
Please note that not all MSP430 I/O pins are brought out the standard headers.
Some are brought out to optional headers (eZ-RF and TP12-TP15 pads under LEDs) and some like PJ.4 and PJ.5 not at all where you have to make your own arrangements (which could be to use the pads where the crystal would be soldered).
Note: This and some recent blogs may appear that I am repeating myself but I am documenting them down for easy reference.
