On Thu, Jul 21, 2011 at 12:08 PM, Emanuele Alidori <
[email protected]> wrote:

> Hi all, I'm planning to develop a demoboard, starting from the
> MSP430P1611 development board
>

why the 1611?   The 1611 is now a days a very old chip with significant
issues that newer chips fix.

What are you trying to accomplish by chosing the 1611?   What problem are
you trying to solve?


> [http://www.olimex.com/dev/msp-p1611.html], the CC2420EMK
> [http://focus.ti.com/docs/toolsw/folders/print/cc2420emk.html] and the
> M25P80 flash module.
> Now, my question is: "which are the other components I have to take in
> consideration to be phisically able to compile and download an
> application on the my future demoboard?"
> I saw TelosB uses an USB interface for the code's compiling and
> downloading.
>

The telosb uses a USB chip coupled with some circuitry to enable the TI BSL
buried in the chip.

We use the JTAG port to debug as well as load code into the chips.   We are
currently using the msp430f5438.  One of the advantages of the 5438 is it
has 8 USCI ports which elimates most cases of needing an arbiter which is a
big win.

The thing to do is study the telosb schematic and understand the basic
blocks and what they are used for.   Then you only need to implement blocks
that you actually need.

In other words what components you need really depends on what you are
doing.   The simplest program (short of Null) is Blink and it needs the
clock for the cpu, timing for Tmilli, and a LED to blink.

eric


> Thanks in advance.
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to