IPv4 issues with the 6lowpan br-webserver-node using samd21

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have successfully built the Smart Connect 6LoWPAN - Border Router Webserver  AT86RF212B - SAM D21 Xplained Pro demo application.  The application successfully runs on the target but does not get a IPv4 IP address on the ethernet port.  I have configured the target hardware as per the user guide and am using ASF 3.35.1.

I have used a different demo application to confirm that the target is connected to the local network using a static IP.

The terminal log reports that the DHCPv4 request has been made but with no response.

 

Starting DHCPv4
Inited
Requested

Ctimer timer callback for dag root
 No root available, we'll make ourself as root
simple_rpl_init_dag: created a new RPL dag

 

If I rebuild the 6LoWPAN demo with a static IP by setting DISABLE_DHCP the target assigns itself the appropriate IP but I am still unable to ping it.

Has anyone else experienced this issue and if not please can you give me tips on how to debug the target.

Can I build a shell into contiki and access these settings dynamically, possibly pinging out from the target or query what the targets run-time configuration is?

Thanks in advance.

 

 

 

Last Edited: Fri. Nov 24, 2017 - 01:27 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi mwelsford,

 

I have exactly the same issue as you. Have you found any solution? Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Problem solved. Use old versions of examples (ASF 3.31.0 or earlier), and it's better to use old versions of browsers for Atmel Server (HTML).

Last Edited: Thu. Jul 26, 2018 - 07:34 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

w52918 wrote:
Problem solved.

Jolly good. Now please mark the solution - see Tip #5

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...