Setting up IPv6 over BLE using nRF52 Series and RIOT OS

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

mboungou — Tue, 28 Nov 2017 11:35:05 GMT

Robert H. Where is this file "Makefile.include.cortexm_common"? In the RIOT directory?

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Jeff B — Wed, 28 Sep 2016 21:55:04 GMT

I found part of the reason why a "nrfjprog --family NRF52 --recover" is needed when switching from helloworld example to microcoap_server one:

microcoap_server needs softdevice.hex to be flashed before. Softdevice.hex is checking the content of address 0x2000: if 0xFFFFFFFF is present, then it jumps to the application(microcoap_server in our case). If different, it will stay in an infinite loop at 0x438.

Once helloworld example is flashed, the value at 0x2000 is different than 0xFFFFFFFF. The flashing procedure of microcoap_server is not ensuring that the content at this address is erased. Doing the "nrfjprog --family NRF52 --recover" ensure the value at this address is reset to 0xFFFFFFFF.

I don't know why softdevice.hex is checking this, not sure if anyone knows here.

Also, I think the microcoap_server flashing should be fixed to ensure this is done. I can do it manually but I have not found a good way of doing it cleanly yet using the JLINK_PRE_FLASH variable for instance: I need to add an erase in the burn.seg file before doing the loadfile for the softdevice.hex.

Anyone having a suggestion ?

Thanks.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Sun, 04 Sep 2016 15:30:07 GMT

What might be wrong if after following all the steps I am not able to ping routable address but device responses to local link address pings?

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Robert H. — Fri, 26 Aug 2016 17:46:29 GMT

I have spent some time debugging this and trying to get it work. The issue was in the build process. In the current RIOT-OS Top of Tree, the variable "LINKER_SCRIPT" is not being used. Here's the git diff that will allow you to get the example to function:

diff --git a/cpu/Makefile.include.cortexm_common b/cpu/Makefile.include.cortexm_common
index 74b2327..be16d02 100644
--- a/cpu/Makefile.include.cortexm_common
+++ b/cpu/Makefile.include.cortexm_common
@@ -16,7 +16,12 @@ export CFLAGS += $(CFLAGS_CPU) $(CFLAGS_LINK) $(CFLAGS_DBG) $(CFLAGS_OPT)
 
 export ASFLAGS += $(CFLAGS_CPU) $(CFLAGS_DBG)
 export LINKFLAGS += -L$(RIOTCPU)/$(CPU)/ldscripts -L$(RIOTCPU)/cortexm_common/ldscripts
-export LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ldscripts/$(CPU_MODEL).ld -Wl,--fatal-warnings
+ifneq (,$(LINKER_SCRIPT))
+export LINKFLAGS += -T$(LINKER_SCRIPT)
+else
+export LINKFLAGS += -T$(RIOTCPU)/$(CPU)/ldscripts/$(CPU_MODEL).ld 
+endif
+export LINKFLAGS += -Wl,--fatal-warnings
 export LINKFLAGS += $(CFLAGS_CPU) $(CFLAGS_DBG) $(CFLAGS_OPT) -static -lgcc -nostartfiles
 export LINKFLAGS += -Wl,--gc-sections

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Collin Mast — Mon, 01 Aug 2016 23:07:19 GMT

I'm having a similar issue. The hello world example worked fine, but when I flash the microap_server example, it fails to print anything to terminal 1. If I use JLinkExe to halt execution and try to single step, I get J-Link>s 0000041C: FE E7 B #-0x04. Using the single step command again will provide the same output. It seems like it may be a hardfault.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Thu, 21 Jul 2016 14:13:06 GMT

I did like you said and I get the following error:

arm-none-eabi-gcc: error: /home/mkru/tmp/test/RIOT/examples/hello-world/bin/nrf52dk/nordic_ble_softdevice.a: No such file or directory

What is funny I do not get this error when compiling microcoap_server example. What I have realized is that there is no USEMODULE += nordic_ble_softdevice in Makefile for microcoap_server example.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

kaspar — Wed, 20 Jul 2016 14:06:21 GMT

@albundy hmm. I'm nearly out of ideas.

You could try one more thing:

add USEMODULE += nordic_ble_softdevice to the makefile in examples/hello-world
nrfjprog --family NRF52 --recover
run BOARD=nrf52dk PORT=/dev/ttyACM0 make term
try the hello-world example again: BOARD=nrf52dk PORT=/dev/ttyACM0 make clean all flash

That would compile hello-world, but include the SoftDevice.

If that still doesn't work, please open a ticket at github.com/.../RIOT.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Tue, 19 Jul 2016 10:22:51 GMT

Ok here is what I have done and results:

Opened terminal #1, executed BOARD=nrf52dk PORT=/dev/ttyACM0 make term. The term has opened successfully.
Opened terminal #2 executedd BOARD=nrf52dk PORT=/dev/ttyACM0 make clean all flash in hello-world example. After that, expected output has appeared on term in terminal #1

2016-07-19 12:13:44,460 - INFO # main(): This is RIOT! (Version: 2016.07-devel-451-g29fd3-K53SV) 2016-07-19 12:13:44,464 - INFO # Hello World! 2016-07-19 12:13:44,466 - INFO # You are running RIOT on a(n) nrf52dk board. 2016-07-19 12:13:44,469 - INFO # This board features a(n) nrf52 MCU.
Run nrfjprog --family NRF52 --recover with success.
Changed directory to microcoap_server run command BOARD=nrf52dk PORT=/dev/ttyACM0 make clean all flash -j4. Unfortunately nothing has appeared on term in terminal #1.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

kaspar — Tue, 19 Jul 2016 09:49:05 GMT

@albundy Hmm.

It is possible that something goes wrong before pyterm has opened the serial port.

Could you try running

BOARD=nrf52dk PORT=/dev/ttyACM0 make term

in one terminal, then, in another terminal, confirm that

BOARD=nrf52dk PORT=/dev/ttyACM0 make clean all flash

(without term) within examples/hello-world does print the hello world output, then run again the nrfjprog recover, then flash again the microcoap_server application?

Hint: you can add, e.g., "-j4" to the make commands to speed up compilation on multi-core machines.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Tue, 19 Jul 2016 09:42:57 GMT

I have executed ./nrfjprog --family NRF52 --recover command with success. Then I have run BOARD=nrf52dk PORT=/dev/ttyACM0 make clean all flash term -j4 in microcoap_server directory but these did not change anything. The only thing I still get in pyterm is:

2016-07-19 10:14:31,760 - INFO # Connect to serial port /dev/ttyACM0 

Welcome to pyterm! 

Type '/exit' to exit.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

kaspar — Mon, 18 Jul 2016 16:41:51 GMT

What kind of dongle did you use?

I'm using the cheapest BLE dongle I could find on ebay (<3€). I'm afraid I can't help with your PCA10031 dongle. Are it's modules loaded?

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

kaspar — Mon, 18 Jul 2016 16:39:48 GMT

@Albundy: could you try using

nrfjprog --recover

and then re-flash? nrfjprog is available in the nordic downloads. AFAIR it needs another parameter for the nrf52.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Mon, 18 Jul 2016 09:06:22 GMT

OK, I have tried with current master but I have some problems. (hello-world example works)

After compilation examples/microcoap_server I get only

Welcome to pyterm!

Type '/exit' to exit.

There are no other messages like:

2016-07-12 20:12:49,151 - INFO # Long HWaddr: 02:4c:86:ff:fe:12:d1:0f

You have written:

Now open another terminal in order to set up the bluetooth connection.

Then make sure your bluetooth dongle has been recognized:

What kind of dongle did you use? Do you have built-in BLE transceiver in your notebook/computer or did you use external dongle? I have dongle PCA10031 but I do not know how to configure it to make it visible in hciconfig. hciconfig sees only my old Bluetooth built-in transceiver which is not compatible with BLE 4.2.

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

Al Bundy — Mon, 18 Jul 2016 08:05:16 GMT

Linux Mint 17.3 but I have already solved the compilation issue. The secret lays here: sys/newlib/Makefile.include:50: NEWLIB_INCLUDE_DIR := $(abspath $(wildcard $(dir $(shell which $(PREFIX)gcc))../$(TARGET_ARCH)/include)). The author of the Makefile did not take into account that people may have symbolic links to toolchain programs.

By the way, have you ever tried to implement more complicated application using RIOT OS on nRF52? I would like to port my software to that system but I have no idea how it would work with softdevice?

RE: Setting up IPv6 over BLE using nRF52 Series and RIOT OS

kaspar — Sun, 17 Jul 2016 21:52:31 GMT

@AlBundy, what host OS / distribution are you using? The hello-world example doesn't use the SoftDevice. Could you try again with current master?