[riot-users] sixlowapp Ping not working in SAM R21

Abdulkhadar Abdulla khadar4u at hotmail.com
Wed Apr 8 08:35:36 CEST 2015


Hi,
I observed another problem, when using sixlowapp with SAM R21. I have 3 sam r21 boards. I flashed sixlowapp in all the boards. When I start the boards, one of the node freezes but other two nodes can exchange data using nc command. Any of you observed this problem before?
ThanksAbdul

From: khadar4u at hotmail.com
To: users at riot-os.org
Date: Sat, 4 Apr 2015 07:46:41 -0700
Subject: Re: [riot-users] sixlowapp Ping not working in SAM R21




sure. Thank you.
ThanksAbdul

From: ranebalslev at gmail.com
Date: Sat, 4 Apr 2015 15:58:59 +0200
To: users at riot-os.org
Subject: Re: [riot-users] sixlowapp Ping not working in SAM R21

Check out my branch named beehive

Sendt fra min iPhone
Den 04/04/2015 kl. 14.51 skrev Abdulkhadar Abdulla <khadar4u at hotmail.com>:






I tried this once by setting the RPL_MAX_ROUTING_ENTRIE as 6. The application complied but it didn't start after flashing the image to the board. I will try do more experiments on this with different routing entry values.
Thanks

Abdul
On Apr 4, 2015 4:44 PM, Lotte Steenbrink <lotte.steenbrink at fu-berlin.de> wrote:


Hi Abdul,



Am 04.04.2015 um 06:42 schrieb Abdulkhadar Abdulla <khadar4u at hotmail.com>:




Hi,



Thank you. This worked for me. I increased the KERNEL_CONF_STACKSIZE_DEFAULT to 2K to
 make things works for my application.



I see that we have problems in making rpl_udp application working in SAM R21 due to the RAM
 limitation. Is there anyway, we can make this work in the platform?










Have you already tried decreasing RPL_MAX_ROUTING_ENTRIES, if that's possible for your network size?



Cheers,
Lotte






Thanks
Abdul




Date: Sat, 28 Mar 2015 20:15:00 +0530

From: khadar4u at hotmail.com

To: users at riot-os.org

Subject: Re: [riot-users] sixlowapp Ping not working in SAM R21



Hi Lucas,
Thank you. I will apply the patch and update you the progress.
Thanks again.

Abdul
On Mar 28, 2015 6:58 PM, =?ISO-8859-1?Q?Lucas_Jen=DF?= <lists at x3ro.de> wrote:



Hi Abdul,



The ping issue should be

fixed by applying https://github.com/RIOT-OS/RIOT/pull/2727. The next problem

you might run into with the sixlowapp is that the stacksize settings for the

SAM R21 board are currently a little conservative, which causes it to run out

of memory when trying to send a UDP packet with the nc command of the sixlowapp.

This can be “fixed” by increasing the KERNEL_CONF_STACKSIZE_DEFAULT in

RIOT/cpu/samd21/include/cpu-conf.h - I’ve got it to work by increasing it to

1536, but you might have to play around a little. 



Cheers,

Lucas



On 28 Mar 2015, at 14:22, Abdulkhadar Abdulla <khadar4u at hotmail.com> wrote:



> Hi All,

> 

> Recently I started using RIOT on my sam r21 xplained board. When I tried to ping between two boards running the sixlowapp application, the application hangs and I need to reset the board to continue working. Can anybody help me to understand it is so? 

> 

> The log below is taken after enabling debug in ip.c, icmp.c, sixlowshell.c, monitor.c, helper.c, lowpan.c

> 

> 

> Node 1 (source from ping initiated)

> -----------

> 

> 2015-03-28 18:46:17,399 - INFO # ifconfig

> 2015-03-28 18:46:17,400 - INFO # 

> 2015-03-28 18:46:17,408 - INFO # Iface   0   HWaddr: 0xa0b9 Channel: 11 PAN ID: 0x0001

> 2015-03-28 18:46:17,412 - INFO #             EUI-64: 5a-56-03-7a-18-64-e1-f1

> 2015-03-28 18:46:17,415 - INFO #             Source address mode: short

> 2015-03-28 18:46:17,417 - INFO #             Transceivers:

> 2015-03-28 18:46:17,419 - INFO #              * at86rf231

> 2015-03-28 18:46:17,426 - INFO #             inet6 addr: fe80::ff:fe00:a0b9/128  scope: local

> 2015-03-28 18:46:17,434 - INFO #             inet6 addr: ff02::1:ff00:a0b9/128  scope: local [multicast]

> 2015-03-28 18:46:17,441 - INFO #             inet6 addr: ff02::1/128  scope: local [multicast]

> 2015-03-28 18:46:17,446 - INFO #             inet6 addr: ::1/128  scope: global

> 2015-03-28 18:46:17,454 - INFO #             inet6 addr: ff02::1:ff00:1/128  scope: local [multicast]

> 2015-03-28 18:46:17,454 - INFO # 

> ping fe80::ff:fe00:a545

> 2015-03-28 18:46:35,255 - INFO # > ping fe80::ff:fe00:a545

> 2015-03-28 18:46:35,255 - INFO # 

> 2015-03-28 18:46:35,264 - INFO # INFO: send echo request (id = 0001, seq = 1, data_len = zu) to: u

> 2015-03-28 18:46:35,279 - INFO # DEBUG(main): /home/alcodex/Aerosense/RIOT/sys/net/network_layer/sixlowpan/ip.c:77 in ipv6_send_packet: Got a packet to send to fe80::ff:fe00:a545

> 2015-03-28 18:46:35,284 - INFO # INFO: fe80::ff:fe00:a545 is in nbr cache

> 2015-03-28 18:46:35,289 - INFO # sixlowpan_lowpan_sendto(0, dest, 2, data, 52)

>  

> <No response after the above log. The device needs a rest to continue>

> 

> Node 2 (Target Node for ping)

> ---------

> 2015-03-28 18:46:10,645 - INFO # ifconfig

> 2015-03-28 18:46:10,646 - INFO # 

> 2015-03-28 18:46:10,655 - INFO # Iface   0   HWaddr: 0xa545 Channel: 11 PAN ID: 0x0001

> 2015-03-28 18:46:10,658 - INFO #             EUI-64: 57-44-39-8a-2d-7a-e6-f1

> 2015-03-28 18:46:10,661 - INFO #             Source address mode: short

> 2015-03-28 18:46:10,663 - INFO #             Transceivers:

> 2015-03-28 18:46:10,666 - INFO #              * at86rf231

> 2015-03-28 18:46:10,672 - INFO #             inet6 addr: fe80::ff:fe00:a545/128  scope: local

> 2015-03-28 18:46:10,680 - INFO #             inet6 addr: ff02::1:ff00:a545/128  scope: local [multicast]

> 2015-03-28 18:46:10,687 - INFO #             inet6 addr: ff02::1/128  scope: local [multicast]

> 2015-03-28 18:46:10,692 - INFO #             inet6 addr: ::1/128  scope: global

> 2015-03-28 18:46:10,700 - INFO #             inet6 addr: ff02::1:ff00:1/128  scope: local [multicast]

> 

> 

> Thanks

> Abdul

> _______________________________________________

> users mailing list

> users at riot-os.org

> http://lists.riot-os.org/mailman/listinfo/users



_______________________________________________

users mailing list

users at riot-os.org

http://lists.riot-os.org/mailman/listinfo/users





_______________________________________________ users mailing list 
users at riot-os.org http://lists.riot-os.org/mailman/listinfo/users



_______________________________________________

users mailing list

users at riot-os.org

http://lists.riot-os.org/mailman/listinfo/users








_______________________________________________
users mailing list
users at riot-os.org
http://lists.riot-os.org/mailman/listinfo/users

_______________________________________________
users mailing list
users at riot-os.org
http://lists.riot-os.org/mailman/listinfo/users 		 	   		  

_______________________________________________
users mailing list
users at riot-os.org
http://lists.riot-os.org/mailman/listinfo/users 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/users/attachments/20150407/8c202c90/attachment.html>


More information about the users mailing list