hmmm...I haven't used SPI, on anything actually, but it
looks like "they" did not bring all the signals you need
to the I/O headers. According the the MSP430 Users Guide,
I think you need SOMI0 which is named "RADIO_SO" on the
schematic. You do get access to SOMO0 and UCLK0 as RADIO_SI
and RADIO_SCLK, and I think you can use them for I2C, but
there's not enough wires for SPI. I believe, from a quick
glance at the spec sheet, that an internal UART is used
to do the actual comm but the I/O pins are those of the
RADIO_* variety.
The CC2420 radio chip interfaces via SPI so you would need
to do arbitration in any case.
MS
Marcelo Coelho wrote:
> Thanks for the quick replies!
>
>>From what I understood, the SPI functionality is provided by the UART0 tx/rx
> ports and the I2Cclk (for clock source) and I2Cdata (for the slave select)
> in the 10pin expansion header.
>
> Michael: I liked the pinout that you pointed, specially the description of
> the UART1TX ("?wtf?") :p
>
>
> Cheers,
> Marcelo Coelho
>
> -----Original Message-----
> From: Michael Schippling [mailto:[email protected]]
> Sent: segunda-feira, 1 de Agosto de 2011 17:04
> To: Thomas Schmid
> Cc: Marcelo Coelho; [email protected]
> Subject: Re: [Tinyos-help] Pinouts of a TelosB SPI bus
>
> And here's a list of controller and header assignments:
> http://www.etantdonnes.com/Motes/TMOTEpins.txt
> MS
>
>
> Thomas Schmid wrote:
>> http://www.snm.ethz.ch/pub/uploads/Projects/tmote_sky_schematic.pdf
>>
>> - Thomas
>>
>>
>>
>>
>>
>> On Mon, Aug 1, 2011 at 8:24 AM, Marcelo Coelho
>> <[email protected]> wrote:
>>> Hi!
>>>
>>>
>>> I'm trying to add Ethernet communication functionality to a Crossbow
>>> TelosB mote. To accomplish that, I intend to use an Arduino Ethernet
>>> shield (and it's schematics), but don't have the pinouts of the TelosB
> mote.
>>> Do you know the pinouts of the TelosB SPI bus?
>>>
>>> Thanks in advance!
>>>
>>>
>>> Best regards,
>>> Marcelo Coelho
>>>
>>>
>>> ________________________________
>>> DISCLAIMER: This message is confidential and may contain privileged
> information. It is for use only by the people or entities to whom it is
> addressed. If you are not an intended recipient, you should not disclose,
> distribute, copy, print, rely on or otherwise make use of this message. If
> an addressing or transmission error has misdirected it to you we would be
> grateful if you would please notify the sender by return, before deleting it
> from your system.
>>> ________________________________
>>> Are you controlling information disclosure? Decide what you need to keep
> secret and enforce it with csSECURE. See how at www.csSECURE.net.
>>> _______________________________________________
>>> Tinyos-help mailing list
>>> [email protected]
>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-h
>>> elp
>>>
>> _______________________________________________
>> Tinyos-help mailing list
>> [email protected]
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> ________________________________
> DISCLAIMER: This message is confidential and may contain privileged
> information. It is for use only by the people or entities to whom it is
> addressed. If you are not an intended recipient, you should not disclose,
> distribute, copy, print, rely on or otherwise make use of this message. If an
> addressing or transmission error has misdirected it to you we would be
> grateful if you would please notify the sender by return, before deleting it
> from your system.
> ________________________________
> Are you controlling information disclosure? Decide what you need to keep
> secret and enforce it with csSECURE. See how at www.csSECURE.net.
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
