ends up in:
apps//build//app.c
i.e. for the Blink app for micaz it would be:
apps/Blink/build/micaz/app.c
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered *
___
Tinyos-help mailin
tion, and when fully
received, set the flags for TosBoot and reset the micro. Done!
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered *
___
Tinyos-help mailing list
Tinyos-help@millennium.berk
to peruse is probably the TosBoot
Makefile:
https://github.com/DiUS/tinyos-siflex02/blob/master/tos/lib/tosboot/Makefile
The siflex02 & modflex related targets have the relevant bits.
Getting it all to work isn't what I'd call trivial, but it *is* doable if
you're willing
#x27;t use CFLAGS (or CXXFLAGS as one would expect for a C++
object). Could that be the problem perhaps?
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered *
___
Tinyos-h
;
>
That should almost certainly be &x rather than x. It looks like you're
treating the value 123 as a pointer, which would explain why you're getting
different values all the time...
> call SHA1.digest(context, Message_Digest[SHA1HashSize]);
>
Again, I don't kn
:
components SHA1M;
here, otherwise it will not know what SHA1M you're talking about here:
> App.SHA1 -> *SHA1M*;
> }
>
The NesC language reference might be of use to you - it's very readable and
contains lots of useful information!
Regards,
/Johny
--
Johny Mattsso
ve a look through the source.
http://tinyos.stanford.edu/tinyos-wiki/index.php/TEPs
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered *
___
Tinyos-help mailing list
Tinyos-help@millennium.b
two, there's not a lot of space left for
an application once the upgrade support has gone in.
People who've worked with TinyOS on the MSP430s probably have better info,
but I hope this gives you a couple of leads at least.
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engine
nal checks in IPDispatchP and
Ieee154PacketLayer that would need to be removed, iirc).
You might need to do something to the IP forwarding engine to prevent
it from acting as a router in the above scenario (but that's probably
a good idea on an NIDS anyway).
Hth,
/Johny
-
As a general pointer, start digging from IPDispatchC/P and work your
way through the code from there.
You probably also want to ask yourself why you're trying to go from a
message_t to IP headers without letting the stack do the proper
unwrapping for you. :)
Regards,
/Johny
--
Johny Mattss
thub
> > wiki, or the regular doc site as well?
>
> Sure, would you take this task, and I will extend it as needed?
>
Me and my large mouth (keyboard?)... Okay, it's up:
https://github.com/tinyos/tinyos-main/wiki/Tasklet-design-notes
Cheers,
/Johny
--
Johny Mattsson
Senior S
cheduled to be executed before the tasklet task).
Thanks for posting the write-up! Can I suggest it be added to the github
wiki, or the regular doc site as well?
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
_
Arduino work is on hold as I have other far more pressing
matters to deal with.
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millennium.be
l/tep131.html
Cheers,
/Johny
--
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
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
Hi list,
I've run into an unexpected problem which I can't figure out how to solve
properly. It seems to me to be impossible to typedef an "nx" (external)
type to a new name for some strange reason. I can't find anything in the
documentation that mentions this as a limitation, so I'm posting here
f Johny is interested.
>
> --Vlado
>
>
--
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
on a different project now, so I don't work
with TinyOS at this point).
> Did anybody test heterogeneous Blip2.0 networks yet using RF230 and
> CC24020 hardware or something similar to it?
>
Only homogenous RF212 networks here, sorry.
Regards,
/Johny
--
Johny Mattsson
Seni
t version of gcc-avr and avr-libc, or you'll
see lots of errors when compiling.
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millen
e "Multi-Precision
Floating point with correct Rounding" library used by gcc, and is typically
installed either together with gcc or prior to gcc. Try reinstalling the
toolchain.
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
t 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
nescc-1.3.1, avr-gcc-4.3.4, avr-libc-1.6.7
- nescc-1.3.3, avr-gcc-4.3.5, avr-libc-1.6.8 (also avr-libc-1.7 at some
point)
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailin
something
more recent. In my case the AVR-libc headers reside in /usr/lib/avr/include.
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
e a const entity in program
memory, as well as some macros for easier reading from program space (e.g.
pgm_read_byte_near/far). If you're storing string constants in program
space, there is also a whole bunch of str..._P functions which directly
take a program space string pointer.
Hth,
/Johny
-
://www.tinyos.net/tinyos-2.1.0/doc/html/tep103.html).
Regards,
/Johny
--
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
d to keep the list cc'd for archival purposes, plus it
gives others a chance to contribute further information.
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
where ideas are engineered
___
Tinyos-help mailing list
ion. Your question might be moot after that.
http://www.tinyos.net/tinyos-2.1.0/doc/html/tep108.html
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
where ideas are engineered
___
Tinyos-help mailing list
Ti
ovided, this would be my diagnosis of what's going on.
Regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.m
at DiUS.
Cheers,
/Johny
--
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
meone could help me understand why only one write cycle is
> allowed between successive power cycles, I'd greatly appreciate it :)
>
> Thanks for your time!
>
> -Max
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-he
t
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millennium.
's processor since it would reduce
>> the amount of data that I would need to transmit and could potentially
>> prolong the life of the battery. Is this doable?
>>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@mil
/tinyos-2.x/tos/../support/sdk/c/sf/libmote.a: No such file or
> directory
> Makefile:9: recipe for target `seriallisten15-4' failed
> make: *** [seriallisten15-4] Error 1
>
y Help
> Me
>
> Ajit R K
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
--
Johny Mattsson
Senior Software Engineer
D
it R Kanale
> IIST, Trivandrum
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
--
Johny Mattsson
Senior Software Engineer
D
On 13 February 2012 22:12, Eric Decker wrote:
>
> I believe there are some docs that talk about porting between the two.
>
Indeed there is:
http://www.tinyos.net/tinyos-2.1.0/doc/html/porting.html
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Lt
age are tagged with the PC local system time and are
> read in through the serial port (e.g. through Matlab).
>
> I want a method to get the PC clock time for tagging messages (e.g. some
> command). Can you help me in this?
>
> Regards,
> *Altamash Ahmed*
>
>
>
>
>
a stupid question but I am not sure how I should go
> about?
>
> Thank you
> regards
> BG
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/lis
r the ways for accessing the PC time from the mote but
> could not find the right way. Can anybody please help me in it matter.
>
>
> Regards,
> *Altamash Ahmed, *
>
>
>
>
>
> ___
> Tinyos-help mailing list
> T
specifics of the chip or platform.
Regards,
/Johny
--
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
ti.supsi.ch/~afoerste/
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
--
Johny Mattsson
Senior Software Engineer
D
cribed in TEP 131 (
http://www.tinyos.net/tinyos-2.1.0/doc/html/tep131.html). Depending on just
how close to a currently supported platform your hardware is, it may be
more or less challenging. It does require quite intimate knowledge of the
hardware, regardless.
Best regards,
/Johny
--
Johny Mattss
testing I want to do, and it would also be a pain to
firmware upgrades since we haven't got over-the-air upgrades going (yet).
Thanks in advance,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
x27;s not possible to build either from our version, unless using the
cc2420x driver. I wasn't game (or had time, or hardware) to attempt to
change the regular cc2420 driver.
Best regards,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
tinyos-2.x.svn/tos/lib/ppp/PppDaemonC.nc:65,***
> *
>
> from PppRouterC.nc:16:
>
> ** **
>
> Regards, Gabriel
>
>
>
--
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
work with the newer
> one?
>
> ** **
>
> Thanks
>
> Gabriel Neumüller
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo
Have a look at the UDPEcho (or TCPEcho) application for an example of usage
and wiring.
Cheers,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.
ter solicitation as it is done in BLIP
> 1.0. This is how we understand it its meant to be done with IPv6 so I also
> wonder why this solution has been abandoned in the new BLIP 2.0 stack? Maybe
> its just not implemented yet?
>
> /Henrik
>
>
--
Johny Mattss
well, come to think of it).
Cheers,
/Johny
--
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-b
l are supposed to work with
mesh-forwarding and hardware address/pan filtering, and until (if!) I have
the time to do that I won't spend any serious time trying to get hardware
acks going.
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing
with a packet size bigger than 75 the mote stops
> responding. I assume this is due to fragmentation.
> Will investigate this more tomorrow.
>
> /Henrik
>
>
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
sConfig.nc
new file mode 100644
index 000..1b8c051
--- /dev/null
+++ b/tos/lib/net/blip/interfaces/ShortAddressConfig.nc
@@ -0,0 +1,6 @@
+interface ShortAddressConfig
+{
+ command void setShortAddr(uint16_t address);
+
+ event void setShortAddrDone(error_t error);
+}
--
Jo
dress, but then it tries to
re-bind to the link-local address of ppp0 (which is already bound in order
to provide the PppRouter with an address), and exits with an error.
Is there anyone out there who has this working and could give me some hints
(or a server.conf even)?
Thank you,
/Johny
--
John
2011/8/16 Johny Mattsson
> We do have BLIP 2.0 running with an RF212 chip here internally.
>
> That said, it's not a very clean hack (it only works with the RF212 now,
> not the CC2420). I can't provide code at this point
>
>
Okay, I've got clearance to re
p; radio stuff and getting it to a
working state, and that was with no prior TinyOS experience.
Hope this helps,
/Johny
*) The naming is very confusing. There are BareSend and Send interfaces
exposed under the names Ieee154Send and BareSend (iirc), despite there being
different interfaces with th
l need a Windows system to do so (VMWare image
works, VirtualBox does not).
HTH,
/Johny
--
Johny Mattsson
Senior Software Engineer
DiUS Computing Pty. Ltd.
*where ideas are engineered
*
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https:/
hen pushing it to the main branch.
>
> -John
>
> On Aug 1, 2011, at 12:33 AM, Johny Mattsson wrote:
>
> > Hello,
> >
> > Could someone please shine some light on the change from r5657 which
> added the following to RPLRankP.nc in IP_DIO.recv():
> >
and
what's really going on here.
Thanks,
/Johny
--
Johny Mattsson
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
On Thu, Jul 28, 2011 at 11:20 PM, Carlos Rodrigues wrote:
> **
>
> It is possible create a random value during a make? For example in Makefile
> have something like this:
> CFLAGS += -DVALUE_RANDOM
>
Assuming you're on a *nix system (and using GNU make, but that should be a
given), you could do s
59 matches
Mail list logo
