Re: [Tinyos-help] Tinyos-help Digest, Vol 117, Issue 52
Hi All, I strongly doubt the availability of software rewritten capabilities of the NesC language, I have read all through the source coding of TINYOS and the mannuals of both TINYOS and NesC. I find that the best to write for TINYOS and its motes is C#, the Assembly best suit for this issue is DSP Assembly for Motorola DSP56002 Microprocessor designed by Professor El-Sharkawy Mohamond in IUPUI, IN 46202. Can some one help me too a lot to provide nesC source coding for this problem:"make two mica2 motes to independently communicate with motherboard and via which to connect with Laptop computers (for instance, to get temperature sensor values) which has TOSSIM and TINYOS installed. and make the mica2 motes and motherboard to run in multihop status in doing this to help double check the motes' availability at the exact operating time." I doubt how to write the nesC, I failed for at least 100 times now. The only things I succeeded is to implement C# coding and the 19 experimental source code pieces the TINYOS organizations provided. The C# source coding can be directly written instead of nesC, and the compiler works. Even though occasionally some errors and compilation errors may apply to this change, still the hardware can work according to my request. Thanks. An Feng anderson.an.f...@aol.com -Original Message- From: tinyos-help-request To: tinyos-help Sent: Sun, Jan 27, 2013 7:00 am Subject: Tinyos-help Digest, Vol 117, Issue 52 Send Tinyos-help mailing list submissions to tinyos-help@millennium.berkeley.edu To subscribe or unsubscribe via the World Wide Web, visit https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help or, via email, send a message with subject or body 'help' to tinyos-help-requ...@millennium.berkeley.edu You can reach the person managing the list at tinyos-help-ow...@millennium.berkeley.edu When replying, please edit your Subject line so it is more specific than "Re: Contents of Tinyos-help digest..." Today's Topics: 1. Re: Mote-to-Mote Serial Communication Problem (Saeid Yazdani) 2. Re: Mote-to-Mote Serial Communication Problem (nishad kamdar) 3. Re: Mote-to-Mote Serial Communication Problem (Eric Decker) 4. Re: Mote-to-Mote Serial Communication Problem (nishad kamdar) -- Message: 1 Date: Sat, 26 Jan 2013 21:13:31 +0100 From: Saeid Yazdani Subject: Re: [Tinyos-help] Mote-to-Mote Serial Communication Problem Cc: tinyos-help@millennium.berkeley.edu Message-ID: <510438eb.4020...@gmail.com> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130126/140961c1/attachment-0001.htm -- Message: 2 Date: Sun, 27 Jan 2013 01:53:54 +0530 From: nishad kamdar Subject: Re: [Tinyos-help] Mote-to-Mote Serial Communication Problem To: Saeid Yazdani Cc: tinyos-help@millennium.berkeley.edu Message-ID: Content-Type: text/plain; charset="iso-8859-1" Hey, Thanks for the reply, I have also tried the UART 0 on the 10 pin connector and connected the TelosB motes which did not lead to communication between them. I have made the necessary changes, in the PlatformSerialC.nc file for switching between UART 1 and UART 0. Is there anything i am missing to configure like the baud rate or anything i am not doing what the JAVA code is doing like opening the Ports before communication? Please Advice, On Sun, Jan 27, 2013 at 1:43 AM, Saeid Yazdani wrote: > I don't think connecting both USB ends of two telosb motes makes sense, > since the FTDI chip is working only when connected to a proper USB host > (Such as PC usb port, but not another TelosB mote). > > Also the USB on TelosB is connected to UART 1. > > If its your only option to use UART1, then you may hardwire two TelosB's > UART1 by solderin wires directly into the FTDI chip on TelosB (See the > datasheet). > > Other wise you could use UART0 that is on the 10pin header expansion. > > Regards, > Saeid Yazdani > http://www.eetutorials.com > > On 26-1-2013 20:31, nishad kamdar wrote: > > Hello all, > > I am trying to establish communication between two TelosB motes not via > the radio but using the UART. > > At first I burned the TestSerial Code in both the motes and connected > their USB ports via a USB Female to Female cable. > However it did not lead to communication and blinking of the Leds which > happens normally while using the Java TestSerial Code. > > So, i further tried to use the UART 0 using the connectors on the mote. > I made the required changes in the PlatformSerialC.nc file to use the UART0 > port. > But this too did not lead to communication between the motes. > > My aim is to interface an Underwater Acoustic modem (SAM 1 from Desert > Star) to the mote's Serial port through which it can be controlled. > > Can anyone p
Re: [Tinyos-help] Tinyos-help Digest, Vol 118, Issue 33
t;>
>>> error_t foo(nx_uint16_t val)
>>>
>>> when using the define.
>>>
>>> So of course it works.
>>>
>>
>> I'd like to think so, but given that a plain typedef doesn't work in this
>> situation, I wouldn't say "of course" - there could've been something wrong
>> with using nx types as pass-by-value parameters, for example. :)
>>
>>
>> If you compile Blink say for the telosb and then take a look at app.c you
>>> can see where the nx types are defined. Search for nx_uint16.
>>>
>>
>> I'll do you one better, I'll show you what's in the app.c from the
>> minimal test case in my previous email:
>>
>> First there's the nx_uint16_t which is an innocuous enough packed struct:
>> typedef struct { unsigned char nxdata[2]; } __attribute__((packed))
>> nx_uint16_t;
>>
>> Then there's an unused typedef of a __nesc_nxbase_nx_uint16_t whose use
>> I'm not entirely clear on without delving into compiler internals:
>> typedef uint16_t __nesc_nxbase_nx_uint16_t ;
>>
>> There is of course my typedef, looking as expected (module__type name):
>> typedef nx_uint16_t TestNxTypedefP__my_type16_t;
>>
>> And then there's the weirdness of the function taking my typedef'd type
>> as an argument:
>> static inline error_t
>> TestNxTypedefP__foo(TestNxTypedefPnesc_nxbase_my_type16_t val);
>>
>> What I had expected to see here was:
>> static inline error_t TestNxTypedefP__foo(TestNxTypedefP__my_type16_t
>> val);
>>
>>
>> It seems the compiler has an internal translation rule for nx types that
>> translates them from the struct version to the "base" version. When
>> compiling with the #define rather than the typedef, the function prototype
>> looks like this:
>> static inline error_t TestNxTypedefP__foo(__nesc_nxbase_nx_uint16_t
>> val);
>>
>>
>> To me this seems like a nesc issue (or at the very least a nesc
>> documentation issue).
>> Who/where do I bounce this to? Running nescc --help only points at the
>> gcc bug reporting, which is clearly not applicable here.
>>
>>
>>
>>> Maybe adding a nx_ prefix to your type would help.
>>>
>>
>> Tried that, it didn't help.
>>
>>
>> Thanks,
>> /Johny
>> *
>> *
>
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130216/4063adf5/attachment-0001.htm
--
Message: 3
Date: Sat, 16 Feb 2013 16:30:19 +0100 (CET)
From: aca...@correo.ugr.es
Subject: [Tinyos-help] What is the number maximum of nodes that can
support blip 2.0?
To: tinyos-help@millennium.berkeley.edu
Message-ID: <47704.96d6dfec.1361028619@correo8.ugr.es>
Content-Type: text/plain;charset=utf-8
Dear all.
Someone have any idea about the maximum number of nodes that can support
one sink mote (TelosB) using PppRouter and working with Blip 2.0?
I've worked ok with one sink node and 3 sensor nodes.
There is a limitant factor?
Thanks in advance for your answer.
Best regards,
Alejandro.
> This is actually for Muhammad but I only have Robin email directly.
>
>
> On Wed, Feb 13, 2013 at 12:42 PM, Robin Martinjak
> wrote:
>
>> On Wed, Feb 13, 2013 at 10:46:29PM +0500, Muhammad Tayyeb wrote:
>> > Hi,
>> > I am new to TinyOS and implementing the tutorials. I am on Deluge T2
>> at
>> the
>> > moment.
>>
>
> I am guessing that you are on cygwin. It would have been really helpful
> if you had told us what system you are hosting your development
> environment
> on.
>
>>
>> > When I run the command
>> >
>> > ./burn serial@/dev/ttyUSB0:115200 telosb
>> >
>> > I get the following error
>> >
>> > xubuntos@xubuntos-tinyos:/opt/tinyos-2.x/apps/tests/deluge/Blink$
>> ./burn
>> > serial@/dev/ttyUSB0:115200 telosb
>> > rm -rf build
>> > rm: cannot remove `build/telosb/ident_flags.txt': Permission denied
>> > rm: cannot remove `build/telosb/StorageVolumes.h': Permission denied
>>
>
> what do the permissions look like for the install?
>
>
>> > make: *** [clean] Error 1
>> > Compile and load Blink
>> >
>> > mkdir -p build/telosb
>> > /bin/sh: cannot create build/telosb/id
[Tinyos-help] water level sensor
Hi again all, Do you know,can a water level sensor or indicator can be directly or indirectly connected to a mote that has Tinyos?If it is,how it may be?If you could some details i'de pleased.Thanks from now.___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] (no subject)
Hi again all, Do you know,can a water level sensor or indicator can be directly or indirectly connected to a mote that has Tinyos?If it is,how it may be?If you could some details i'de pleased.Thanks from now.___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] What is the number maximum of nodes that can support blip 2.0?
Dear all. Someone have any idea about the maximum number of nodes that can support one sink mote (TelosB) using PppRouter and working with Blip 2.0? I've worked ok with one sink node and 3 sensor nodes. There is a limitant factor? Thanks in advance for your answer. Best regards, Alejandro. > This is actually for Muhammad but I only have Robin email directly. > > > On Wed, Feb 13, 2013 at 12:42 PM, Robin Martinjak > wrote: > >> On Wed, Feb 13, 2013 at 10:46:29PM +0500, Muhammad Tayyeb wrote: >> > Hi, >> > I am new to TinyOS and implementing the tutorials. I am on Deluge T2 >> at >> the >> > moment. >> > > I am guessing that you are on cygwin. It would have been really helpful > if you had told us what system you are hosting your development > environment > on. > >> >> > When I run the command >> > >> > ./burn serial@/dev/ttyUSB0:115200 telosb >> > >> > I get the following error >> > >> > xubuntos@xubuntos-tinyos:/opt/tinyos-2.x/apps/tests/deluge/Blink$ >> ./burn >> > serial@/dev/ttyUSB0:115200 telosb >> > rm -rf build >> > rm: cannot remove `build/telosb/ident_flags.txt': Permission denied >> > rm: cannot remove `build/telosb/StorageVolumes.h': Permission denied >> > > what do the permissions look like for the install? > > >> > make: *** [clean] Error 1 >> > Compile and load Blink >> > >> > mkdir -p build/telosb >> > /bin/sh: cannot create build/telosb/ident_flags.txt: Permission denied >> >> You should copy the whole tinyos-2.x directory to somewhere in your >> user's $HOME if you want to build stuff. >> > > Gag. > > We haven't updated the install instructions but the new improved > mechansims > to get the release are as follows: > > cd ~ > mkdir -p w > cd w > git clone git://github.com/tinyos/tinyos-release.git > > The above will put the current tinyos release (2.1.2) into the directory > ~/w/tinyos-release > > you will have to tweak your environment variable appropriately. > > you will also need git, "apt-get install git-core" should do the trick > > But I am assuming that you are on Linux and I suspect that isn't true. > > Currently, we don't have cygwin rpms for the 4.6.3 buildsSo if you are > on cygwin, I'm not > sure what you can do. The problem you will also run into is 2.1.2 needs > 4.6.3. > > I would strongly encourage you to switch over to a Linux box (Debian or > Ubuntu). I originally started TinyOS development using a Cygwin host and > found it to be quite painful as well as problematic. At some point I got > fed up and switched over to Linux and haven't looked back. I do much of > the packaging for toolchains and tinyos and do not support the cygwin > rpms. > I support the debian archives. > > Also the TinyOS repository at Stanford is no longer actively maintained so > am hosting my work at tinyprod.net. See below. > > >> > >> > Your help will be much appreciated on the error "Couldn't execute >> > msp430-gcc" error. msp430-gss exe is present in its folder. >> > > running commands as root isn't recommended, you can really do damage if > you > screw something up. > > > did you install the msp430 toolchain (you need 4.6.3 which you can get > from > http://tinyprod.net/repos/debian/ > > you should be able to execute the command "msp430gcc --version" to make > sure that > > >> > >> >> You probably need to install additional packages. Search your package >> manager for "msp430" or so. >> > > > > >> >> >> -- >> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org >> >> ___ >> 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] typedef + nx_intN_t = impossible?!
I'll look into it in a week or so...
David
On Feb 12, 2013 7:14 PM, "Eric Decker" wrote:
>
>
> Sigh. Would of been nice if we could have found a work around.
>
> File it as a bug against https://github.com/tinyos/nesc
>
> Maybe we can get David's attention.David?
>
> On Tue, Feb 12, 2013 at 3:48 AM, Johny Mattsson wrote:
>
>> On 12 February 2013 13:31, Eric Decker wrote:
>>
>>> First, the #define works because it is simple text substitution. So if
>>> you look at the resultant app.c you will see
>>>
>>> error_t foo(nx_uint16_t val)
>>>
>>> when using the define.
>>>
>>> So of course it works.
>>>
>>
>> I'd like to think so, but given that a plain typedef doesn't work in this
>> situation, I wouldn't say "of course" - there could've been something wrong
>> with using nx types as pass-by-value parameters, for example. :)
>>
>>
>> If you compile Blink say for the telosb and then take a look at app.c you
>>> can see where the nx types are defined. Search for nx_uint16.
>>>
>>
>> I'll do you one better, I'll show you what's in the app.c from the
>> minimal test case in my previous email:
>>
>> First there's the nx_uint16_t which is an innocuous enough packed struct:
>> typedef struct { unsigned char nxdata[2]; } __attribute__((packed))
>> nx_uint16_t;
>>
>> Then there's an unused typedef of a __nesc_nxbase_nx_uint16_t whose use
>> I'm not entirely clear on without delving into compiler internals:
>> typedef uint16_t __nesc_nxbase_nx_uint16_t ;
>>
>> There is of course my typedef, looking as expected (module__type name):
>> typedef nx_uint16_t TestNxTypedefP__my_type16_t;
>>
>> And then there's the weirdness of the function taking my typedef'd type
>> as an argument:
>> static inline error_t
>> TestNxTypedefP__foo(TestNxTypedefPnesc_nxbase_my_type16_t val);
>>
>> What I had expected to see here was:
>> static inline error_t TestNxTypedefP__foo(TestNxTypedefP__my_type16_t
>> val);
>>
>>
>> It seems the compiler has an internal translation rule for nx types that
>> translates them from the struct version to the "base" version. When
>> compiling with the #define rather than the typedef, the function prototype
>> looks like this:
>> static inline error_t TestNxTypedefP__foo(__nesc_nxbase_nx_uint16_t
>> val);
>>
>>
>> To me this seems like a nesc issue (or at the very least a nesc
>> documentation issue).
>> Who/where do I bounce this to? Running nescc --help only points at the
>> gcc bug reporting, which is clearly not applicable here.
>>
>>
>>
>>> Maybe adding a nx_ prefix to your type would help.
>>>
>>
>> Tried that, it didn't help.
>>
>>
>> Thanks,
>> /Johny
>> *
>> *
>
>
>
>
> --
> 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
