• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 41 subscribers
  • Views 270 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220: IP4 loss in cloud_ota

david s
Genius 3005 points
Part Number: CC3220


Hi,

My applications is based on cloud_ota. The device successfully connects to the network and acquires IP but then all of a sudden the device loses IP:

IPv4 lost Id or timeout, Id [0x8]!!!

It then self-restarts twice and eventually acquires the same IP as it had initially.

What can be a reason for IP loss? 

Thanks,

David

  • 0
    Guru 39650 points

    Hi David,

    I am not 100% sure (I will need check it) but I think this is due to expiration IP acquired from the DHCP server.

    Jan

  • 0 in reply to Hnz
    Genius 3005 points
    Hi Jan,

    Thanks for reply. Is there a way to increase the expiration time?

    Thanks,
    David
  • 0 in reply to david s
    Guru 39650 points
    Hi David,

    You can check settings at your DHCP server/router. DHCP lease time is related to your network infrastructure.

    Previous answer I will be able check tomorrow. I have set lease timeout at my router to one hour. Unfortunately it is late I am not able wait one hour to see result in log.

    Jan
  • 0 in reply to Hnz
    Genius 3005 points
    Hi Jan,

    Oh, you mean DHCP lease time. I think code [0x8] indicates IP loss. In my setup it looks like DHCP timeout would be code 9.

    Let me know if I am wrong.

    Thanks,
    David
  • 0 in reply to david s
    Guru 39650 points
    Hi David,

    I have done my tests. I am pretty sure that your event is called due to IP lease time expiration.

    In case of IP lease lime expiration you should see SL_NETAPP_EVENT_IPV4_LOST with status 0x00 (pNetAppEvent->Data.IpV4Lost.Status).

    Event SL_NETAPP_EVENT_DHCP_IPV4_ACQUIRE_TIMEOUT is for acquiring IP from DHCP server as is evident from his name. From SWRU455E: "Acquiring the IPv4 address by DHCP is too long and not completed yet, acquiring by DHCP still continues."

    Jan
  • 0 in reply to Hnz
    Genius 3005 points
    Thanks, Jan. I will make sure to add (pNetAppEvent->Data.IpV4Lost.Status) to UART printout and check the status.

    David