[Tinyos-help] Error programming telosb
Hi all, I am getting the following Bootstrap loader synchronization error while installing any prog. on the telosb. I have rev. 5886 of tinyos from svn and I installed the toolchain from deb http://tinyprod.net/razvanm/debian squeeze main. I even tried installing tinyos using the instructions on the tinyos website using the jhu repo. but I get the same error. I am running Ubuntu 10.04. :~/tinyos-2.x/apps/Blink$ make telosb install mkdir -p build/telosb compiling BlinkAppC to a telosb binary ncc -o build/telosb/main.exe -Os -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\BlinkAppC\ -DIDENT_USERNAME=\solar\ -DIDENT_HOSTNAME=\solar-laptop\ -DIDENT_USERHASH=0x0cb46dcbL -DIDENT_TIMESTAMP=0x4f30867eL -DIDENT_UIDHASH=0x88ac2cbbL BlinkAppC.nc -lm compiled BlinkAppC to build/telosb/main.exe 2528 bytes in ROM 56 bytes in RAM msp430-objcopy --output-target=ihex build/telosb/main.exe build/telosb/main.ihex writing TOS image cp build/telosb/main.ihex build/telosb/main.ihex.out found mote on /dev/ttyUSB0 (using bsl,auto) installing telosb binary using bsl tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p build/telosb/main.ihex.out MSP430 Bootstrap Loader Version: 1.39-goodfet-8 Mass Erase... MSP430 Bootstrap Loader Version: 1.39-goodfet-8 Mass Erase... Traceback (most recent call last): File /home/solar/tinyos-2.x/local/bin/tos-bsl, line 1918, in module main(0); File /home/solar/tinyos-2.x/local/bin/tos-bsl, line 1833, in main for f in toinit: f() File /home/solar/tinyos-2.x/local/bin/tos-bsl, line 1098, in actionMassErase 0xa506) #Required setting for mass erase! File /home/solar/tinyos-2.x/local/bin/tos-bsl, line 757, in bslTxRx self.bslSync(wait) #synchronize BSL File /home/solar/tinyos-2.x/local/bin/tos-bsl, line 716, in bslSync raise BSLException(self.ERR_BSL_SYNC) #Sync. failed __main__.BSLException: Bootstrap loader synchronization error make: *** [program] Error 1 Any help will be greatly appreciated. Thanks, Ankur -- Ankur U. Kamthe EECS, University of California - Merced ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] about RSSI in tinyos 1.x
Hi, what radio are you using? if its the cc2420, look at the datasheet (page 47) http://www-inst.eecs.berkeley.edu/~cs150/Documents/CC2420.pdf if its some other radio then look at their data-sheets, the info should be in there. -- Ankur U. Kamthe EECS, University of California - Merced On Thu, Dec 23, 2010 at 9:58 PM, zhiyong yang zhiyongyang8...@gmail.com wrote: HI everyone ! In struct TOS_Msg, uint8_t strength is defined. After i get the strength data, how can I change it to db? what is the formula? My platform is micaz, in tinyos 1.x. Thanks very much! ___ 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] Error while compiling TestSerial
Hi,
your java seems to be messed up. check if tinyos.jar is in your
classpath variable.
ankur
On Sun, Feb 28, 2010 at 5:23 PM, Alhad Rajurwar arajur...@gmail.com wrote:
Hi there, I am getting this error when I mkdir -p build/telosb
javac -target 1.4 -source 1.4 *.java
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Message.java:84:
cannot find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Message
private SerialPacket serialPacket;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Message.java:676:
cannot find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Message
public SerialPacket getSerialPacket() {
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Message.java:684:
cannot find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Message
protected void setSerialPacket(SerialPacket mySerialPacket) {
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Sender.java:86: cannot
find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Sender
SerialPacket packet =
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Sender.java:87: cannot
find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Sender
new SerialPacket(SerialPacket.offset_data(0) + data.length);
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Sender.java:87: cannot
find symbol
symbol : variable SerialPacket
location: class net.tinyos.message.Sender
new SerialPacket(SerialPacket.offset_data(0) + data.length);
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Sender.java:87:
operator + cannot be applied to SerialPacket.offset_data,int
new SerialPacket(SerialPacket.offset_data(0) + data.length);
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Sender.java:95: cannot
find symbol
symbol : variable Serial
location: class net.tinyos.message.Sender
fullPacket[0] = Serial.TOS_SERIAL_ACTIVE_MESSAGE_ID;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Receiver.java:166:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.message.Receiver
if (packet[0] != Serial.TOS_SERIAL_ACTIVE_MESSAGE_ID)
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Receiver.java:169:
cannot find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Receiver
SerialPacket msg = new SerialPacket(packet, 1);
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Receiver.java:169:
cannot find symbol
symbol : class SerialPacket
location: class net.tinyos.message.Receiver
SerialPacket msg = new SerialPacket(packet, 1);
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Receiver.java:170:
internal error; cannot instantiate Integer(int) at java.lang.Integer to ()
Integer type = new Integer(msg.get_header_type());
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/message/Receiver.java:190:
cannot find symbol
symbol : variable SerialPacket
location: class net.tinyos.message.Receiver
received.dataSet(msg.dataGet(), SerialPacket.offset_data(0) +
msg.baseOffset(),
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:85:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int SYNC_BYTE = Serial.HDLC_FLAG_BYTE;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:87:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int ESCAPE_BYTE = Serial.HDLC_CTLESC_BYTE;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:93:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int P_ACK = Serial.SERIAL_PROTO_ACK;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:95:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int P_PACKET_ACK = Serial.SERIAL_PROTO_PACKET_ACK;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:97:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int P_PACKET_NO_ACK = Serial.SERIAL_PROTO_PACKET_NOACK;
^
/opt/tinyos-2.1.0/support/sdk/java/net/tinyos/packet/Packetizer.java:99:
cannot find symbol
symbol : variable Serial
location: class net.tinyos.packet.Packetizer
final static int P_UNKNOWN =
[Tinyos-help] writing tossim extensions
hi all, Is there a document or a tutorial with an example for writing extensions to tossim in tinyos 2.x. In regards to my question, I only found a reference to an email communication in the tinyos sim-wg dated september 2007 between Phil Levis and Chad Metcalf http://mail.millennium.berkeley.edu/pipermail/sim-wg/2007-September/94.html If not, then is there a starting point from where I could make some headway by playing with some of the existing code. thanks, ankur ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] writing tossim extensions
hi all, Is there a document or a tutorial with an example for writing extensions to tossim in tinyos 2.x. In regards to my question, I only found a reference to an email communication in the tinyos sim-wg dated september 2007 between Phil Levis and Chad Metcalf http://mail.millennium.berkeley.edu/pipermail/sim-wg/2007-September/94.html If not, then is there a starting point from where I could make some headway by playing with some of the existing code. thanks, ankur ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] crossbow IMB400 camera board
Hi all, I noticed that crossbow had a new product out the IMB400 camera/pir sensor board. They say on the web site that they its is compatible with the Imote 2 and they have drivers for tinyos with support on the way for linux. Has anyone ordered them from xbow and is currently using it? Is yes, then could you post your experiences about it. Thanks, Ankur ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Have SenSys 2008 deadlines been extended by 24 hours
Hi all, I apologize for sending this email on the forum but I was forwarded an email from Liqian Luo, a committee member at SenSys 2008 that the deadlines had been extended by 24 hours. However, EDAS is not allowing any changes to existing submissions and I havent received any emails talking about the changes to submission deadlines. I would be grateful if any of you would be able to shed some light on this. Sincerely, Ankur Kamthe Dear Authors of SenSys 2008: Due to technical problems with EDAS that prevented successful upload of several papers prior to the 5pm deadline today, and in the spirit of fairness, we extend the submission deadline until 5pm US Eastern time tomorrow, Tuesday, April 15th. Please upload your paper sufficiently in advance of the new deadline as no further extensions will be given. The EDAS site will reopen shortly. We sincerely apologize for the inconvenience caused by the malfunction. Sincerely, Liqian ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Have SenSys 2008 deadlines been extended by 24 hours
Hi all, Just received an email from EDAS saying that there is a problem with the submission system and that the deadline is extended for 24 hours but this time the authors are just to email the final version of the paper (just one time) to specific email addresses. regards, ankur It seems that EDAS has some submissions issues around the time of the Sensys deadline. Some (but not all) of you may have received an email regarding a 1-day extension. We are reluctant to re-open the Sensys submission site for another full day of general updates and uploads, however. If you feel that EDAS impeded you yesterday, please **email** your final version (pdf only) to: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] We will accept at most one version per paper. We will NOT accept emails after 5pm eastern time. If you are happy with the version uploaded yesterday, you can be confident we have received. Best regards, Margaret Martonosi and Adam Wolisz On Tue, Apr 15, 2008 at 7:10 AM, Ankur Kamthe [EMAIL PROTECTED] wrote: Hi all, I apologize for sending this email on the forum but I was forwarded an email from Liqian Luo, a committee member at SenSys 2008 that the deadlines had been extended by 24 hours. However, EDAS is not allowing any changes to existing submissions and I havent received any emails talking about the changes to submission deadlines. I would be grateful if any of you would be able to shed some light on this. Sincerely, Ankur Kamthe Dear Authors of SenSys 2008: Due to technical problems with EDAS that prevented successful upload of several papers prior to the 5pm deadline today, and in the spirit of fairness, we extend the submission deadline until 5pm US Eastern time tomorrow, Tuesday, April 15th. Please upload your paper sufficiently in advance of the new deadline as no further extensions will be given. The EDAS site will reopen shortly. We sincerely apologize for the inconvenience caused by the malfunction. Sincerely, Liqian ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Maximum payload length for serial communication
Hi all, I am using tinyos1-x with Boomerang for tmotes. Is there anything in the tinyos spec which dictates the maximum length of buffer sent thru the UART to the PC? In the program, I wire my App.UARTSend to UARTNoCRCPacket (App.UARTSend - UARTNoCRCPacket;). I tested with buffer sizes upto 240 bytes (using TOS_Msg struct) and everything worked. However, at TOSH_DATA_LENGTH = 250 the leds on the tmote indicate a successful sendDone but the program on the PC side does not display any message. Could anyone tell me why the mote behaves this way? and what is the max payload limit for serial communication for a tmote? thanks a lot, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Time Synchronization using NetSync
Hi all, I want to use NetSync to provide time synchronization in the Delta app code for Tmotes at full power. In the NetSyncC file it says, never to wire to it but instead use make tmote lowpower. So, when I compile using make tmote lowpower not providing the duty cycle value there but changing the default NETSYNC_DUTYCYCLE value from 5 to 100 hoping to get the desired effect. Will doing this suffice or would it adversely affect the nodes? Thanks, Ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to make an application multi-hop enabled
Hi, If you want an example showing the wiring, take a look at Surge(if using mica/z/2 motes) in the tinyos repository or Delta(if using Moteiv motes). ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tmote I2C problems
Hi Miguel, Assuming your addresses and other things are ok, where/when are you releasing the bus? I had the same problem because the bus was released too soon, so the data was not being written after the address. The fix was to put the ResourceCmd.release in the writeDone event. See the Moteiv implementation at http://www.moteiv.com/community/Boomerang_UART0_Sample there they wait till the transmit buffer is empty and then release the bus. hope this helps, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Port / PIN information on Tmote Sky
Hi Alborz, Take a look at the schematic given in the Tmote Sky datasheet to find out which pin is connected to a certain port. To use the MSP430GeneralIO interface wire it to the MSP430GeneralIOC.Portxx where portxx is the pin of interest. hope this helps, ankur ps: i'm using boomerang with tinyos1-x, so it might be different for T2. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Question regarding Acks for radio messages
Hi all, I was running the CountDualAck program from the tinyos1.x repository. when I run the program the count on the leds on node 1 never increments. Does that mean that none of the messages are being acked by the receiving nodes ? In there, if msg-ack equals zero does it mean that the message was ack'ed by a receiver or is it the other way around? (msg is of type TOS_MsgPtr) thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge in Tinyos
hi, I havent used Deluge,yet and if I read your mail correctly, then you could use TOS_LOCAL_ADDRESS (tos1.x) to check against the value given during installation. Use TOS_NODE_ID for tos2.x ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Access Expansion Connector for Tmote Sky
Hi all, I apologize in advance for asking a hardware related question in this forum but I want to use the 10-pin expansion connector on the Tmote Sky modules without soldering wires to it. Is there any commercially available connector which fits on the expansion connector? Thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Concurrent Radio and Mote-PC communication in Tmote
Hi Joe, Thanks for your reply. regards, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Concurrent Radio and Mote-PC communication in Tmote
Hi, I am trying to write an application wherein the Tmote receives data over the radio and forwards it to the PC via the UART. I was not getting the data to flow correctly into the PC, so I was concerned about the following things: 1. Is 57600 the default baud rate on the Tmote? 2. Do I need to use Resource Arbitration to send data to the PC and do radio communication for the Tmote? I am wiring my send, receive interfaces to UARTNoCRCPacket which wires to HPLUSART1M at the lower levels. HPLUSART1M gives the implementation of USART0 lowlevel functionality. I thought that Resource Arbitration was required only for communication between the radio and UART0. Could anyone correct me if I am making a wrong conclusion? Thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] I2C Communication problem using Tmote
Hi Joe,
I tried with the pullup resistor on the SCL lines, but still couldnt
get any response on the Cyclops side. I then viewed the i2c clock and
data signals on an oscilloscope once with the tmote connected to the
cyclops and then with a micaz. The signals appear totally different in
the two cases. (Waveform photos:
http://www.flickr.com/photos/[EMAIL PROTECTED]/ )
In case of the micaz, the data lines are pulled high after the write
is completed (address of device + data written to the bus) whereas in
case of the tmote the clock lines are high and the data lines remain
low after the first byte and nothing else seems to be transmitted. On
the tmote, the leds toggle indicating a write and writeDone event but
the oscilliscope shows no change on either lines till the mote is
reset.
From the I2C specification description, it says that slave holds the
clock lines low to force the master into a wait state. In my case, the
slave device does not try to force a wait state but doesnt allow a
transfer to continue as well.
I am pasting code snippets for the micaz, tmote and cyclops programs
in the space below. In the program, I used different interfaces for
the micaz and tmote but I use the same set of parameters (slave
address, data) in both cases. I am puzzled by this behavior and would
deeply appreciate any further help in this matter.
thanks,
ankur.
FOR MICAZ:
In Configuration file:
MoteI2CRelayM.I2CPacket - I2CPacketC.I2CPacket[0x80];
In Implementation
call I2CPacket.writePacket(2,(char *)imgData, 0x00);
FOR TMOTE:
In configuration file;
SimpleResponderM.I2CPacketMaster - I2CPacketC.MSP430I2CPacket;
SimpleResponderM.I2CStdControl - I2CPacketC.StdControl;
SimpleResponderM.ResourceCmd - I2CResourceC;
in implementation file:
interface MSP430I2CPacket as I2CPacketMaster;
// when user button is pressed, call task
task void getImageTask() {
imgData[0] = imgResolution;
imgData[1] = SEGMENTSIZE;
atomic {i2c_task = GET_IMAGE_TASK;}
call ResourceCmd.request( RESOURCE_NONE );
}
// After the resource is granted
event void ResourceCmd.granted(uint8_t rh) {
imgData[0] = 64;
imgData[1] = 64;
call I2CPacketMaster.writePacket(rh, i2c_slave_addr, 2, (char*) (imgData));
call ResourceCmd.release();
}
event void I2CPacketMaster.writePacketDone(uint16_t addr, uint8_t
length, uint8_t* data, result_t success) {
if (!success) {
call Leds.redToggle();
}
else {
call Leds.greenToggle();
}
}
CYCLOPS:
In Implementation file:
event char *I2CPacketSlave.write(char *data, uint8_t len) {
call Leds.redToggle();
return data;
}
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] I2C Communication problem using Tmote
To Philip, I am using Boomerang as the I2C interfaces are compatible with the tmote. To Joe: I was not aware that I had to have I2C pullup resistors. My current design does not have any. Is there a schematic which shows the placment of the resistors? Thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] I2C Communication problem using Tmote
Hi all, I am trying to interface a tmote with a cyclops camera. I am using the 10-pin expansion connector of the Tmote for powering the cyclops and using the I2C pins for communication. No other pins are connected between the two devices. The mote is the master and the cyclops is the slave device. I am using the bus arbitration functions ResourceCmd.request(), .granted() and release on the tmote side. I tried setting the addresses on the mote and the cyclops to 0x80, but I wasnt able to elicit any reponse from the cyclops. On the mote side, the writePacketDone() is executed sucessfully, so I thought that cyclops should have received the data. I test the cyclops side by toggling the leds in the *I2CPacketSlave.write() function. My program works (leds toggle) while using the micaz with the cyclops. Only modification being that (1) I swap the MSP430I2CPacket interface for tmote with the I2CPacket interface for the micaz and (2) the micaz 51-pin male connector attaches directly to the corresponding female connector on the cyclops whereas I had to solder the lines from the 10-pin expansion connector on the tmote to an intermediate MDA 100 board Is this because of soldering problems or am I not connecting some lines between the two devices? I would appreciate any help in this regard. Thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Assigning addresses for I2C slave devices for Tmote Sky
Hi all, I was attempting to establish communication between a tmote and a slave i2c device (cyclops camera). The led on the slave device is supposed to blink everytime I press the user button on the mote. I am assigning the slave device the address 0x80 (=value and bcast = true). While writing packets to the I2C bus the mote calls the slave device using address 0x80. I, also tried calling the slave device using 0x00 since bcast is enabled, however I was unable to get any response from the slave device (no leds blink) Could someone be able to tell me if I am atleast assigning the correct addresses to these entities? thanks, ankur for reference: /* * Sets the address of the I2C Slave * * @param value The 7 lower bits of value are the I2C slave address. * @param bcast determines whether slave will respond to general call * address * * @return SUCCESS always */ command result_t setAddress(uint8_t value, bool bcast); ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] I2C hardware support error while compiling for telosb
Hi all, I am trying to get data from the I2C pins on the expansion connector for the Tmote Sky and send it to another mote thru the radio. I have wired the my app called MoteRelay to the I2CPacketC configurations which provides the initialization, arbitration, send/receive packet methods. But when I compile my app (in tinyos 1x), I get the Compiling with hardware I2C support, but MCU does not support I2C error. I looked some more and found that the __msp430_have_usart0_with_i2c was not defined. I was not able to find the definition for that anyplace. Could someone help me with this problem. Thanks, ankur [EMAIL PROTECTED]:/opt/tinyos-1.x/apps/MoteRelay$ make telosb mkdir -p build/telosb compiling MoteRelayC to a telosb binary ncc -o build/telosb/main.exe -O -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -I%T/lib/Deluge -Wl,--section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DIDENT_PROGRAM_NAME=\MoteRelayC\ -DIDENT_USER_ID=\akamthe\ -DIDENT_HOSTNAME=\venus\ -DIDENT_USER_HASH=0xee29689cL -DIDENT_UNIX_TIME=0x45d2355eL -DIDENT_UID_HASH=0xc2d3ff04L -mdisable-hwmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio MoteRelayC.nc -lm /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CM.nc:60:2: #error MSP430I2C: Compiling with hardware I2C support, but MCU does not support I2C In file included from /opt/tinyos-1.x/tos/platform/telosb/I2CPacketC.nc:38, from MoteRelayC.nc:33: In component `MSP430I2CC': /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:45: failed to preprocess /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CM.nc /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:47: no match /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:48: no match /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:49: no match /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:50: no match /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:52: cannot find `USARTControl' /opt/tinyos-1.x/tos/platform/msp430/MSP430I2CC.nc:53: cannot find `HPLI2CInterrupt' make: *** [exe0] Error 1 [EMAIL PROTECTED]:/opt/tinyos-1.x/apps/MoteRelay$ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] I2C hardware support error while compiling for telosb
hi Xiaofan, thanks for your email. When I compiled it under the moteiv version it worked. however, can anyone explain why this occurs. Does this mean that the telosb/Tmote platforms are not fully supported in TOS 1.x? thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems using enums
Hi all,
I trying using enum inside a program in tinyos. However, the program
compiles for mica2 but while compiling for telosb (using tinyos1.x)
the compiler gives the following error:
In component `BlinkM':
BlinkM.nc:47: syntax error before `0x0001'
make: *** [exe0] Error 1
The statement at line 47 is: enum{INIT,BUSY};
Could someone tell me what I am doing wrong. The program is quite
simple and works without the enum statement. But I was planning to use
enum in a different program and the same error comes up. I am pasting
the program below for reference.
regards,
ankur
Blink.nc
configuration Blink {
}
implementation {
components Main, BlinkM, SingleTimer, LedsC;
Main.StdControl - SingleTimer.StdControl;
Main.StdControl - BlinkM.StdControl;
BlinkM.Timer - SingleTimer.Timer;
BlinkM.Leds - LedsC;
}
BlinkM.nc
module BlinkM {
provides {
interface StdControl;
}
uses {
interface Timer;
interface Leds;
}
}
implementation {
enum {INIT,BUSY} ;
uint8_t state;
command result_t StdControl.init() {
call Leds.init();
state = INIT;
return SUCCESS;
}
command result_t StdControl.start() {
return call Timer.start(TIMER_REPEAT, 1000);
}
event result_t Timer.fired() {
if(state == INIT){
state = BUSY;
}
else{
state = INIT;
}
call Leds.redToggle();
return SUCCESS;
}
}
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems using enums
Hi Michael,
I tried that along with
typedef enum {INIT=0,BUSY=1} states;
states state;
I always end up getting the compiler error
ankur
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems using enums
hi Michael, I found out my mistake. It seems INIT, BUSY are already used by telosb platform someplace. I replaced the names and it worked. thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Accessing particular digital I/O pins in Tmote Sky
Hi all,
I was trying to use the pins on the expansion connector for Tmote Sky
on a project. I started by writing a simple program that would toggle
one of the Exclusive Digital I/O pins but was not sure how to
address/indentity a particular pin in TOS. In the program, I set a
particular port for the ADC, set the pin as an output pin and toggle
it. Everytime my pin toggles, one of the LEDs also toggles. When I try
Port23 : Pin 3 of the 6-pin expansion connector toggles and for Port
26: pin 4 of the 6pin expansion connector toggles.
Could someone point me to any resource which explains the pin mapping
or explain this behavior? My aim is to toggle pin 7/10 on the 10 pin
expansion connector, which are dual purpose pins (primary: analog
input 2, secondary: exclusive digital i/o). I am pasting the program I
used to test the pins after this email.
TestAppC.nc: Top Level Configuration File
BlinkC.nc: Main Section which toggles the timer, leds and pins
HplUserButtonC.nc: Wiring for I/O pin
thanks,
ankur
1. Makefile
COMPONENT=TestAppC
include $(MAKERULES)
2. TestAppC.nc
configuration TestAppC
{
}
implementation
{
components MainC, BlinkC, LedsC;
components new TimerMilliC() as Timer0;
components new TimerMilliC() as Timer1;
components new TimerMilliC() as Timer2;
BlinkC - MainC.Boot;
BlinkC.Timer0 - Timer0;
BlinkC.Timer1 - Timer1;
BlinkC.Timer2 - Timer2;
BlinkC.Leds - LedsC;
components HplUserButtonC;
BlinkC.GeneralIO - HplUserButtonC.GeneralIO;
}
3. BlinkC.nc
#include Timer.h
module BlinkC
{
uses interface GeneralIO;
uses interface TimerTMilli as Timer0;
uses interface TimerTMilli as Timer1;
uses interface TimerTMilli as Timer2;
uses interface Leds;
uses interface Boot;
}
implementation
{
event void Boot.booted()
{
call GeneralIO.makeOutput();
if(call GeneralIO.isOutput()){
call Timer2.startPeriodic( 5000 );
}
else{
call Timer1.startPeriodic( 1000 );
call Timer0.startPeriodic( 2000 );
}
}
event void Timer0.fired()
{
dbg(BlinkC, Timer 0 fired @ %s.\n, sim_time_string());
call GeneralIO.toggle();
call Leds.led0Toggle();
}
event void Timer1.fired()
{
dbg(BlinkC, Timer 1 fired @ %s \n, sim_time_string());
call GeneralIO.toggle();
call Leds.led1Toggle();
}
event void Timer2.fired()
{
dbg(BlinkC, Timer 2 fired @ %s.\n, sim_time_string());
call GeneralIO.toggle();
call Leds.led2Toggle();
}
}
4. HplUserButtonC.nc
configuration HplUserButtonC {
provides interface GeneralIO;
}
implementation {
components HplMsp430GeneralIOC as GeneralIOC;
components new Msp430GpioC() as TogglePinC;
TogglePinC - GeneralIOC.Port23;
GeneralIO = TogglePinC;
}
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Flashing cyclops camera application memory
Hi all, I am trying to load a program into the Cyclops camera board application memory using tmote sky. Generally, a cyclops board loads a program similar to a mote using the MIB510 programmer. However, while doing it from a mote, I had the following questions: 1. Is the tos_image.xml the binary or is it the main.ihex file? Both of them are quite similar content-wise. Each line consists of 42 hex characters (only the last 6-7 lines are smaller). Is there pattern to the content of a line. 2. Both the files contain hex code, how do I transfer this to the cyclops which has 16bit memory? If I were to write into a memory location, what would be stored at the higher byte and the lower byte. Are there any references for this kind of work. I am reading thru the material on Deluge and trying to figure out any similarities as regards reprogramming the mote. thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Programming the atmega128 without MIB510
Hi all, I am trying to program the atmega128 inside the cyclops camera board using a mote (Tmote Sky). Generally, it (atmega inside the cyclops) is programed using the MIB510 board. Is there any resource which tells users how the MIB510 operates (like which pins it activates on the 51 pin connector to reprogram a device). All I could gather from the MIB510 manual is that the board has an Atmega16L chip which acts as the In-System Programmer. However, details were missing. I have also read the atmel128 manual as regards programming but still couldnt figure out how these pins would interact with the MIB510. Are there are resources regarding the working of the MIB510 which I could read ? thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] getenv JNI library not found. Env.getenv will not work
hi, Also, while installing TinyOS as per the instructions given in http://www.tinyos.net/tinyos-1.x/doc/install.html , while installing the javax.comm package, the zip file that I obtained from Sun's site was named comm2.0.3.zip, not javacomm20-win32.zip . Is the win32com.dll file supposed to be contained within javacomm20-win32.zip? comm2.0.3.zip didn't yield any such file on unzipping, nor did it give any javax.comm.properties file. Have I downloaded the wrong file than? Can anyone help? read this message on the java forums on sun.com http://forum.java.sun.com/thread.jspa?threadID=680756 they have a link to javacomm20-win32.zip which I have pasted below: http://www.idicalif.com/scripts/meta.idc?teamkey=FSUNlink=http://24.234.143.242/p5/javacomm20-win32.zip try using this version.. regards, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Getting Data from Tmote Sky's Sensors
Hi, first of all thanks to michael schippling and jon gomez... i'm using tinyos1-x and both of you were right, my toscomm is messed up but I still cant figure it out. my library path is: library path: /usr/lib/jvm/java- 1.5.0-sun-1.5.0.06 /jre/lib/i386/client:/usr/lib/jvm/java-1.5.0-sun-1.5.0.06 /jre/lib/i386:/usr/lib/jvm/java-1.5.0-sun-1.5.0.06/jre/../lib/i386 first of all I had two libtoscomm.so files one in /usr/lib/tinyos and the second in /usr/lib/jvm/java- 1.5.0-sun-1.5.0.06/jre/lib/i386/ Executing nm libtoscomm.so gives db5c T Java_net_tinyos_comm_TOSCommJNI_NativeSerial_1read_1_1SWIG_10 df88 T Java_net_tinyos_comm_TOSCommJNI_NativeSerial_1read_1_1SWIG_11 so the read methods exist.. which is one good news... Executing ldd libtoscomm.so gives linux-gate.so.1 = (0xe000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7eac000) libm.so.6 = /lib/tls/i686/cmov/libm.so.6 (0xb7e8a000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0xb7e8) libc.so.6 = /lib/tls/i686/cmov/libc.so.6 (0xb7d51000) /lib/ld- linux.so.2 (0x8000) so, my libstdc++ and gcc libraries seem to be in order. however, linux-gate.so.1 points to nothin, so does that mean that its not linked ? I did not find any mention of libtoscomm (or associated paths) in my CLASSPATH. could that be the problem ? Could you please help me with this ? regards, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Re: Getting Data from Tmote Sky's Sensors
my problem was that I want able to get any data from the sensors when trying the Oscilloscope program from Moteiv. as for javax.comm, I have installed that and when i execute toscheck it says javax.comm ok. Plus, I have the javax.servlet.jar in the classpath. I followed the wiki link you sent and tried the steps to install TOSComm and I ended up with tons of errors which look like this (pasted below) does this mean there is a problem with my compiler (c/java) ?? ankur /usr/include/linux/signal.h:2:2: warning: #warning You should include signal.h. This time I will do it for you. /usr/include/linux/signal.h:4:20: error: #include nested too deeply In file included from NativeSerial_linux.cpp:512: build_linux/TOSComm_wrap.cxx:108:17: error: jni.h: No such file or directory /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstddef:52: error: '::ptrdiff_t' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstddef:53: error: '::size_t' has not been declared /usr/include/string.h:39: error: 'size_t' has not been declared /usr/include/string.h:43: error: 'size_t' has not been declared /usr/include/string.h:52: error: 'size_t' has not been declared /usr/include/string.h:59: error: 'size_t' has not been declared /usr/include/string.h:62: error: 'size_t' has not been declared /usr/include/string.h:66: error: 'size_t' has not been declared /usr/include/string.h:77: error: 'size_t' has not been declared /usr/include/string.h:88: error: 'size_t' has not been declared /usr/include/string.h:96: error: 'size_t' has not been declared /usr/include/string.h:102: error: 'size_t' has not been declared /usr/include/string.h:109: error: 'size_t' does not name a type /usr/include/string.h:124: error: 'size_t' does not name a type /usr/include/string.h:138: error: 'size_t' has not been declared /usr/include/string.h:184: error: 'size_t' does not name a type /usr/include/string.h:188: error: 'size_t' does not name a type /usr/include/string.h:225: error: 'size_t' has not been declared /usr/include/string.h:226: error: 'size_t' has not been declared /usr/include/string.h:232: error: 'size_t' has not been declared /usr/include/string.h:235: error: 'size_t' has not been declared /usr/include/string.h:242: error: 'size_t' does not name a type /usr/include/string.h:249: error: 'size_t' does not name a type /usr/include/string.h:281: error: 'size_t' has not been declared /usr/include/string.h:288: error: 'size_t' has not been declared /usr/include/string.h:292: error: 'size_t' has not been declared /usr/include/string.h:296: error: 'size_t' has not been declared /usr/include/string.h:299: error: 'size_t' has not been declared /usr/include/string.h:329: error: 'size_t' has not been declared /usr/include/string.h:341: error: 'size_t' has not been declared /usr/include/string.h:370: error: 'size_t' has not been declared /usr/include/string.h:373: error: 'size_t' has not been declared /usr/include/string.h:380: error: 'size_t' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstring:89: error: '::strxfrm' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstring:90: error: '::strcspn' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstring:91: error: '::strspn' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstring:95: error: '::strlen' has not been declared /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/cstring:100: error: 'size_t' has not been declared /usr/include/stdlib.h:140: error: 'size_t' does not name a type /usr/include/linux/time.h:10: error: 'time_t' does not name a type /usr/include/linux/time.h:16: error: 'time_t' does not name a type /usr/include/linux/time.h:17: error: 'suseconds_t' does not name a type /usr/include/bits/time.h:69: error: redefinition of 'struct timeval' /usr/include/linux/time.h:15: error: previous definition of 'struct timeval' /usr/include/bits/pthreadtypes.h:50: error: 'size_t' does not name a type /usr/include/bits/pthreadtypes.h:53: error: 'size_t' does not name a type /usr/include/stdlib.h:450: error: 'size_t' has not been declared /usr/include/stdlib.h:480: error: 'size_t' has not been declared /usr/include/stdlib.h:584: error: 'size_t' was not declared in this scope /usr/include/stdlib.h:584: error: expected ',' or ';' before 'throw' /usr/include/stdlib.h:586: error: 'size_t' was not declared in this scope /usr/include/stdlib.h:586: error: 'size_t' was not declared in this scope /usr/include/stdlib.h:586: error: initializer expression list treated as compound expression /usr/include/stdlib.h:587: error: expected ',' or ';' before 'throw' /usr/include/stdlib.h:595: error: 'size_t' has not been declared /usr/include/alloca.h:33: error: 'size_t' was not declared in this scope /usr/include/alloca.h:33: error:
[Tinyos-help] Getting Data from Tmote Sky's Sensors
Hi, I was trying to execute the Oscilloscope program to acquire data from the Tmote Sky sensors. I install the Oscilloscope program on one node and TOSBase on another (which is connected to the PC). I dont get any error messages or warnings at this step. Then when I start Serial Forwarder I get the following messages: [EMAIL PROTECTED]:/opt/moteiv/$ java net.tinyos.sf.SerialForwarder -comm serial@/dev/ttyUSB0:tmote Exception in thread Thread-3 java.lang.UnsatisfiedLinkError: NativeSerial_read at net.tinyos.comm.TOSCommJNI.NativeSerial_read (Native Method) at net.tinyos.comm.NativeSerial.read(NativeSerial.java:65) at net.tinyos.comm.TOSSerial$ReadThread.flush(TOSSerial.java:59) at net.tinyos.comm.TOSSerial.init(TOSSerial.java :177) at net.tinyos.packet.SerialByteSource.openStreams( SerialByteSource.java:58) at net.tinyos.packet.StreamByteSource.open(StreamByteSource.java:51) at net.tinyos.packet.Packetizer.openSource (Packetizer.java:119) at net.tinyos.packet.AbstractSource.open(AbstractSource.java:77) at net.tinyos.packet.Packetizer.open(Packetizer.java:114) at net.tinyos.packet.PhoenixSource.run(PhoenixSource.java :167) Java TOSSerial finalize When I try to run java com.moteiv.oscope.oscilloscope after that from the Oscilloscope directory I dont see any output on the Oscilloscope screen (even after checking the scrolling and zoom out Y axis) . I realize the java.lang.UnsatisfiedLinkError: has something to do with missing libraries or dependencies, but I am unable to make any progress. Could you please help me with this? thanks, ankur ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] some corrections for tinyos 2.0 tutorials
Hi,
I noticed some typos/omissions in the tinyOS 2.0 tutorials. I am appending
them at the end of the email. Thanks for the great tutorials.
Please excuse me if I am mailing on the wrong list but there were no contact
email addresses in the tutorials
regards,
Ankur
In Lesson 3: http://www.tinyos.net/tinyos-2.x/doc/html/tutorial/lesson3.html
***
1. message_t packet; should be message_t pkt; in the following section
(gives 'pkt' undeclared in Timer0.fired function)
implementation {
bool busy = FALSE;
message_t packet;
...
}
**
*
2. BlinkToRadioMsg* btrmsg should be BlinkToRadioMsg* btrpkt in the
following section (gives 'btrpkt' undeclared error):
event message_t* Receive.receive(message_t* msg, void* payload, uint8_t len)
{
if (len == sizeof(BlinkToRadioMsg)) {
BlinkToRadioMsg* btrmsg = (BlinkToRadioMsg*)payload;
call Leds.set(btrpkt-counter);
}
return msg;
}
**
**
3. Need to add the following function for the program to compile
(gives AMControl.stopDone' not implemented error).
event void AMControl.stopDone(error_t err) {
}
**
**
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
