try:
rpm -ivh --nodeps --ignoreos msp430tools-base-0.1-20050607.cygwin.i386.rpm
-Fred
On Oct 30, 2009, at 8:16 AM, wendy guo wrote:
Hi all!
I'm a new user of TinyOs under Cygwin!
When trying to install the following RPM:
msp430tools-base-0.1-20050607.cygwin.i386.rpm, I get the
and ckpl = 0 instead, then data is written at rising
edge and stable at falling edge (see Figure 14−9 MSP430 User's
Guide).
Jan
On Fri, Jul 18, 2008 at 1:56 AM, Xiaofan Jiang
[EMAIL PROTECTED] wrote:
Hi,
I've been working on a driver to talk to a SPI slave from a Telos
master.
The slave
problems.
-Fred
On Nov 8, 2007, at 10:49 PM, Xiaofan Jiang wrote:
Yes. I have t2 installed on leopard successfully. Follow kevin's
guide except use darwinport to install the avr toolchain instead of
using fink.
-fred
On Nov 8, 2007, at 10:34 PM, Nitish Jha [EMAIL PROTECTED] wrote:
has
Yes. I have t2 installed on leopard successfully. Follow kevin's guide
except use darwinport to install the avr toolchain instead of using
fink.
-fred
On Nov 8, 2007, at 10:34 PM, Nitish Jha [EMAIL PROTECTED] wrote:
has anybody been able to successfully install TinyOS 1.x or 2.x on
Mac
Hi,
I'm trying to run some power measurements of motes running CTP
collection with and without LPL enabled (on the MicaZ). However, I
don't seem to see any difference. In this picture - http://buzzing.cs.berkeley.edu/~xjiang/webfiles/NOLPLvsLPL.png
, the left is without LPL and the right is
a little googling for the error msg would reveal this link:
http://moteserver.uv.es/documentation.php
basically run: sudo apt-get remove brltty
-Fred
While using Ubuntu with tinyos-2.0.2 downloaded via apt-get
The first time I plug the mote in:
[EMAIL PROTECTED]:/opt/tinyos-2.x/apps/Blink$
Hi all,
I'm trying to communicate with a I2C device using MicaZ (MicaZ is the
master) but have encountered some strange problems as described
below. Does anyone have any ideas?
I wrote a very simple program that basically write a byte to the I2C
device (code shown at the end). The
ankur,
I have seen this error before when I was compiling my I2C program for tmote. I
fixed it by reinstalling the toolchain. I'm not certain about the exact part
but most likely the msp430 toolchain. Also you might try installing moteiv's
version.
hope that helps
-Fred
- Original
ankur
If I remember correctly, Tinyos-1.x's implementation of I2C is not correct /
complete. It does not address arbitration appropriately. Moteiv's
implementation (i.e. boomerang) uses the resource abstraction for usart
arbitration and therefore more fully support I2C.
Tinyos-2.x has also
on second thought, tinyos-1.x's i2c might've been software bit-
banging... which would explain why the macro wasn't available lol.
-Fred
On Feb 13, 2007, at 2:52 PM, Xiaofan Jiang wrote:
ankur
If I remember correctly, Tinyos-1.x's implementation of I2C is not
correct / complete. It does
hardware (e.g. CPU) requirements largely depends on the actual code /
application running on it, notably the RAM and ROM requirements of
the application. ATmega32 should be fine for most small applications.
For example, the ultrasound ranging board (http://www.tinyos.net/
At this point, the best way is probably hook up a small shunt
resistor (1-50Ohm depending on your load and oscilloscope accuracy)
in series between the battery and the board, either on the ground
side or the Vdd side. Then use an oscilloscope to measure it.
Also pay attention to the
I don't think there is a guide on it. Although you probably should
look at the existing sensorboard designs on http://www.tinyos.net/
scoop/special/hardware. It's probably best to copy after a
corresponding design depending on which main board you want your
sensorboard to interface with.
13 matches
Mail list logo
