date:20120727

Re: [Tinyos-help] Deluge T2 and iris motes

2012-07-27 Thread Janos Sallai

Yann,

Thanks for reporting this issue. A quick recap, just for the record: a
recent change to chips/at45db/BlockStorageP.nc that allowed for
non-power-of-two page sizes broke deluge/tosboot on the iris and micaz
(probably other platforms, too), because deluge and tosboot were
expecting the page size to be 256.

For now, I reverted back to the old chips/at45db/BlockStorageP.nc,
which assumes that the page size is a power of 2. Deluge/tosboot needs
to be fixed post 2.1.2. I'm posting a google code issue, as well.

Janos


On Fri, Jul 27, 2012 at 8:54 AM, Yann Le Corre  wrote:
> Hi all,
>
> I think I have solved my issues with deluge T2 and iris motes with
> Ubuntu 11.04.
> I used the git repository (checked out on July 13th 2012) and all the
> latest versions of avr tools (locally recompiled with gcc4.6.1).
>
> I found 2 bugs in this version of the database/tools compiled for IRIS
> target. They are all related to the external flash (AT45DB) having pages
> of 264 bytes instead of 256 bytes:
>
> - the function StorageMap.getPhysicalAddress() in
> tos/lib/net/Deluge/BlockStorageManagerP.nc is obviously written for
> AT45DB with 256-bytes pages.
>
> - the function ExtFlash.startRead() in tos/lib/tosboot/at45db does not
> work for 264-bytes pages.
>
> I think the root of all evil lies in function multiplageContinue() in
> chips/at45db/BlockStorageP.nc. The version that is used in the Xubuntu
> vmware image (which does work), is written for 256-bytes pages while the
> version in the git repository is designed for 264-bytes pages.
>
> I guess we should either revert back to the old version of
> multiplageContinue(), or update StorageMap.getPhysicalAddress() and
> ExtFlash.startRead().
>
> I would be glad to submit/discuss my corrections with an official
> maintainer of tinyOS/Deluge or anybody with needs them.
>
> Regards,
>
> Yann
>
>
>
> On 07/10/2012 09:54 PM, András Bíró wrote:
>> Hi Guys,
>>
>> It's seems there is a bunch of  deluge related problem recently, and
>> altough I don't really know the source of your problems, Deluge T2
>> certainly works. I didn't use it on memsic motes for quite  a long
>> time (although I could test it on irises if you wish), but I've ported
>> it to the motes our company manufactures, and recently I programmed
>> about 150 motes with it (all of them in the same room).
>> By the way, I'm using Arch linux, and the newest python2 package on it
>> for tinyos python scripts, I never had any problem with the tos-deluge
>> - mote connection.
>> Debugging a deluge related problem is really painful, since it's quite
>> complex protocol, handling awful lot of data.
>> Some issues I had problems with:
>> -TOSH_DATA_LENGTH _must_ be the same on all motes. If the receiver's
>> TOSH_DATA_LENGTH is bigger than the sender's, the receiver fills the
>> remaining data with garbage, and that will cause crc error in the
>> bootloader. That means it will restart with the old image, redownload
>> the new, reboots, detects the crc error and so on.
>> -Deluge doesn't like if there's serious communication in the area. It
>> really slows down the downloading of the image (from two minutes to
>> fifteen-thirty), and worst of all, it also causes image crc errors
>> (not sure why, but at first we could only reprogram about 50 of the
>> 150 motes. Fortunately, we could disable almost all communication on
>> the motes).
>> -Image 0 is the golden image (1; 2 and 3 are general purpose images),
>> but it's not well designed. You have to inject the golden image
>> yourself, but at some point deluge will stop you to use it as the
>> other images, and I think that point is the dissemination. Therefor,
>> you have to inject it with serial on all motes (but I'm not sure, I
>> didn't really cared this issue)
>> -You also have to be extramly unfortunate, if you encounter a mote
>> automaticly programs itself with golden image. Tosboot only incrases
>> the gesture counter (which counts to 3, and when reaches 3, tosboot
>> will program the golden image) if ther was some problem during copying
>> a page from the external flash to the internal, but I never had such
>> problem. It does not protect your mote from redownloading a crc error
>> image again and again, which happens quite often however.
>>
>> Andris
>>
>> On Tue, Jul 10, 2012 at 4:54 PM, Yann Le Corre  wrote:
>>> Hi,
>>>
>>> It looks similar to what I have here.
>>> I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki.
>>> Everything seems to be working fine now. I can disseminate and execute.
>>>
>>> It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would
>>> be glad to help to solve them if anybody could give me some clues.
>>>
>>> Regards,
>>>
>>> Yann
>>>
>>>
>>>
>>>
>>> On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote:
>>>
>>> Hi,
>>>
>>> I have been having no success in using Deluge T2 with IRIS and MIB520. First
>>> I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu
>>> 12.04 LS and I installed

Re: [Tinyos-help] Deluge T2 and iris motes

2012-07-27 Thread Yann Le Corre

Hi all,

I think I have solved my issues with deluge T2 and iris motes with 
Ubuntu 11.04.
I used the git repository (checked out on July 13th 2012) and all the 
latest versions of avr tools (locally recompiled with gcc4.6.1).

I found 2 bugs in this version of the database/tools compiled for IRIS 
target. They are all related to the external flash (AT45DB) having pages 
of 264 bytes instead of 256 bytes:

- the function StorageMap.getPhysicalAddress() in 
tos/lib/net/Deluge/BlockStorageManagerP.nc is obviously written for 
AT45DB with 256-bytes pages.

- the function ExtFlash.startRead() in tos/lib/tosboot/at45db does not 
work for 264-bytes pages.

I think the root of all evil lies in function multiplageContinue() in 
chips/at45db/BlockStorageP.nc. The version that is used in the Xubuntu 
vmware image (which does work), is written for 256-bytes pages while the 
version in the git repository is designed for 264-bytes pages.

I guess we should either revert back to the old version of 
multiplageContinue(), or update StorageMap.getPhysicalAddress() and 
ExtFlash.startRead().

I would be glad to submit/discuss my corrections with an official 
maintainer of tinyOS/Deluge or anybody with needs them.

Regards,

Yann



On 07/10/2012 09:54 PM, András Bíró wrote:
> Hi Guys,
>
> It's seems there is a bunch of  deluge related problem recently, and
> altough I don't really know the source of your problems, Deluge T2
> certainly works. I didn't use it on memsic motes for quite  a long
> time (although I could test it on irises if you wish), but I've ported
> it to the motes our company manufactures, and recently I programmed
> about 150 motes with it (all of them in the same room).
> By the way, I'm using Arch linux, and the newest python2 package on it
> for tinyos python scripts, I never had any problem with the tos-deluge
> - mote connection.
> Debugging a deluge related problem is really painful, since it's quite
> complex protocol, handling awful lot of data.
> Some issues I had problems with:
> -TOSH_DATA_LENGTH _must_ be the same on all motes. If the receiver's
> TOSH_DATA_LENGTH is bigger than the sender's, the receiver fills the
> remaining data with garbage, and that will cause crc error in the
> bootloader. That means it will restart with the old image, redownload
> the new, reboots, detects the crc error and so on.
> -Deluge doesn't like if there's serious communication in the area. It
> really slows down the downloading of the image (from two minutes to
> fifteen-thirty), and worst of all, it also causes image crc errors
> (not sure why, but at first we could only reprogram about 50 of the
> 150 motes. Fortunately, we could disable almost all communication on
> the motes).
> -Image 0 is the golden image (1; 2 and 3 are general purpose images),
> but it's not well designed. You have to inject the golden image
> yourself, but at some point deluge will stop you to use it as the
> other images, and I think that point is the dissemination. Therefor,
> you have to inject it with serial on all motes (but I'm not sure, I
> didn't really cared this issue)
> -You also have to be extramly unfortunate, if you encounter a mote
> automaticly programs itself with golden image. Tosboot only incrases
> the gesture counter (which counts to 3, and when reaches 3, tosboot
> will program the golden image) if ther was some problem during copying
> a page from the external flash to the internal, but I never had such
> problem. It does not protect your mote from redownloading a crc error
> image again and again, which happens quite often however.
>
> Andris
>
> On Tue, Jul 10, 2012 at 4:54 PM, Yann Le Corre  wrote:
>> Hi,
>>
>> It looks similar to what I have here.
>> I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki.
>> Everything seems to be working fine now. I can disseminate and execute.
>>
>> It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would
>> be glad to help to solve them if anybody could give me some clues.
>>
>> Regards,
>>
>> Yann
>>
>>
>>
>>
>> On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote:
>>
>> Hi,
>>
>> I have been having no success in using Deluge T2 with IRIS and MIB520. First
>> I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu
>> 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2
>> runs on the mote, I inject the image and I read the flash successfully and
>> even mine doesn't give the error you mentioned (is it base station or not
>> ... ) but still after dissemination I can see other motes start to get the
>> image and write it down on their flash (the green LED blinks fast) but after
>> all no one reboots and execute the new image ... I kinda gave up on it, but
>> if anyone has a similar experience and knows how to solve these issues with
>> IRIS and Deluge T2, I appreciate ...
>>
>>
>> Regards,
>>
>>
>> Hamid Rafiei Karkvandi
>>
>>
>>
>>
>>
>> On Tue, Jul 10, 2012 at 7:40 AM, Yann Le Corre  wrote:
>>> Hi All,
>

Re: [Tinyos-help] is it possible to perform multihopping without using collection tree protocol?????????

2012-07-27 Thread Omprakash Gnawali

Yes, that is possible as long as you use some multi-hop routing
protocol. You don't have to use CTP.

- om_p

On Wed, Jul 11, 2012 at 3:59 AM, mamta_b  wrote:
>
> hi,
> i am confused that how to write an application which performs multihopping
> but without using collection tree protocol. is it possible to do that? i
> have gone through multihoposcilloscope and testnetwork applications both are
> using CTP. please help.
> --
> View this message in context: 
> http://old.nabble.com/is-it-possible-to-perform-multihopping-without-using-collection-tree-protocol--tp34144482p34144482.html
> Sent from the TinyOS - Help mailing list archive at Nabble.com.
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] implementation of a new routing algorithm

2012-07-27 Thread Omprakash Gnawali

Why do you want to implement your own routing protocol? I am assuming
the existing protocols don't meet your requirements. If so, what are
your requirements?

- om_p

On Tue, Jul 24, 2012 at 1:42 AM, mamta_b  wrote:
>
> hi friends,
> i have studied and tested multihoposcilloscope and testnetwork applications.
> now i want to implement my own routing algorithm but i am confused that from
> where to start, how to create different layers of nodes, how to store
> routing information tables in each node and broadcasting them. i am not
> coming up to the start point of implementing a new routing algo. please
> help.
> --
> View this message in context: 
> http://old.nabble.com/implementation-of-a-new-routing-algorithm-tp34203690p34203690.html
> Sent from the TinyOS - Help mailing list archive at Nabble.com.
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] RS232 Communication Problem

2012-07-27 Thread WSNDeveloper WSN

Dear all,

Has anybody solved the problem to communicate Telosb mote to any RS232
Device different than PC?

I would like to integrate a external sensor to Telosb mote via RS232
interface. In order to to that, I first tried to communicate Telosb mote
with PC (using a Serial monitor software) and everything was right. After
that, I tested to communicate PC and RS232 sensor and everything was right.
Finally, when I tried to send from Telosb the same message as sent from PC
to the RS232 sensor I don't get any response from RS232 device. I am
thinking about three possibilities:

- Signal amplification (the mote could not provide the same level as the PC
can)
- Handshaking issue (The PC is sending handshaking bytes as DTE which are
not sent by the mote)
- Synchronization issue

Could anybody provide me any clue about this issue?

Thanks a lot
David
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TKN154: What I am receiving?

2012-07-27 Thread Jan Hauer

> Test 2: LISTEN JAVA (5 data frames are depicted)
>
> $ java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telosb
>
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 01 23 02 23 03 23 04 23 06 EA

This packet is not an AM-packet, because the first byte is not zero
(c.f. 
http://docs.tinyos.net/tinywiki/index.php/Mote-PC_serial_communication_and_SerialForwarder).
You are using apps/tests/tkn154/packetsniffer, which doesn't use the
default serial stack, but wires to Serial802_15_4C (in
tos/lib/serial). Take a look
apps/tests/tkn154/packetsniffer/README.txt, it explains the packet
format and points you to a c-file that you can use to extract the
data.

If you want to send standard AM-Packets (and use java
net.tinyos.tools.Listen) wire to SerialActiveMessageC instead of
Serial802_15_4C (see example in apps/tests/TestSerial).

Jan

On Fri, Jul 27, 2012 at 12:10 PM, David Rodenas  wrote:
> Hi all
>
> Sorry for the length, but I thing that it was necessary to explain my
> concern. I've programmed a telosb acting as a transmitter that sends
> periodically a broadcast message to another telosb acting as a network
> coordinator (and also as a reciver). I am using the TKN154 libraries. The
> main network parameters are:
>
> RADIO CHANNEL is 26,
> PAN ID is 0x4927,
> COORDINATOR ADDRESS is 0x6287,
> DEVICE ADDRESS is 0x6245,
> TRANSMISSION is broadcast (daddr is 0x).
>
> The payload contains two fields: 1) the device address (0x6287) and 2) four
> uint16_t values as network data (0x2301 0x2302 0x2303 0x2304)
>
> The coordinator app is based on the packetsniffer app (apps/tests/tkn154)
> with some modifications. What I want is to send every data frame received by
> the coordinator through the serial port to my laptop. Thereby, here is the
> part of the code that conducts this issue:
>
> event message_t* MCPS_DATA.indication ( message_t* frame_ ){
>   call Leds.led1Toggle();
>   if (call Queue.enqueue(frame_) != SUCCESS) {
> call Leds.led0On(); // overflow
> return frame_;
>   } else {
> post serialSendTask();
> return call Pool.get();
>   }
> }
>
> task void serialSendTask()
> {
>   message_t* frame;
>   uint8_t headerLen;
>   uint8_t payloadLen;
>   uint8_t serialLen;
>   uint8_t *header;
>   uint8_t *payload;
>   uint8_t i;
>   if (call Queue.empty() || m_serialSendBusy)
> return;
>
>   frame = call Queue.head();
>
>   headerLen = call Frame.getHeaderLength(frame);
>   payloadLen = call Frame.getPayloadLength(frame);
>   header = call Frame.getHeader(frame);
>   payload = call Frame.getPayload(frame);
>
>   /*
>   // Test 1: printf
>   printf("MHRLen: %d\n", headerLen);
>   printf("MHR: ");
>   for (i=0; i printf("0x%02X ", header[i]);
>   }
>   printf("\n");
>   printf("PayloadLen: %d\n", payloadLen);
>   printf("Payload: ");
>   for (i=0; i printf("0x%02X ", payload[i]);
>   }
>   printf("\n\n");
>   */
>
>   // Test 2: java Listen
>   serialLen = headerLen + payloadLen;
>   m_serialSendBusy = TRUE;
>   if (call SerialSend.send(frame, serialLen) != SUCCESS)
> report_received();   //call Leds.led2Toggle();
> }
>
> As you can see, I carry out two tests: 1) by using the printf libraries, I
> represent the content of the header and the payload fields; and 2) I use the
> Listen java app to see what I receive from the serial port. The results are
> the following:
>
> Test 1: PRINTF (only one data frame is depicted since the transmission
> conditions and network data are always the same)
>
> $ java net.tinyos.tools.PrintfClient -comm serial@/dev/ttyUSB0:telosb
>
> MHRLen: 9
> MHR: 0x41 0x88 0x90 0x27 0x49 0xFF 0xFF 0x45 0x62
> PayloadLen: 10
> Payload: 0x45 0x62 0x01 0x23 0x02 0x23 0x03 0x23 0x04 0x23
>
> I've not checked the header fields but, a priori, the result is what I
> expected.
>
>
> Test 2: LISTEN JAVA (5 data frames are depicted)
>
> $ java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telosb
>
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 01 23 02 23 03 23 04 23 06 EA
> 00 00 00 00 00 00 00
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 00 00 02 23 03 23 04 23 08 EB
> 00 00 00 00 00 00 00
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 00 00 02 23 03 23 04 23 0C E9
> 00 00 00 00 00 00 00
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 00 00 02 23 03 23 04 23 09 EA
> 00 00 00 00 00 00 00
> 02 00 00 00 00 00 00 00 00 00 00 00 00 45 62 00 00 02 23 03 23 04 23 0C EB
> 00 00 00 00 00 00 00
>
> I am aware of that the first byte is the AM type (0x02). In addition, the
> payload is successfully received (45 62 01 23 02 23 03 23 04 23). However,
> where is the header? And the latest zeros? and what do "06 EA", "08 EB", "0C
> E9", "09 EA", "0C EB" mean?
>
> I'd like to know what I am doing wrong. In this sense, all the help possible
> would be appreciated.
>
> Regards
>
> David
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_

Re: [Tinyos-help] Problem with printf

2012-07-27 Thread JeongGil Ko

Tyler,

When running with Cooja, it is best that you wire SerialPrintfC rather than 
PrintfC.

-John

--
JeongGil Ko, Ph.D.
Researcher
Electronics and Telecommunications Research Institute (ETRI)
http://sites.google.com/site/jeonggilko/

On Jul 26, 2012, at 7:12 PM, Tyler Sundance wrote:

> Hello Everybody
> 
> I compiled the printf example application for the telosb mote.
> 
> When i run the program in the cooja simulator i get the following output:
> 
> ~EdHi I am writing to you from ~~Edmy TinyOS application!!
> HereF~~Ed is a uint8: 123
> Here is a u~~Edint16: 12345
> Here is a uint3J~~Ed2: 1234567890
> 
> I get these wrong "~~Ed" characters.
> 
> I have the following tools installed
> 
> ncc: 1.2.4
> nescc: 1.3.4
> msp430-gcc: msp430-gcc (GCC) 3.2.3
> 
> Does anybody know what could be the problem ?
> 
> Thank you in advance.
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> 


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Building your own Motes

2012-07-27 Thread João Gonçalves

Hello Siddharth
for manufacturing your pcbs you can use pcbcart:
http://www.pcbcart.com

I got them to produce and solder 20 motes I designed in the university.
Cheap and not so bad service for the price. They will always try to use
similar components they have in stock instead of yours however. But they
always ask before making any change in the bill of materials.

If you want to design your own mote, you need of course some pcb layout
editor to design your platform. I use Altium designer.

A starting point could be to look at the schematics and layouts of some
comercial platforms like telos or mica, this way you cant get the idea of
what the platform hardware is normally composed of.
You can take a look here:
http://www.tinyos.net/scoop/special/hardware#telosplatform


2012/7/26 João Gonçalves 

>
>
> 2012/7/26 Johny Mattsson 
>
>> On 26 July 2012 03:13, Siddharth Dagar  wrote:
>>
>>> If anybody knows anything about mote development (hardware), or if
>>> anybody knows about any online sites where they go into detailed mote
>>> hardware component description, please guide me.
>>>
>>
>> If you want to get started with hardware tinkering, the Arduino is a
>> pretty good start. Lots of available documentation and examples, and it's
>> friendly to beginners.
>>
>> Once you feel comfortable building things and are no longer frying
>> components too frequently, you might find the Atmel ATmega128RFA1 a good
>> starting point for a mote. The chip already has TinyOS support, and with
>> the built-in radio you avoid a degree of complexity in setting up a new
>> TinyOS platform definition.
>>
>> Be forewarned that it's a fair bit of work in getting a new platform set
>> up and working from scratch - debugging hardware is "fun", and unless you
>> have a nice set of tools at your disposal (like a good DSO), you'll be
>> flying dark for a lot of the time. That said, if you want a bit of a
>> challenge and have the time for it, you'll learn a lot and probably have a
>> whole lot of fun too :)
>>
>> Good luck!
>>
>> Cheers,
>> /Johny, who knows just enough about hardware to be dangerous to
>> components...
>> --
>> Johny Mattsson
>> Senior Software Engineer
>>
>> DiUS Computing Pty. Ltd.
>> *where ideas are engineered
>> *
>>
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Building your own Motes

2012-07-27 Thread João Gonçalves

2012/7/26 Johny Mattsson 

> On 26 July 2012 03:13, Siddharth Dagar  wrote:
>
>> If anybody knows anything about mote development (hardware), or if
>> anybody knows about any online sites where they go into detailed mote
>> hardware component description, please guide me.
>>
>
> If you want to get started with hardware tinkering, the Arduino is a
> pretty good start. Lots of available documentation and examples, and it's
> friendly to beginners.
>
> Once you feel comfortable building things and are no longer frying
> components too frequently, you might find the Atmel ATmega128RFA1 a good
> starting point for a mote. The chip already has TinyOS support, and with
> the built-in radio you avoid a degree of complexity in setting up a new
> TinyOS platform definition.
>
> Be forewarned that it's a fair bit of work in getting a new platform set
> up and working from scratch - debugging hardware is "fun", and unless you
> have a nice set of tools at your disposal (like a good DSO), you'll be
> flying dark for a lot of the time. That said, if you want a bit of a
> challenge and have the time for it, you'll learn a lot and probably have a
> whole lot of fun too :)
>
> Good luck!
>
> Cheers,
> /Johny, who knows just enough about hardware to be dangerous to
> components...
> --
> Johny Mattsson
> Senior Software Engineer
>
> DiUS Computing Pty. Ltd.
> *where ideas are engineered
> *
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Building your own Motes

2012-07-27 Thread Janos Sallai

Siddharth:

The easiest way to go is using a pre-built module, that you can just
solder on your custom-designed PCB. The IRIS and the micaz are
available as an OEM module from MEMSIC. The Zigbit, which has the same
MCU and radio as the IRIS, is available from Atmel.

Alternatively, you can build your own boards from proven designs that
are free. The EPIC (http://www.cs.berkeley.edu/~prabal/projects/epic/)
is a good example of that.

Janos



On Wed, Jul 25, 2012 at 12:13 PM, Siddharth Dagar
 wrote:
>
> Hello all
> This is not directly related to TinyOS but I think this is probably the best
> place to get help. I have been using TelosB motes for building a home
> automation system. However, I'd like a lot of other functionalities which
> are not offered by the TelosB modules. I wanted to build my own motes from
> scratch, utilizing only the components which are required for my project.
>
> Can somebody help me out a little in this? If anybody knows anything about
> mote development (hardware), or if anybody knows about any online sites
> where they go into detailed mote hardware component description, please
> guide me.
> Thanks!
>
> --
> Siddharth Dagar
> IIT Kharagpur
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] PhoneSense 2012 (SUBMISSION EXTENSION: 1 Aug 2012) w/ SenSys 2012, Toronto, Canada, 6 Nov 2012

2012-07-27 Thread SenSys'12 Publicity

PhoneSense 2012: 3rd International Workshop on Sensing Applications on
Mobile Phones (with SenSys 2012)
6 November 2012
Toronto, Canada

http://research.microsoft.com/en-us/um/redmond/events/phonesense2012

Important Dates
---
• Paper submissions due: 1 August 2012, 9:00 p.m. PDT  (NEW - EXTENSION)
• Notification of acceptance: 12 September 2012

Organizers
--
Program Co-Chairs
David Chu (Microsoft Research)
Ramesh Govindan (USC)

Program Committee
Gaetano Borriello (University of Washington)
Eyal de Lara (University of Toronto)
Deborah Estrin (UCLA)
Deepak Ganesan (UMass Amherst)
Shyamnath Gollakota (MIT)
Ben Greenstein (Google)
Richard Han (University of Colorado)
Anthony LaMarca (Intel Labs)
Jie Liu (Microsoft Research)
Alexander Varshavsky (AT&T Labs)

Steering Committee
--
Deborah Estrin (UCLA)
Aman Kansal (Microsoft Research)
Deepak Ganesan (UMass Amherst)

Overview

Mobile phones provide a widespread platform for deploying sensing
applications. Multiple factors, including the large number of sensors
available on phones with new ones being introduced in newer models,
proximity to user’s immediate environment, broadband connectivity, and
the potential to provide actionable information, make the phone a
compelling platform for many sensing applications. The emergence of
the mobile computing cloud further expands the scope of possible use
cases. Sensing applications can use the mobile phones and cloud
resources to sense, mine, and learn human behaviors and intentions to
provide personalized feedback and persuasion. Example sensing
application domains include personalized mobile information delivery,
context aware social networking, healthcare, games and entertainment,
education, device and environment customization, safety, and mobile
business.

The efficient and effective design of mobile sensing applications
opens up many interesting technical challenges. The PhoneSense
workshop promotes exchange of ideas among academic and industrial
researchers in research areas such as sensing, mobile computing,
location, energy efficiency, data management, data mining, machine
learning, inference, privacy, user incentives and applications.

The workshop considers hot topics, position papers, novel ideas,
in-progress work on system architecture, enabling technologies, and
emerging applications. Topics of interest include, but are not limited
to:

• Novel Applications
• Mining large scale sensor and location data
• Mobile cloud and sensing interfaces
• Incentive models for mobile data collection
• Interaction between phones and humans
• Novel mobile sensor accessories
• Sensing and machine learning techniques
• Persuasion models and techniques to close the loop with users
• Privacy
• Participatory sensing, crowdsourcing, and opportunistic sensing paradigms
• Activity recognition and subjective sensing
• Programming models
• Experiment and campaign design
• Integration of on-phone and off-phone sensing
• Personalization, geo-targeting
• Personal health monitoring using mobile phones
• Data quality issues
• Experience with app store delivery systems and large scale deployment

What to Submit
--
Submissions must be at most 5 single-spaced 8.5" x 11" pages,
including figures, tables, and references, two-column format, using
10-point type with ACM proceedings format. Submissions will be
reviewed by the program committee for novelty, relevance, and quality.

PhoneSense is single-blind, so authors should include their names on
their paper submissions.  For more details, see
http://research.microsoft.com/en-us/um/redmond/events/phonesense2012.

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Blip with shimmer motes

2012-07-27 Thread farrukh munir

Hi
I was trying to implement BLIP on shimmer motes and tried to do following

*Description :*
Shimmer Mote >>> Routing Node
SPAN module ->>> Edge Router that is connected to the Laptop.

In shimmer motes I have complied and installed app name UDPEcho that is in
TinyOS-2.1.1 app folder while in SPAN module I complied and installed
IPBasestation app.

but when i Compiled and ran the routing driver command

*sudo driver/ip-driver /dev/ttyUSB* shimmer on laptop gives as following
errors

tiny2@ShimmerLive:/opt/tinyos-2.1.1/support/sdk/c/blip$ sudo
driver/ip-driver /dev/ttyUSB1 shimmer
2012-07-26T16:16:44.691GMT: INFO: Read config from 'serial_tun.conf'
2012-07-26T16:16:44.691GMT: INFO: Using channel 15
2012-07-26T16:16:44.691GMT: INFO: Retries: 5
2012-07-26T16:16:44.691GMT: INFO: telnet console server running on port 6106
2012-07-26T16:16:44.735GMT: INFO: created tun device: tun0
*2012-07-26T16:16:49.858GMT: FATAL: configuring interface failed! aborting!*

Can you help me regarding that ? Also any advice to Implement Blip  using
span and shimmer motes



Regards
Farrukh Munir
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TKN154: What I am receiving?

2012-07-27 Thread David Rodenas


Hi all
Sorry for the length, but I thing that it was necessary to explain my concern. 
I've programmed a telosb acting as a transmitter that sends periodically a 
broadcast message to another telosb acting as a network coordinator (and also 
as a reciver). I am using the TKN154 libraries. The main network parameters 
are: 
RADIO CHANNEL is 26,PAN ID is 0x4927,COORDINATOR ADDRESS is 0x6287,DEVICE 
ADDRESS is 0x6245,TRANSMISSION is broadcast (daddr is 0x).
The payload contains two fields: 1) the device address (0x6287) and 2) four 
uint16_t values as network data (0x2301 0x2302 0x2303 0x2304)
The coordinator app is based on the packetsniffer app (apps/tests/tkn154) with 
some modifications. What I want is to send every data frame received by the 
coordinator through the serial port to my laptop. Thereby, here is the part of 
the code that conducts this issue: 
event message_t* MCPS_DATA.indication ( message_t* frame_ ){  call 
Leds.led1Toggle();  if (call Queue.enqueue(frame_) != SUCCESS) {call 
Leds.led0On(); // overflowreturn frame_;  } else {post 
serialSendTask();return call Pool.get();  }}  task void serialSendTask() {  
message_t* frame;  uint8_t headerLen;   uint8_t payloadLen;   uint8_t 
serialLen;   uint8_t *header;  uint8_t *payload;  uint8_t i;   if (call 
Queue.empty() || m_serialSendBusy)return;frame = call Queue.head(); 
   headerLen = call Frame.getHeaderLength(frame);  payloadLen = call 
Frame.getPayloadLength(frame);  header = call Frame.getHeader(frame);  payload 
= call Frame.getPayload(frame); /*  // Test 1: printf  printf("MHRLen: 
%d\n", headerLen);  printf("MHR: ");  for (i=0; i___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

2012-07-27 Thread David Rodenas

Hi Erik
thanks, your email was really useful. As you say, what I did was rocket 
science, but I could not be able to find another solution because of my poor 
knowledge of linux. 
Bye
David

Date: Fri, 27 Jul 2012 02:25:36 -0700
Subject: Re: [Tinyos-help] Does TinyOS dist from 
http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?
From: cire...@gmail.com
To: drod...@hotmail.com
CC: tinyos-help@millennium.berkeley.edu

On Fri, Jul 27, 2012 at 12:55 AM, David Rodenas  wrote:

Hi all
I have the latest version of tinyos (from tinyos trunk) with telosb working 
together. I found the solution after several instalations and looking into the 
following threads: 

Cool.
Be aware that David is doing an installation of the Released T2.1.1 (which is 
getting pretty dated at this point) and ALSO the development trunk which is 
about to be released as T2.1.2.

Installing both isn't usual,   I'd actually recommend installing from the 
TinyProd (master Branch) on github which is a snapshot from the TinyOS 
development trunk.  The master branch will always follow the current (latest) 
full release of TinyOS.  In this case the upcoming T2.1.2 release.

MSP430 toolchains come in various flavors because it has gotten extensively 
reworked by Peter Bigot (this is a good thing).
The Release T2.1.1 code builds with the older msp430 toolchain (3.2.3, now 
called legacy).   The legacy toolchain installs into the /usr heirarchy.

The Development Trunk builds with the newer msp430 4.6.3 toolchain (now called 
-46).   The -46 toolchain installs into /opt/msp430-46.

What I've done is the following (using a Ubuntu 10.04 LTS) - Please read them 
carefully before doing anything -:

11.10 is recommended at this point.  I've also used 10.04, 10.10 and am 
currently using 11.10.   All my current testing and operational use has been on 
11.10.  If you are setting up a new system, use 11.10 (Oneric) or give 12.04 a 
try.   It should work, but hasn't been tested.

Be warned, the following will remove your existing packages named nesc, and 
anything with tinyos in its package name.   This includes any installation of 
tinyos-2.1.1 you might have.

If you don't want that to happen remove the packages one by one by hand. 
$ sudo dpkg -P `dpkg -l nesc '*tinyos*' | grep ^ii | awk '{ print $2 }' | 
xargs`$ sudo apt-get clean

It is better to add the deb lines into /etc/apt/sources.d/tinyprod-debian.list 
as described in the README.  Just to keep things seperate.  apt-get update will 
automatically find the additions.

$ sudo gedit /etc/apt/sources.list
deb http://tinyprod.net/repos/debian squeeze maindeb 
http://tinyprod.net/repos/debian msp430-46 main
$ sudo apt-get update
be aware that the packages on tinyprod.net are signed with my key, which you 
are installing below.   The packages on stanford have not been signed (the last 
I looked). This can potentially be a security problem if you are using 
unsigned packages from stanford.
 $ gpg --keyserver keyserver.ubuntu.com --recv-keys 34EC655A
$ gpg -a --export 34EC655A | sudo apt-key add -$ apt-get install tinyos-2.1.1 
nesc tinyos-tools msp430-tinyos-legacy avr-tinyos$ sudo gedit $HOME/.bashrc
source /opt/tinyos-2.1.1/tinyos.sh
$ sudo chown -R  /opt/tinyos-2.1.1
This completes the installation of the old T2.1.1 release and the legacy tools. 
  Your PATH variable typically includes /usr/bin and since this is where the 
legacy tools get installed, the toolchain that gets used comes from /usr/bin 
when you build T2 apps.

 Now, if you go to $TOSROOT/apps/Blink, and do make telosb, it should work. 

The remainder is  installing the development trunk code and required tools.

However, I recommend you have the latest instalation of tinyos, so (first steps 
retrieved from 
http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT):

$ cd $HOME$ mkdir -p local/src$ cd local/src$ svn checkout 
http://tinyos-main.googlecode.com/svn/trunk/ tinyos-2.x 

You can also use git (which I recommend, it's a better fit for how T2 
development seems to be working):
cd local/srcgit clone git://github.com/tinyprod/prod.git tinyos-2.x

The s/w will be in local/src/tinyos-2.x and you will be on the master branch 
from the tinyprod/prod repository.   You will have to modify the environment 
variables to set TOSDIR and TOSROOT correctly.

See the script tinyos.sh in /opt/tinyos-2.1.1 for details about what gets set.

(now, I made a backup of everything within the tinyos-2.1.1 directory, and 
after that, I deleted everything except the tinyos.sh file)

You don't need to do any of this.   Change the environment variables for 
TOSROOT and TOSDIR as needed to point to your local copy of the source code.

You really don't want to mess with /opt/tinyos-2.1.1 because for one thing it 
was installed as a package.   It won't hurt anything but is weird and is a 
whole bunch of extra steps.   You really don't need to do this.   Just change 
the environment variables.
 $ cd local/src/tinyos-2

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

2012-07-27 Thread Eric Decker

On Fri, Jul 27, 2012 at 12:55 AM, David Rodenas  wrote:

>  Hi all
>
> I have the latest version of tinyos (from tinyos trunk) with telosb
> working together. I found the solution after several instalations and
> looking into the following threads:
>

Cool.

Be aware that David is doing an installation of the Released T2.1.1 (which
is getting pretty dated at this point) and ALSO the development trunk which
is about to be released as T2.1.2.

Installing both isn't usual,   I'd actually recommend installing from
the TinyProd
(master Branch) on github  which is a
snapshot from the TinyOS development trunk.  The master branch will always
follow the current (latest) full release of TinyOS.  In this case the
upcoming T2.1.2 release.

MSP430 toolchains come in various flavors because it has gotten extensively
reworked by Peter Bigot (this is a good thing).

The Release T2.1.1 code builds with the older msp430 toolchain (3.2.3, now
called legacy).   The legacy toolchain installs into the /usr heirarchy.

The Development Trunk builds with the newer msp430 4.6.3 toolchain (now
called -46).   The -46 toolchain installs into /opt/msp430-46.

> What I've done is the following (using a Ubuntu 10.04 LTS) - Please read
> them carefully before doing anything -:
>

11.10 is recommended at this point.  I've also used 10.04, 10.10 and am
currently using 11.10.   All my current testing and operational use has
been on 11.10.  If you are setting up a new system, use 11.10 (Oneric) or
give 12.04 a try.   It should work, but hasn't been tested.

Be warned, the following will remove your existing packages named nesc, and
anything with tinyos in its package name.   This includes any installation
of tinyos-2.1.1 you might have.

If you don't want that to happen remove the packages one by one by hand.

> $ sudo dpkg -P `dpkg -l nesc '*tinyos*' | grep ^ii | awk '{ print $2 }' |
> xargs`
> $ sudo apt-get clean
>
>
It is better to add the deb lines into
/etc/apt/sources.d/tinyprod-debian.list as described in the
README.
 Just to keep things seperate.  apt-get update will automatically find the
additions.

$ sudo gedit /etc/apt/sources.list
> 
> deb http://tinyprod.net/repos/debian squeeze main
> deb http://tinyprod.net/repos/debian msp430-46 main
> 
> $ sudo apt-get update
>

be aware that the packages on tinyprod.net are signed with my key, which
you are installing below.   The packages on stanford have not been signed
(the last I looked). This can potentially be a security problem if you
are using unsigned packages from stanford.

> $ gpg --keyserver keyserver.ubuntu.com --recv-keys 34EC655A
> $ gpg -a --export 34EC655A | sudo apt-key add -
> $ apt-get install tinyos-2.1.1 nesc tinyos-tools
> msp430-tinyos-legacy avr-tinyos
> $ sudo gedit $HOME/.bashrc
> 
> source /opt/tinyos-2.1.1/tinyos.sh
> 
> $ sudo chown -R  /opt/tinyos-2.1.1
>

This completes the installation of the old T2.1.1 release and the legacy
tools.   Your PATH variable typically includes /usr/bin and since this is
where the legacy tools get installed, the toolchain that gets used comes
from /usr/bin when you build T2 apps.

> Now, if you go to $TOSROOT/apps/Blink, and do make telosb, it should work.
>

The remainder is  installing the development trunk code and required tools.

However, I recommend you have the latest instalation of tinyos, so (first
> steps retrieved from
> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT):
>
> $ cd $HOME
> $ mkdir -p local/src
> $ cd local/src
> $ svn checkout http://tinyos-main.googlecode.com/svn/trunk/ tinyos-2.x
>

You can also use git (which I recommend, it's a better fit for how T2
development seems to be working):

cd local/src
git clone git://github.com/tinyprod/prod.git tinyos-2.x

The s/w will be in local/src/tinyos-2.x and you will be on the master
branch from the tinyprod/prod repository.   You will have to modify the
environment variables to set TOSDIR and TOSROOT correctly.

See the script tinyos.sh in /opt/tinyos-2.1.1 for details about what gets
set.

> (now, I made a backup of everything within the tinyos-2.1.1 directory, and
> after that, I deleted everything except the tinyos.sh file)
>
>
You don't need to do any of this.   Change the environment variables for
TOSROOT and TOSDIR as needed to point to your local copy of the source code.

You really don't want to mess with /opt/tinyos-2.1.1 because for one thing
it was installed as a package.   It won't hurt anything but is weird and is
a whole bunch of extra steps.   You really don't need to do this.   Just
change the environment variables.

> $ cd local/src/tinyos-2.x
> $ cp -r * /opt/tinyos-2.1.1/
>
>
You also don't need to rebuild the tools.   The package tinyos-tools
provides those tools.   The tinyos-tools 1.4.2 package and nesc 1.3.4
should be fully backward compatible with both the msp430 3.2.3 and
msp430-46 (4.6.3) versions of the MSP430 toolchains.

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

2012-07-27 Thread David Rodenas





Hi all
I have the latest version of tinyos (from tinyos trunk) with telosb working 
together. I found the solution after several instalations and looking into the 
following threads: 
http://www.mail-archive.com/tinyos-help@millennium.berkeley.edu/msg41701.html 
http://www.mail-archive.com/shimmer-users@eecs.harvard.edu/msg00411.html 
What I've done is the following (using a Ubuntu 10.04 LTS) - Please read them 
carefully before doing anything -:
$ sudo dpkg -P `dpkg -l nesc '*tinyos*' | grep ^ii | awk '{ print $2 }' | 
xargs`$ sudo apt-get clean$ sudo gedit /etc/apt/sources.listdeb 
http://tinyprod.net/repos/debian squeeze maindeb 
http://tinyprod.net/repos/debian msp430-46 main$ sudo apt-get update$ gpg 
--keyserver keyserver.ubuntu.com --recv-keys 34EC655A$ gpg -a --export 34EC655A 
| sudo apt-key add -$ apt-get install tinyos-2.1.1 nesc tinyos-tools 
msp430-tinyos-legacy avr-tinyos$ sudo gedit $HOME/.bashrcsource 
/opt/tinyos-2.1.1/tinyos.sh
$ sudo chown -R  /opt/tinyos-2.1.1
Now, if you go to $TOSROOT/apps/Blink, and do make telosb, it should work. 
However, I recommend you have the latest instalation of tinyos, so (first steps 
retrieved from 
http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT):
$ cd $HOME$ mkdir -p local/src$ cd local/src$ svn checkout 
http://tinyos-main.googlecode.com/svn/trunk/ tinyos-2.x 
(now, I made a backup of everything within the tinyos-2.1.1 directory, and 
after that, I deleted everything except the tinyos.sh file)
$ cd local/src/tinyos-2.x$ cp -r * /opt/tinyos-2.1.1/$ cd 
/opt/tinyos-2.1.1/tools$ ./Bootstrap$ ./configure --prefix=$HOME/local$ make 
all$ make install
At this point, you have the latest version of tinyos, but now, "make telosb" 
does not work. The reason is that you need the msp430-46 toolchain:
$ sudo apt-get install msp430-46$ cd /usr (where the directory msp430 is, maybe 
/usr/local)$ mv msp430 msp430-gcc-3.2.3$ ln -s /opt/msp430-46 msp430$ cd 
/usr/bin$ rm msp430-*$ ln -s ../msp430/bin/* .
And that's all. This finally worked for me. I wish you luck.
David
Date: Thu, 26 Jul 2012 23:00:15 -0700
From: cire...@gmail.com
To: gary.lee1...@gmail.com
CC: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Does TinyOS dist from 
http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?



On Thu, Jul 26, 2012 at 8:56 PM, Gary Lee  wrote:

Thanks for your reply.

Could you let me know how to install *-legacy packages, where the 3.2.3 
compiler lives now from stanford.

Read the rest of the email.   I already told you.   Follow the links.  Go read 
the README at tinyprod.net/repos/debian
 

On Thu, Jul 26, 2012 at 12:17 AM, Eric Decker  wrote:




On Wed, Jul 25, 2012 at 8:49 PM, Gary Lee  wrote:



"make telosb" works before.

when I run "ncc --version -target=telosb", I got 

ncc: 1.2.4
nescc: 1.3.4
msp430-gcc: msp430-gcc (GCC) 4.5.3
Copyright (C) 2010 Free Software Foundation, Inc.




This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Prior to updating the tools from dists/ubuntu, I strongly suspect you had the 
3.2.3 compiler.   Because it worked.



When you updated the tools again you got the 4.5.3 compiler which is 
incompatible with the T2.1.1 release code you have in /opt/tinyos-2.1.1.

Try installing the  *-legacy packages, it is where the 3.2.3 compiler lives 
now.   I beleive they are in the dists/ubuntu repository at stanford.   They 
also exist in the tinyprod repository at http://tinyprod.net/repos/debian/








On Wed, Jul 25, 2012 at 10:41 PM, Eric Decker  wrote:






On Wed, Jul 25, 2012 at 8:26 PM, Gary Lee  wrote:





Hi,

I have installed TinyOS 2.1.1 from 
http://tinyos.stanford.edu/tinyos/dists/ubuntu many times.






Did "make telosb"  work before? 




recently, when I installed from http://tinyos.stanford.edu/tinyos/dists/ubuntu 
again, when I run "make micaz", it works fine.







However, when I run "make telosb", lots of errors.

what does the output of 
ncc --version -target=telosb
say?





 





Any help?

Thanks a lot,

Gary


___

Tinyos-help mailing list

Tinyos-help@millennium.berkeley.edu

https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




-- 
Eric B. Decker
Senior (over 50 :-) Researcher







-- 
Eric B. Decker
Senior (over 50 :-) Researcher







-- 
Eric B. Decker
Senior (over 50 :-) Researcher




___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
  ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] how to debug TelosB code at instruction level?

2012-07-27 Thread Eric Decker

The problem with MSPSim (and pretty much any sim for that matter) is how to
deal with the actual I/O.  Peripherals, etc.


On Fri, Jul 27, 2012 at 12:31 AM, André Rodrigues <
andremiguelrodrig...@gmail.com> wrote:

> **
> MSPSim?
>
> - Original Message -
> *From:* Eric Decker 
> *To:* Gary Lee 
> *Cc:* tinyos-help@millennium.berkeley.edu
> *Sent:* Friday, July 27, 2012 6:58 AM
> *Subject:* Re: [Tinyos-help] how to debug TelosB code at instruction
> level?
>
>
>
> On Thu, Jul 26, 2012 at 9:20 PM, Gary Lee  wrote:
>
>> TelosB motes have no JTAG interface.
>
>
> Not true.   U8 is the jtag header.  you can wire that up with a special
> cable (you will have to figure it out, I don't remember what the
> connections are) to the TI MSP-FET430UIF, USB JTAG.   Documentation is out
> there that describes what the pin outs look like.
>
>
>> Avrora does not support debugging TelosB. So any suggestion about what
>> tools can be used to analyze TelosB TinyOS code at instruction level?
>>
>> Thanks.
>>
>> Gary
>>
>> ___
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>>
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
>  --
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>


-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] how to debug TelosB code at instruction level?

2012-07-27 Thread André Rodrigues

MSPSim?
  - Original Message - 
  From: Eric Decker 
  To: Gary Lee 
  Cc: tinyos-help@millennium.berkeley.edu 
  Sent: Friday, July 27, 2012 6:58 AM
  Subject: Re: [Tinyos-help] how to debug TelosB code at instruction level?

  On Thu, Jul 26, 2012 at 9:20 PM, Gary Lee  wrote:

TelosB motes have no JTAG interface. 

  Not true.   U8 is the jtag header.  you can wire that up with a special cable 
(you will have to figure it out, I don't remember what the connections are) to 
the TI MSP-FET430UIF, USB JTAG.   Documentation is out there that describes 
what the pin outs look like.

Avrora does not support debugging TelosB. So any suggestion about what 
tools can be used to analyze TelosB TinyOS code at instruction level?

Thanks.

Gary

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

  -- 
  Eric B. Decker
  Senior (over 50 :-) Researcher

--

  ___
  Tinyos-help mailing list
  Tinyos-help@millennium.berkeley.edu
  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Deluge T2 and iris motes

Re: [Tinyos-help] Deluge T2 and iris motes

Re: [Tinyos-help] is it possible to perform multihopping without using collection tree protocol?????????

Re: [Tinyos-help] implementation of a new routing algorithm

[Tinyos-help] RS232 Communication Problem

Re: [Tinyos-help] TKN154: What I am receiving?

Re: [Tinyos-help] Problem with printf

Re: [Tinyos-help] Building your own Motes

Re: [Tinyos-help] Building your own Motes

Re: [Tinyos-help] Building your own Motes

[Tinyos-help] PhoneSense 2012 (SUBMISSION EXTENSION: 1 Aug 2012) w/ SenSys 2012, Toronto, Canada, 6 Nov 2012

[Tinyos-help] Blip with shimmer motes

[Tinyos-help] TKN154: What I am receiving?

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

Re: [Tinyos-help] Does TinyOS dist from http://tinyos.stanford.edu/tinyos/dists/ubuntu support TelosB motes?

Re: [Tinyos-help] how to debug TelosB code at instruction level?

Re: [Tinyos-help] how to debug TelosB code at instruction level?

18 matches

Site Navigation

Mail list logo

Footer information