icmp in nrf51 iot sdk can not run continuously

RE: icmp in nrf51 iot sdk can not run continuously

nk — Wed, 26 Oct 2016 13:14:13 GMT

I tried another way. I tried to use old kernel. about reason, please to refer link text I used raspberry pi2 + USB dongle and 2015-05-05-raspbian-wheezy. The same problem was happend.

RE: icmp in nrf51 iot sdk can not run continuously

Krishna Shingala — Mon, 24 Oct 2016 11:35:15 GMT

I would monitor the traffic on the bt interface if possible and confirm if the packets are actually sent on the bt interface or not. There have been observations that too much traffic result in a reset of the controller on the BlueZ. And this is not related to any specific vendor.

RE: icmp in nrf51 iot sdk can not run continuously

nk — Fri, 21 Oct 2016 07:51:14 GMT

I would suspect the wifi/bt chipset. If you google the error you get back and add "bcm", you can see that most threads point to an issue with the bcm drivers in the kernel.

I tried to put in USB dongle of CSR chip on RasPi. the result was same. the amount of bytes was little different.

RE: icmp in nrf51 iot sdk can not run continuously

nk — Fri, 21 Oct 2016 00:32:02 GMT

I tried to update bluez from 5.23 to 5.39. but the result was same.

RE: icmp in nrf51 iot sdk can not run continuously

nk — Fri, 21 Oct 2016 00:30:44 GMT

To test this theory, you can ping any other ipv6 address with the same amount of bytes and see if it stops after 120 iterations.

Yes. I tried it by using some nrf51 module(IPSP Node). these result were same. And when sending the same byte size, the error is happened.

RE: icmp in nrf51 iot sdk can not run continuously

Håkon Alseth — Thu, 20 Oct 2016 10:14:15 GMT

I would suspect the wifi/bt chipset. If you google the error you get back and add "bcm", you can see that most threads point to an issue with the bcm drivers in the kernel.

To test this theory, you can ping any other ipv6 address with the same amount of bytes and see if it stops after 120 iterations.

Cheers, Håkon