Hello,
My question is, is the processor MSP430F5438A supported by tinyos? How does
one take compile apps for that target?
I am attempting to add a new platform to my tinyos installation. The mote I
want to add support for is a Texas Instruments CC1180DK_DB mote. It has an
MSP430F5438A
You should take a look at the fine work Eric has done:
https://github.com/tp-freeforall/prod
/tos/platform/mm5s/
Regards,
--Antonio
On Tue, Apr 9, 2013 at 9:09 AM, Tim Godfrey timothy.godf...@gmail.comwrote:
Hello,
My question is, is the processor MSP430F5438A supported by tinyos? How
Hi there,
the processor itself has some working code in the following repository:
https://github.com/tp-freeforall/prod (I'm not sure if it's the same
you've used.)
As for the CC1180 radio I don't know about any implementation. I've
tried to interface MSP430F5438a with CC2520 (CC2520 has an
On Tue, Apr 9, 2013 at 12:09 AM, Tim Godfrey timothy.godf...@gmail.comwrote:
Hello,
My question is, is the processor MSP430F5438A supported by tinyos? How
does one take compile apps for that target?
I am attempting to add a new platform to my tinyos installation. The mote
I want to add
On Tue, Apr 9, 2013 at 12:36 AM, Erdélyi Ádám [Edöm]
erdelyiadam.e...@gmail.com wrote:
Hi there,
the processor itself has some working code in the following repository:
https://github.com/tp-freeforall/prod (I'm not sure if it's the same
you've used.)
As for the CC1180 radio I don't know
OK, I've done everything. Now it tells me there's no rule to make « micaz »
target.
De : Eric Decker [mailto:cire...@gmail.com]
Envoyé : lundi 8 avril 2013 19:11
À : MICHARD Romain 231795
Cc : Srikanth Nori; tinyos-help@millennium.berkeley.edu
Objet : Re: [Tinyos-help] Missing header files when
Call for Papers: The Fifth Workshop on Real-World Wireless Sensor Networks
==
19-20 September 2013
Como Lake (Italy)
http://realwsn.deib.polimi.it
Follow
Dear all,
I am wondering how to integrate general additions (modules, interfaces,
etc.) to the TinyOS tool chain, so that they are
- available for any application and
- overwrite standard TinyOS implementations.
I'll (try to) give an example of what I want to achieve:
Say I implemented a
Hi Christian,
I would put it into the folder of that particular platform and then
rewrite the .platform file accordingly. As far as I know the path list
in the .platform file is a priority list, so if you put the folder of
your own version of McuSleepC before the general one it will override
I don't know what to tell you other than follow the instructions
sounds like you don't have the environment variables set up correctly.
If you don't know what I'm talking about, then follow the instructions
On Tue, Apr 9, 2013 at 1:32 AM, MICHARD Romain 231795 romain.mich...@cea.fr
wrote:
Hello,
Is there a way to debug the app.c file generated from the NesC code?
I have referenced the link provided in this message from 2008:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2008-May/033178.html
The link provides a number of ways to debug the NesC code, but not the app.c
On Tue, Apr 9, 2013 at 9:04 AM, Erdélyi Ádám [Edöm]
erdelyiadam.e...@gmail.com wrote:
Hi Christian,
I would put it into the folder of that particular platform and then
rewrite the .platform file accordingly. As far as I know the path list
in the .platform file is a priority list, so if you
I use a JTAG h/w pod running mspdebug as a gdb server.
I then use msp430-gdb to talk to that server.
While this is technically debugging the app.c output, there are references
to the original nesc files.
see
https://github.com/tp-freeforall/prod/blob/tp-master/tos/chips/msp430/99_gdb/00_README
13 matches
Mail list logo
