Support for the ScatterWeb Modular Sensor Board 430. More...
Support for the ScatterWeb Modular Sensor Board 430.
|Frequency||up to 8 MHz|
|Timers||2 (2x 16bit)|
|ADCs||1x 8 channel 12-bit|
|Vcc||1.8 V - 3.6 V (battery holder board provides 3.0 V)|
|User Guide MCU||User Guide|
The GPIOs on the MSP430F1612 only have two MUX settings: Being used as digital input/output or routed to a peripheral. The MCU has two universal serial synchronous/asynchronous communication interfaces (USARTs), which can be used to provide either an UART, an SPI, or (only in case of USART0) an I2C bus. Every USART signal is available at exactly one GPIO pin.
The UART exposed via the battery holder board (P3.6 and P3.7) can only be provided via USART1. In order to support asynchronous reception (e.g. to allow interaction via the shell), USART1 needs to be continuously configured as UART and cannot be used to provide an SPI bus.
The SPI bus connected to the SD card socket (P5.1, P5.2, and P5.3) can only be provided via USART1. Hence, it is not possible to use SPI bus connected to the SD card socket while the UART used for
stdio is in use, as they use the same USART. They could be used at the same time, if module
stdin is not used (the UART is output only). However, sharing USARTs is not yet implemented.
The SPI bus of the CC1020 transceiver (used for configuration only) is connected to pins P2.0, P2.1, and P2.3. Those pins are not connected to either USART, so no hardware SPI can be used to interact with the transceiver. However, the SPI is only used for configuration and control of the transceiver, so using a slow bit-banging SPI bus won't affect the performance of the transceiver, other than for quick power down after transmission or channel hopping. A second two wire serial interface (not I2C or compatible) is used to feed data into the CC1020 or read data from the CC1020. The serial clock is driven by the transceiver and the MCU needs to keep up with providing the frames to send bit by bit. Unlike modern transceivers, the CC1020 has no frame buffer and the MCU needs to control the transmission and reception on the bit level.
The pins above the JTAG header with the pin closest to the power supply switch being denoted as Pin 1, the signals are as follows:
The battery holder board contains a 3V power regular that powers the MSB-430 board via 3V pin (pin 1 on JP2). The switch at the bottom can be used to select the input voltage of that power regulator: If the switch is in the position towards the daughter board, it will use the 5V pin of the header above the JTAG header as power supply, otherwise the batteries are used as power supply.
Place the MSB-430 board into the batter holder board with the SD card socket facing towards the battery holder board and the (likely unpopulated) antenna connector facing away from the switch and JTAG-connector of the battery holder board. (As shown in the picture at the top of the page.)
Afterwards, connect a JTAG debugger supported by mspdebug; by default the Olimex MSP430-JTAG-Tiny is assumed, which is among the less expensive options.
MSPDEBUG_PROGRAMMERto the correct value via an environment variable or as parameter to make. E.g. use
make BOARD=msb-430 MSPDEBUG_PROGRAMMER=bus-pirateto flash using the bus pirate.
Once the board is firmly connected in the battery holder and the JTAG cable is connected, just run
in the application's directory.
stdio is available via the UART interface with
RXD = P3.7 (pin 35 on the header) and
TXD = P3.6 (pin 34 on the header) at 115,200 Baud.
The easiest way is to connect an USB TTL adapter (such as the cheap
ch341 based adapters) to the battery holder board as follows:
|Central definitions for the ScatterWeb MSB-430 board. |
|MSB-430 peripheral configuration. |