Hi Dec,

I just tested the repository using XubunTOS in VirtualBox and adapted
the Readme:

General setup:
- clone this repository
- Adapt paths (TOSROOT, TOSDIR...)
- cd to support/sdk/c/blib
- Execute
 ./bootstrap.sh
 ./configure
 make

How to compile the app and run the simulation:
- cd to apps/UDPEcho
- Build simulation libraries: make micaz sim-rpl blip
- Start the simulation: ./sim/Simulation.py
- The results are located in sim/output/suite_<date>/

It is more or less the same you figured out. Perhaps this helps someone
else.

I wish you good luck with the simulation!

Best regards,

Jens

Am 06.09.2013 17:30, schrieb Declan Delaney:
> 
> On Fri, Sep 6, 2013 at 11:41 AM, Declan Delaney
> <[email protected] <mailto:[email protected]>> wrote:
> 
>     Yes, this is a great help.
> 
>     I am able to make with the "sim" option
> 
>     I am not able to run make with the "sim-rpl" option however.
> 
> 
> Ive managed to make the program with sim-rpl:
> $ make micaz blip sim-rpl
> and have managed to run the simulations successfully.
>  
> 
> 
>     The sim-rpl.extra file in support/make is trying to include some
>     object files that are not available.
> 
> 
> The object files that were missing pertain to the blip lowpan library in
> "/support/sdk/c/blip/lib6lowpan/"
> 
>     Is there a certain process that I should follow to get this all
>     running smoothly together?
> 
> 
> Process I went through to get to this stage:
> clone reo. -  https://github.com/jdede/tinyos-main
> 
> run bootstrap.sh in /support/sdk/c/blip/
> run configure in /support/sdk/c/blip/
> run make in /support/sdk/c/blip/lib6lowpan/
> 
> Then make program in /apps/UDPEcho/
> $make micaz blip sim-rpl
> 
> ... and thats about it.
>  
> 
> 
>     Thanks again for your help.
>     Dec
> 
> 
> 
>     On Thu, Sep 5, 2013 at 11:45 AM, Jens Dede <[email protected]
>     <mailto:[email protected]>> wrote:
> 
>         The modified file is the UDPEchoP.nc. There you will find the
>         following
>         lines:
> 
>         #ifdef TOSSIM
>         #ifdef RPL_ROUTING
>              if (TOS_NODE_ID == SOURCE_NODE_ID) {
>               if(TOS_NODE_ID == RPL_ROOT_ADDR){
>                 dbg ("UDPEchoP", "Root ID = %d.\n", TOS_NODE_ID);
>                 call RootControl.setRoot();
>               }
> 
>               call UDPReceive.bind(SOURCE_NODE_PORT);
>               call StatusTimer.startOneShot(1024*WAITTIME);
>               route_dest.sin6_port = htons(DEST_NODE_PORT);
>               inet_pton6(DEST_NODE_IP, &route_dest.sin6_addr);
>               dbg("UDPEchoP","Begin with Destination Node = %X:%X:%X on
>         Port =
>         %i   \n",ntohs(route_dest.sin6_addr.s6_addr16[0]),
>         ntohs(route_dest.sin6_addr.s6_addr16[3]),
>         ntohs(route_dest.sin6_addr.s6_addr16[7]),
>         ntohs(route_dest.sin6_port));
>             }
>         #endif
>         #endif
> 
>         Using this lines, a UDPEcho node acts as the root node. You are not
>         using a PPPRouter anymore. So you can use the same application
>         on all nodes.
> 
>         The simulation (located in sim) starts this application with a
>         scenario
>         defined in sim/config.py. After a defined time, the simulation is
>         stopped and the log output from the nodes is parsed by the
>         evaluation
>         suite. This creates graphs and statistics from the simulation.
>         So you
>         can test your application in huge network scenarios and evaluate for
>         example some timings.
> 
>         Hope that helps.
> 
> 
>         Jens
> 
>         Am 05.09.2013 12:29, schrieb Declan Delaney:
>         > Thanks Srikanth and Jens for your reply,
>         >
>         > I will first take a look a Jens code and see if I can find a
>         solution
>         > that works for my case. I will post any results I get to the list.
>         >
>         > Jens, you mentioned that you modified the TCPEcho application
>         in your
>         > repo. to work with sim..... Is this still the best place to
>         start looing
>         > around?
>         >
>         > Thanks,
>         > Dec
>         >
>         >
>         > On Wed, Sep 4, 2013 at 11:10 PM, Jens Dede
>         <[email protected] <mailto:[email protected]>
>         > <mailto:[email protected]
>         <mailto:[email protected]>>> wrote:
>         >
>         >     Hi Dec,
>         >
>         >     you found a very old repository. At present, I'm not
>         working with
>         >     tinyos. Due to some toolchain problems, I cannot test the
>         simulation at
>         >     present.
>         >     However, I pushed the old repository to github:
>         >
>         >     https://github.com/jdede/tinyos-main
>         >
>         >     Maybe that works for you.
>         >
>         >     Hope that helps.
>         >
>         >     Best regards,
>         >
>         >     Jens
>         >
>         >
>         >     Am 04.09.2013 12:13, schrieb Declan Delaney:
>         >     > Hi all!
>         >     >
>         >     > I am running into problems trying to compile a program
>         for TOSSIM
>         >     using
>         >     > the blip stack.
>         >     > I know this has been asked in the past, but currently it
>         seems
>         >     there is
>         >     > no solution.
>         >     >
>         >     > Firstly:
>         >     > Has anybody managed to compile a TinyOS program using
>         the blip
>         >     stack for
>         >     > TOSSIM(i.e. Using: $ make micaz sim blip)?
>         >     >
>         >     > I have seen a couple of solutions to this online:
>         >     >        1. Using Tossim.patch - Instructions in TinyOS
>         doc files:
>         >     >
>         >     >
>         >    
>         
> https://github.com/tinyos/tinyos-main/blob/master/tos/lib/net/blip/doc/README-SIM
>         >     >            The patch file is no longer available in the
>         git repo.
>         >     >            Has anyone used this technique successfully?
>         >     >        2. Using Solution posed by Jens Dede:
>         >     >
>         >     >
>         >    
>         
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/2012-March/054444.html
>         >     >            The repo. pointed to in this solution is
>         however no longer
>         >     > available.
>         >     >            Has anyone used this technique successfully?
>         >     >
>         >     > Any program using the blip stack creates a binary larger
>         than that
>         >     which
>         >     > the micaz can handle:
>         >     > Will this be a problem in simulation, or can the RAM be
>         extended under
>         >     > simulation environment?
>         >     >
>         >     > Failing the use of TOSSIM in this instance, can anyone
>         advise a decent
>         >     > simulator which can model the CC2420 radio, with a quick
>         enough
>         >     learning
>         >     > curve? (Avrora?, OMNet++?, NS2?)
>         >     >
>         >     > Thanks for any information you can offer,
>         >     > Dec
>         >     >
>         >     >
>         >     > _______________________________________________
>         >     > Tinyos-help mailing list
>         >     > [email protected]
>         <mailto:[email protected]>
>         >     <mailto:[email protected]
>         <mailto:[email protected]>>
>         >     >
>         >    
>         
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>         >     >
>         >     _______________________________________________
>         >     Tinyos-help mailing list
>         >     [email protected]
>         <mailto:[email protected]>
>         >     <mailto:[email protected]
>         <mailto:[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

Reply via email to