this should work right?
On Thu, Jul 31, 2008 at 3:12 PM, Jack Travis
[EMAIL PROTECTED] wrote:
Hi
I have a problem defining the default events for my interface.
The module implementation contains:
signal Interface.Receive(msg, payload, len);
...
default async event
Hi
I have a problem defining the default events for my interface.
The module implementation contains:
signal Interface.Receive(msg, payload, len);
...
default async event message_t* Interface.Receive(message_t* msg, void*
payload, uint8_t len) {
return msg;
}
I am having problem with my TOS installation.
$ make telosb
mkdir -p build/telosb
compiling BlinkAppC to a telosb binary
ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-target=
-gcc= -mmcu= -fnesc-separator=__ -Wall -Wshadow
-DDEF_TOS_AM_GROUP=0x7d -Wnesc-all
-target=telosb
second try...
any advice is welcome.
Thx
-- Forwarded message --
From: Jack Travis [EMAIL PROTECTED]
Date: Tue, May 27, 2008 at 5:12 PM
Subject: erratic boot.booted
To: tiny help tinyos-help@millennium.berkeley.edu
Hi all,
I am having an erratic problem with my platform and I
Hi,
Is the msp430f261x serie supported in tinyOS?
It's supported by mspgcc, it has basically the same functionalities, pinout,
processing unit, than the msp430f1611 (which is supported obviously) but
some of the registers are slightly different for some modules.
It there a compatibility list for
Hi,
I am creating a new platform, and I need to change the types in AM.h (like
AM_BROADCAST_ADDR = 0xfff*e*,) I guess directly changing the types in AM.h
would not be clean, how can I override it so that my fooAM.h be included
before AM.h? the directory is already included in my .platform but
Hi,
I am creating a new platform, and I need to change the types in AM.h I
guess directly changing the types in AM.h would not be clean, how can I
override it so that my fooAM.h be included before AM.h? the directory is
already included in my .platform but it does not work.
Thanks
Hi,
I know TinyOS assumes it has complete control over the hardware but what if
it doesn't. What is the best way to prevent user applications to access
hardware that should be exclusively controller by standard C functions. Is
there anyway thing simpler than arbiters?
Thanks,
hi all,
The idea is to implement the body of an event in TinyOs. This event is
signaled in low level C function.
Is it possible?
How should I setup my includes and where should I put the event prototype?
Thanks,
___
Tinyos-help mailing list
Hi,
I am struggling with the linker, when I try to run programs over existing C
functions.
Apparently I cant initialize variables at declaration Ex:
volatile Word2_t gw2BatteryVoltage= 0;
linker Output:
/cygdrive/c/DOCUME~1/ALEXAN~1/LOCALS~1/Temp/ccUZLX45.o:(.data+0x0): multiple
definition
Hi, anybody ever got this error
$ tos-install-jni
Installing 32-bit Java JNI code in /cygdrive/c/Program
Files/Java/jdk1.5.0_15/jre/bin ...
install: cannot stat `/usr/lib/tinyos/*-32.dll': No such file or directory
(There is effectivly no /usr/lib/tinyos/ dir and copying /lib/tinyos/ to
that
Forget last question got it renaming the toscomm.dll to toscomm-32.dll
and copying the directory to `/usr/lib/tinyos/
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
Hello all,
Is it possible to integrate some existing low level C code functions into a
new platform and then to interface those functions to standard HAL or HIL
interfaces in nesC? Or do I necessarily need to reorganize my low level code
to use low level interfaces provided in the µC chips
13 matches
Mail list logo
