Re: [riot-devel] Bringup procedure of a real device
Hello malo, I love you! That was the missing link - I had totally forgotten the hardware address (MAC). Everything seem now to work well - I have tested ping6 and udp - what a wonderful world! Thanks, thanks, thanks! Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Bringup procedure of a real device
Hello Malo, thank you for this hint. What else has to be changed in an IPv6 network? Up to now I have only worked with IPv4 under Linux and there the only thing which was necessary to change was the IP-address Thanks a lot, Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Bringup procedure of a real device
Hello Bernhard, Did you change L2(HWaddr) address on one board? since you are mentioning only IP address change. Check for AT86RF2XX_DEFAULT_ADDR_LONG. To see the 802.15.4. traffic in the air you would need some kind of 802.15.4 sniffer... wbr malo On 6 March 2016 at 20:31, Bernhard Nägele wrote: > Sorry, > I have forgotten to post the forked theads: > > ps > pid | name | stateQ | pri | stack ( used) | > location > 1 | idle | pending Q | 15 | 256 ( 148) | > 0x2298 > 2 | main | running Q | 7 | 1536 ( 792) | > 0x2398 > 3 | pktdump | bl rx_ | 6 | 1536 ( 256) | > 0x20001924 > 4 | 6lo | bl rx_ | 3 | 1024 ( 468) | > 0x20001f38 > 5 | ipv6 | bl rx_ | 4 | 1024 ( 420) | > 0x2e60 > 6 | udp | bl rx_ | 5 | 1024 ( 296) | > 0x200026e4 > 7 | at86rfxx | bl rx_ | 3 | 1024 ( 412) | > 0x29f0 > | SUM || | 7424 ( 2792) > > > > Thanks for any hint! > > Best regards, > > Bernhard > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Bringup procedure of a real device
Sorry, I have forgotten to post the forked theads: ps pid | name | stateQ | pri | stack ( used) | location 1 | idle | pending Q | 15 | 256 ( 148) | 0x2298 2 | main | running Q | 7 | 1536 ( 792) | 0x2398 3 | pktdump | bl rx_ | 6 | 1536 ( 256) | 0x20001924 4 | 6lo | bl rx_ | 3 | 1024 ( 468) | 0x20001f38 5 | ipv6 | bl rx_ | 4 | 1024 ( 420) | 0x2e60 6 | udp | bl rx_ | 5 | 1024 ( 296) | 0x200026e4 7 | at86rfxx | bl rx_ | 3 | 1024 ( 412) | 0x29f0 | SUM || | 7424 ( 2792) > Thanks for any hint! Best regards, Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Bringup procedure of a real device
Hello everybody, I try to bring up a wireless connection between two identical boards, both equiped with the at86rf233 module. At first everything seems to be good - the source was compiled without failure, the process list shows all the threads needed for a working interface, but when I try to get a contact from one board to the other nothing happens. Is there anyone who can give some hints about the best way to bring up a wireless connection with RIOT? Here is what I have done: First I flash the gnrc_networking example on both boards. The command showed exactly the same on both boards: > ifconfig Iface 7 HWaddr: 30:02 Channel: 26 Page: 0 NID: 0x23 Long HWaddr: 88:77:66:55:44:33:22:12 TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4 AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC Source address length: 8 Link type: wireless inet6 addr: ff02::1/128 scope: local [multicast] inet6 addr: fe80::8a77:6655:4433:2212/64 scope: local inet6 addr: ff02::1:ff33:2212/128 scope: local [multicast] so far so good. Then I altered the ip-addresses on one board to: > ifconfig Iface 7 HWaddr: 30:02 Channel: 26 Page: 0 NID: 0x23 Long HWaddr: 88:77:66:55:44:33:22:12 TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4 AUTOACK CSMA MTU:1280 HL:64 6LO RTR IPHC Source address length: 8 Link type: wireless inet6 addr: ff02::1/128 scope: local [multicast] inet6 addr: fe80::8a77:6655:4433:2214/64 scope: local inet6 addr: ff02::1:ff33:2214/128 scope: local [multicast] then I tried to ping from one board to the other: > ping6 fe80::8a77:6655:4433:2214 result: no output - the shell output stucks and I have to reboot A ping to the own address delivers this output, but then the shell stucks again: > ping6 fe80::8a77:6655:4433:2212 12 bytes from fe80::8a77:6655:4433:2212: id=83 seq=1 hop limit=64 time = 4.892 ms Is this the normal behaviour of RIOT that the command don't come back to the shell? When the board stucks and I stop it with the debugger it seems the it cycles through the Idle-State. Can anyone give me some hints what I'm doing wrong? How could it be found out that there is some traffic in the air? Thanks a lot and best regards, Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
