Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Struggling to get iot tftp example working

Hi,

I'm trying to get the tftp example working from the sdk iot examples. When I try it out following these instructions (http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/iot_sdk_app_tftp.html and others linked) I get the following error from the dev kit:

"<info> app: New interface added!
<info> app: Sending Router Solicitation to all routers!
<info> app: Read button has been pushed.
<info> app: In TFTP Application Handler.
<info> app: TFTP error = 0x0000C84A

. Transfered 0 bytes."

I have a NRF52-DK(pca10040) and have downloaded nRF5_SDK_15.0.0_a53641a\examples\iot\tftp\client\hex\iot_ipv6_tftp_pca10040_s132.hex via windows explorer into the dev kit.

On my rpi2b (Raspbian stretch- latest noobs install and updated) it looks like it is already 6LoWPAN support so I have not rebuilt the kernel, but have installed and configured radvd. hciconfig, lescan and ifconfig look good.

root@alpha:/home/pi# hciconfig
hci0: Type: Primary Bus: USB
BD Address: 00:02:72:C9:62:B2 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:6394 acl:157 sco:0 events:311 errors:0
TX bytes:13285 acl:286 sco:0 commands:140 errors:0

root@alpha:/home/pi# hcitool lescan
LE Scan ...
00:39:2F:16:4F:E9 IPv6TFTP
00:39:2F:16:4F:E9 (unknown)

root@alpha:/home/pi# ifconfig
bt0: flags=4161<UP,RUNNING,MULTICAST> mtu 1280
inet6 fe80::2:72ff:fec9:62b2 prefixlen 64 scopeid 0x20<link>
unspec 00-02-72-C9-62-B2-38-E1-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 1 bytes 28 (28.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1 bytes 60 (60.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

The command "root@alpha:/home/pi# echo "connect 00:39:2F:16:4F:E9 1" > /sys/kernel/debug/bluetooth/6lowpan_control" returns nothing but dev kit reports in a connected state with LEDs and output per above.

I'm unable to ping with "ping6 -I bt0 fe80::239:2FFF:FE16:4FE9"

Hci tool con output seems good.

"root@alpha:/home/pi# hcitool con
Connections:
< LE 00:39:2F:16:4F:E9 handle 64 state 1 lm MASTER"

Because I was going through all documentation and trying stuff that looked applicable I tried assigning the static ip address and then pinging with no results.

"root@alpha:/home/pi# ifconfig bt0 add 2001:db8::1/64
root@alpha:/home/pi# ping6 -I bt0 fe80::239:2FFF:FE16:4FE9
PING fe80::239:2FFF:FE16:4FE9(fe80::239:2fff:fe16:4fe9) from fe80::2:72ff:fec9:62b2%bt0 bt0: 56 data bytes
From fe80::2:72ff:fec9:62b2%bt0 icmp_seq=1 Destination unreachable: Address unreachable
From fe80::2:72ff:fec9:62b2%bt0 icmp_seq=5 Destination unreachable: Address unreachable
From fe80::2:72ff:fec9:62b2%bt0 icmp_seq=6 Destination unreachable: Address unreachable
"

I don't know how to check "# Observe if new IPv6 prefix is disseminating over bt0 interface." per http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/iot_ug_border_router.html

Any ideas on what could be wrong, or further steps I can take to diagnose the problem?

Cheers,
Daniel

Parents Reply Children
Related