[riot-users] Ping from tap interface of one RIOT instance to another dont work.

Rikhu Prasad rikhuprasad at gmail.com
Sun Jan 10 17:11:42 CET 2016


I did try to update avrdude to the latest version (thinking maybe the image
created by the older version was not fully compatible) - available at
http://download.savannah.gnu.org/releases/avrdude/

Now I am using Ubuntu 14.04. I get the below error while flashing. avrdude
version 6.2.

System wide configuration file is "/usr/local/etc/avrdude.conf"
         User configuration file is "/home/rikhu/.avrduderc"
         User configuration file does not exist or is not a regular file,
skipping

         Using Port                    : /dev/ttyACM0
         Using Programmer              : stk500v2
         Overriding Baud Rate          : 115200
make: *** [flash] Floating point exception (core dumped)

Anyone faced these issues, please.

Regards,
Rikhu

On Sat, Jan 9, 2016 at 1:57 AM, Rikhu Prasad <rikhuprasad at gmail.com> wrote:

> Hi ,
>
> Thank you. It works finally, I tried the below for the Mega 2560 by
> checking what the IDE does actually and and following accordingly. So, the
> below works for me without updating the avrdude. I am using avrdude 6.1
> version.
>
> avrdude -v -patmega2560 -cwiring -P/dev/ttyACM0 -b115200 -D
> -Uflash:w:bin/arduino-mega2560/default.hex
>
> Now the issue is that I am not able to use ifconfig (networking) does not
> work. When I do a help command, it only shows as below... Does not have
> support for ifconfig. Your opinions would give me further insights.
>
> 2016-01-09 01:51:54,238 - INFO # Welcome to RIOT!
> 2016-01-09 01:51:54,238 - INFO # > >
>
> 2016-01-09 01:51:54,239 - INFO # main(): This is RIOT!
> 2016-01-09 01:51:54,250 - INFO # Welcome to RIOT!
> help
> 2016-01-09 01:51:56,408 - INFO # > help
> 2016-01-09 01:51:56,445 - INFO # Command              Description
> 2016-01-09 01:51:56,486 - INFO # ---------------------------------------
> 2016-01-09 01:51:56,523 - INFO # reboot               Reboot the node
> 2016-01-09 01:51:56,593 - INFO # ps                   Prints information
> about running threads.
>
>
> Regards,
> Rikhu
>
>
> On Thu, Jan 7, 2016 at 1:39 PM, Hauke Petersen <
> hauke.petersen at fu-berlin.de> wrote:
>
>> Hej!
>>
>> I think I had a similar problem once when trying to flash the
>> arduino-mega2560. If I recall correctly, I think I fixed this by updating
>> my avrdude tool to a new version (build it from their master). My current
>> version is 6.2-20151117 which works fine under Linux Mint 17. Maybe you
>> give that a try?
>>
>> Cheers,
>> Hauke
>>
>>
>>
>> On 07.01.2016 13:32, Rikhu Prasad wrote:
>>
>> Hi Cenk,
>>
>> Thank you for your response. Its very strange that its not working. I
>> tried to use another piece of Arduino Mega 2560, and it gives the same
>> error. I am trying to flash using the default USB connector.
>>
>> Just to make further clear, I tried flashing it in "Arduino MEGA ADK for
>> Android" [Link: https://www.arduino.cc/en/Main/ArduinoBoardMegaADK ]
>> using default USB connector. Its extremely strange that the flashing works
>> for this!!! It may be because The MEGA ADK is based on the Mega 2560. But,
>> how can it be that flashing works for this and does not work in the Mega
>> 2560 (which its mentioned specifically in the RIOT that it supports for
>> this device). One problem with ArduinoBoardMegaADK is that I do not get
>> networking support - after flashing I cannot use ifconfig for the device.
>> Probably it should be that networking is its not supported for
>> ArduinoBoardMegaADK.
>>
>> But my main concern/problem I am facing is why flasehing does not work in
>> Mega 2560 in 2 devices when trying to flash from USB. Both give same
>> errors.
>>
>> Regards,
>> Rikhu
>>
>> On Tue, Jan 5, 2016 at 5:46 PM, Cenk G√ľndogan <
>> cenk.guendogan at fu-berlin.de> wrote:
>>
>>> Hello Rikhu,
>>>
>>> Sorry for the late response.
>>> I just tried to flash the default example (master) on an arduino mega
>>> 2560 board
>>> and it works without any errors. Does your problem still persist?
>>> Admittedly, I have not much knowledge in this area. Maybe Hauke or
>>> someone else
>>> can give more hints regarding this problem?
>>>
>>> Best,
>>> Cenk
>>>
>>>
>>> On 29.12.2015 15:33, Rikhu Prasad wrote:
>>>
>>> *Hi Cenk,*
>>>
>>> *I am trying to use the example provided for Arduino Mega 2560, and I
>>> believe it should work for this board too. But I receive the below error. *
>>>
>>> *When I reset the board before uploading, I get timeout errors (listed
>>> below). The same issue happens with the default example provided in RIOT.
>>> When I upload the Receive and/or Transmit lights on the Arduino blink. *
>>>
>>> *To test if Arduino is working : I tested with Blink sketch using
>>> Arduino IDE and it works fine. I even tried without the IDE using
>>> Arduino-Makefile (https://github.com/sudar/Arduino-Makefile
>>> <https://github.com/sudar/Arduino-Makefile>) to reassure myself and it
>>> works. The problem happens with using RIOT. *
>>>
>>> *Without RESET:*
>>> *avrdude -p m2560 -c stk500v2 -P /dev/ttyACM0 -b 115200 -F -U
>>> flash:w:bin/arduino-mega2560/default.hex*
>>>
>>> *avrdude: AVR device initialized and ready to accept instructions*
>>>
>>> *Reading | ################################################## | 100%
>>> 0.01s*
>>>
>>> *avrdude: Device signature = 0x1e9801*
>>> *avrdude: NOTE: "flash" memory has been specified, an erase cycle will
>>> be performed*
>>> *         To disable this feature, specify the -D option.*
>>> *avrdude: erasing chip*
>>> *avrdude: stk500v2_command(): command failed*
>>>
>>> *avrdude done.  Thank you.*
>>>
>>> *make: *** [flash] Error 255*
>>>
>>>
>>> *After Reset:*
>>> *"make" -C /home/rikhu/Desktop/RIOT/sys/xtimer*
>>> *   text   data    bss    dec    hex filename*
>>> *  48670   5326  11189  65185   fea1
>>> /home/rikhu/Desktop/RIOT-Tutorial/application/bin/arduino-mega2560/ieee_wf-iot_2015.elf*
>>> *avrdude -p m2560 -c stk500v2 -P /dev/ttyACM0 -b 115200 -F -U
>>> flash:w:bin/arduino-mega2560/ieee_wf-iot_2015.hex*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_getsync(): timeout communicating with programmer*
>>>
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>> *avrdude: stk500v2_ReceiveMessage(): timeout*
>>>
>>>
>>>
>>>
>>> Thanks,
>>> Rikhu
>>>
>>> On Tue, Dec 22, 2015 at 9:45 PM, Cenk G√ľndogan <
>>> <cenk.guendogan at fu-berlin.de>cenk.guendogan at fu-berlin.de> wrote:
>>>
>>>> Hello Rikhu,
>>>>
>>>> Can you try creating the tap interfaces with the tapsetup script
>>>> located in RIOT/dist/tools/tapsetup/tapsetup ?
>>>>
>>>> This tapsetup script will create an interface (br0) that serves as a
>>>> bridge
>>>> between tap0 and tap1 (and other taps created by the tapsetup script).
>>>>
>>>> Thank you for pointing out this issue, I will address this in the
>>>> tutorial.
>>>>
>>>> Best,
>>>> Cenk
>>>>
>>>>
>>>> On 22.12.2015 21:39, Rikhu Prasad wrote:
>>>>
>>>> Hi,
>>>>
>>>> I followed the following tutorial to get used to developing application
>>>> in RIOT.
>>>>
>>>> https://github.com/cgundogan/RIOT-Tutorial/
>>>>
>>>> As per the below, I have configured one instance of RIOT to tap0 and
>>>> another instance to tap1. and try to ping between 2 instances and this does
>>>> not work. Am I missing something? Please advice.
>>>>
>>>> 1. Running RIOT on Native -> 8th point..
>>>>
>>>> *RIOT  (Instance 1):*
>>>>
>>>> ifconfig
>>>> Iface  4   HWaddr: 22:a4:56:14:8a:61
>>>>            MTU:1280  HL:64
>>>>            Source address length: 6
>>>>            Link type: wired
>>>>            inet6 addr: ff02::1/128  scope: local [multicast]
>>>>            inet6 addr: fe80::20a4:56ff:fe14:8a61/64  scope: local
>>>>            inet6 addr: ff02::1:ff14:8a61/128  scope: local [multicast]
>>>>            inet6 addr: ff02::2/128  scope: local [multicast]
>>>>
>>>> *RIOT (Instance 2) : *
>>>>
>>>> ifconfig
>>>> Iface  4   HWaddr: ca:ec:7d:fd:db:d0
>>>>            MTU:1280  HL:64
>>>>            Source address length: 6
>>>>            Link type: wired
>>>>            inet6 addr: ff02::1/128  scope: local [multicast]
>>>>            inet6 addr: fe80::c8ec:7dff:fefd:dbd0/64  scope: local
>>>>            inet6 addr: ff02::1:fffd:dbd0/128  scope: local [multicast]
>>>>            inet6 addr: ff02::2/128  scope: local [multicast]
>>>>
>>>> *I try to ping RIOT1 from RIOT2 : *
>>>>
>>>> ping6 fe80::20a4:56ff:fe14:8a61
>>>> ping timeout
>>>> ping timeout
>>>> ping timeout
>>>> --- fe80::20a4:56ff:fe14:8a61 ping statistics ---
>>>> 3 packets transmitted, 0 received, 100% packet loss
>>>>
>>>> I try to ping RIOT instance 1 from instance 2 and dont work. I tried
>>>> various other means like mentioning tap interface in ping command, still,
>>>> don't work.
>>>>
>>>>
>>>>
>>>> -Rik
>>>>
>>>>
>>>> _______________________________________________
>>>> users mailing listusers at riot-os.orghttps://lists.riot-os.org/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users at riot-os.org
>>>> https://lists.riot-os.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> users mailing listusers at riot-os.orghttps://lists.riot-os.org/mailman/listinfo/users
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users at riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/users/attachments/20160110/b1b89302/attachment-0001.html>


More information about the users mailing list