Hi, In your test, I saw one problem:
sudo pppd debug passive noauth nodetach 115200 /dev/ttyUSB0 nocrtscts nocdtrcts lcp-echo-interval 0 noccp noip ipv6 ::23,::24 The default baudrate on iris is 56700, not 115200, and it's serial port is usually /dev/ttyUSB1 (but it depends on your system). I tried to get Blip2 to run on ucmini motes (it has 16k RAM), unfortunatly it didn't work after I ported the rf230 modifications to rfa1. I could connect to the router with the command above, and installed UDPEcho, but nothing else worked from the tutorial (altough after some commands the first led blinked on the router). I couldn't test with telsob motes, since I don't have any. I'd like to fix that, but I don't know blip at all. If anyone could help me how to debug it, I'd put some time into it. Andris On Thu, Oct 4, 2012 at 11:25 AM, Sebastian Scheibe <[email protected]> wrote: > Hello everyone, > > I'm interested in anybody, who has experiences with Blip 2.0 / RPL tested on > IRIS-motes or other RF230 hardware platforms. > > > > I tried to test PppRouter and UDPEcho on IRIS-motes, but both applications > doesn't work either, although no errors occur while compiling. > > I use the following toolchains: > > * AVR-GCC: avr-gcc (GCC) 4.1.2 > * MSP-GCC: msp430-gcc (GCC) 4.6.3 20120301 > * NesC: nescc: 1.3.4 > * TinyOS repository of Miklos Maroti (mmaroti-tinyos-b6d93cb) > (https://github.com/mmaroti/tinyos.git) > > -> official TinyOS-2.1.2 trunk ( > http://tinyos-main.googlecode.com/svn/trunk/) throws the following errors > compiling UDPEcho for IRIS: > > root@ubuntu:/opt/tinyos-2.x/apps/UDPEcho# make iris blip > mkdir -p build/iris > compiling UDPEchoC to a iris binary > ncc -o build/iris/main.exe -Os -DRPL_ROUTING -DRPL_STORING_MODE > -I/opt/tinyos-2.1.2/tos/lib/net/rpl -DREPORT_DEST=\"fec0::100\" -DBLIP_STATS > -DBLIP_DERIVE_SHORTADDRS -DIN6_PREFIX=\"fec0::\" > -DCC2420_HW_ACKNOWLEDGEMENTS -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK > -DTOSH_DATA_LENGTH=112 -I/opt/tinyos-2.1.2/tos/lib/net/ > -I/opt/tinyos-2.1.2/tos/lib/printf/ -I/opt/tinyos-2.1.2/support/sdk/c/blip/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/interfaces/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/nwprog/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/shell/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/serial/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/platform/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/icmp/ > -I/opt/tinyos-2.1.2/tos/lib/net/blip/dhcp/ > /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/iovec.c > /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/in_cksum.c > /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/ip_malloc.c > /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/utility.c > /opt/tinyos-2.1.2/tos/lib/net/blip/table.c -fnesc-separator=__ -Wall > -Wshadow -Wnesc-all -target=iris -fnesc-cfile=build/iris/app.c -board=micasb > -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 > -Ibuild/iris -DCC2420_DEF_CHANNEL=13 -DRF230_DEF_CHANNEL=13 > -DIDENT_APPNAME=\"UDPEchoC\" -DIDENT_USERNAME=\"root\" > -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L > -DIDENT_TIMESTAMP=0x505ba0fdL -DIDENT_UIDHASH=0xb0cfd6c1L -fnesc-dump=wiring > -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, > components)' -fnesc-dumpfile=build/iris/wiring-check.xml UDPEchoC.nc -lm > In file included from > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressC.nc:6, > from /opt/tinyos-2.1.2/tos/lib/net/blip/IPAddressC.nc:28, > from > /opt/tinyos-2.1.2/tos/lib/net/blip/IPNeighborDiscoveryC.nc:11, > from /opt/tinyos-2.1.2/tos/lib/net/blip/IPStackC.nc:47, > from UDPEchoC.nc:46: > In component `Ieee154AddressP': > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc:9: interface > CC2420Config not found > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc: In function > `Ieee154Address.setShortAddr': > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc:43: interface has no > command or event named `setShortAddr' > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc:44: interface has no > command or event named `sync' > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc: At top level: > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressP.nc:49: `syncDone' is not > in interface `CC2420Config' > In file included from /opt/tinyos-2.1.2/tos/lib/net/blip/IPAddressC.nc:28, > from > /opt/tinyos-2.1.2/tos/lib/net/blip/IPNeighborDiscoveryC.nc:11, > from /opt/tinyos-2.1.2/tos/lib/net/blip/IPStackC.nc:47, > from UDPEchoC.nc:46: > In component `Ieee154AddressC': > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressC.nc:15: component > CC2420ControlC not found > /opt/tinyos-2.1.2/tos/lib/net/blip/Ieee154AddressC.nc:16: no match > In file included from /opt/tinyos-2.1.2/tos/lib/net/blip/IPStackC.nc:48, > from UDPEchoC.nc:46: > In component `IPDispatchC': > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:43: component CC2420RadioC > not found > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:58: no match > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:60: cannot find > `BarePacket' > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:61: cannot find `BareSend' > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:62: cannot find > `BareReceive' > /opt/tinyos-2.1.2/tos/lib/net/blip/IPDispatchC.nc:69: no match > make: *** [exe0] Error 1 > root@ubuntu:/opt/tinyos-2.x/apps/UDPEcho# > > For this reason, I chose the repository of M. Maroti (see above). With this, > no errors occur while compiling the sources of PppRouter or UDPEcho for > IRIS-motes. > > Both Applications, PppRouter and UDPEcho, are working fine on Telosb- and > Tmote nodes. The problems with IRIS-motes are listed below: > > > > # PppRouter seems to fail because of the limited RAM size on the IRIS-motes > (8 KB). > > The recommended memory size of the compiled code of PppRouter is 56998 bytes > in ROM and 10257 bytes in RAM. > > When I tried to connect to the mote using the pppd-driver as explained in > the tutorials: > > sudo pppd debug passive noauth nodetach 115200 /dev/ttyUSB0 nocrtscts > nocdtrcts lcp-echo-interval 0 noccp noip ipv6 ::23,::24 > > no output occurs. In the end I installed PppRouter on a Telosb-mote to > continue testing UDPEcho on IRIS-motes. > > Makefile of PppRouter: > > COMPONENT=PppRouterC > # PFLAGS += -DENABLE_SPI0_DMA > > PFLAGS += -DRF230_DEF_CHANNEL=13 > > PFLAGS += -DCC2420_DEF_CHANNEL=13 > > # use rpl > PFLAGS += -DRPL_ROUTING -DRPL_STORING_MODE -I$(LOWPAN_ROOT)/tos/lib/net/rpl > # PFLAGS += -DRPL_OF_MRHOF > > # and ppp > PFLAGS += -I$(TOSDIR)/lib/ppp > PFLAGS += -I$(TOSDIR)/lib/fragpool > > # this works around fragmentation in the RX buffer pool > PFLAGS += -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 > > # if you set this, the stack won't use dhcp to assign addresses -- it > # will use this prefix combined with TOS_NODE_ID > PFLAGS += -DIN6_PREFIX=\"fec0::\" > > # derive short address from the dhcp address assignment, if possible > PFLAGS += -DBLIP_DERIVE_SHORTADDRS > > include $(MAKERULES) > > > > # UDPEcho actually should work, because it only recommends 38656 bytes in > ROM and 7108 bytes in RAM. > > When booted, the motes leds start toggling normally but no message is sent. > I approved this by a packet sniffer. > Is there a problem with the rfxlink stack? I'm inexpierienced with this > topic, so it seems to be impossible for me debugging this alone. > > > Makefile of UDPEcho: > > COMPONENT=UDPEchoC > # uncomment this for network programming support > # BOOTLOADER=tosboot > > # radio options > PFLAGS += -DCC2420_DEF_CHANNEL=13 > PFLAGS += -DRF230_DEF_CHANNEL=13 > # CFLAGS += -DCC2420_DEF_RFPOWER=4 -DENABLE_SPI0_DMA > > # enable dma on the radio > # PFLAGS += -DENABLE_SPI0_DMA > > # you can compile with or without a routing protocol... of course, > # without it, you will only be able to use link-local communication. > PFLAGS += -DRPL_ROUTING -DRPL_STORING_MODE -I$(TOSDIR)/lib/net/rpl > # PFLAGS += -DRPL_OF_MRHOF > > # tell the 6lowpan layer to not generate hc-compressed headers > # PFLAGS += -DLIB6LOWPAN_HC_VERSION=-1 > > # if this is set, motes will send debugging information to the address > # listed. BLIP_STATS causes blip to record statistics. > # you can log this information using the util/Listener.py script > PFLAGS += -DREPORT_DEST=\"fec0::100\" -DBLIP_STATS > > # if you're using DHCP, set this to try and derive a 16-bit address > # from the IA received from the server. This will work if the server > # gives out addresses from a /112 prefix. If this is not set, blip > # will only use EUI64-based link addresses. If not using DHCP, this > # causes blip to use TOS_NODE_ID as short address. Otherwise the > # EUI will be used in either case. > PFLAGS += -DBLIP_DERIVE_SHORTADDRS > > # this disables dhcp and statically chooses a prefix. the motes form > # their ipv6 address by combining this with TOS_NODE_ID > PFLAGS += -DIN6_PREFIX=\"fec0::\" > > # PFLAGS += -DNEW_PRINTF_SEMANTICS -DPRINTFUART_ENABLED > > include $(MAKERULES) > > > I've read that these applications work fine in simulations, but were they > already tested on real hardware? > Is there a solution for porting Blip2.0/RPL on RF230-hardware? > > Is there anyone who had similar problems and got them solved? Who else is > working on that problem? > Maybe we can solve this problem by supporting each other! > > Best regards, > Sebastian Scheibe > > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
