Connecting the nRF9160DK to the nRF52833 over Bluetooth

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Thu, 13 Aug 2020 17:00:19 GMT

Hey Øyvind,

That worked!!!!!! Excellent, thank you. So, when I press button 1 on the nRF52833 I send "hello" to the nRF9160DK.

I recompliled this targeting the nRF52840 Dongle and this also worked! Unfortunately, I am still unable to see any output from the dongle but when I press the button on the dongle I see "hello" on the nRF9160DK.

Thanks again for your support,

Regards,
Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Thu, 13 Aug 2020 13:49:40 GMT

Hi Rod,

Here's an update from my part. I was able to get the HIDS examples to run.

From lte_ble_gateway copy the overlay file to the central_hids folder.

In central_hids/prj.conf add the following lines:

CONFIG_BT_H4=y

CONFIG_BT_WAIT_NOP=y

CONFIG_MAIN_STACK_SIZE=8192

Compile for nRF9160dk_nrf9160ns and program the central_hids to nRF9160DK.

Compile for nRF9160dk_nrf52840 and program the hci_uart to nRF9160Dk (remember to switch 5 on the board to nRF52)

And on the nRF52833DK program the peripheral_hids_keyboard sample.

Let me know how it works for you

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Wed, 12 Aug 2020 15:42:36 GMT

Hi Øyvind,

Thanks for your feedback and support, much appreciated. I have hooked up the dongle to and external debugger and UART but am not getting any Printf() output, I have opened a separate ticket.,

https://devzone.nordicsemi.com/f/nordic-q-a/64627/no-uart-output-from-printf

Once I have this working, I can try the code you mentioned

Thanks,
Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Wed, 12 Aug 2020 13:49:44 GMT

Hi Rod,

Sorry for the lack of answers, it's just been a busy week.

I've tested with nRF52840DK and nRF52833DK, running respectively Central HIDS and Peripheral HIDS Keyboard. Those work perfectly together. However, I have not been successful in running the Central HIDS on the nRF9160DK. Will keep testing and get back to you.

There has been an ongoing discussion regarding BLE and NCS in this Git thread, please read through this as well.

[quote user="RodWatt"]I have also bought an NRF52840 dongle which seems to be a good fit for me.[/quote]

Yes, this should work fine, just remember to use nRF52840dongle_nrf52840.

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Thu, 06 Aug 2020 14:03:42 GMT

Hi Øyvind,

That would be great, thank you. (Since we talked, I modified some of the code on the Sensor gateway example so I could get an nRF52833 board to connect over BLE, I didn't get as far as sending data )

I have also bought an NRF52840 dongle which seems to be a good fit for me.

So, ideally I would like to be able to send sensor data from a sensor connected to the nRF52840 board (for example, a simple temperature sensor connected over I2C) back to the nRF9160DK.

Any pointers you could provide would be much appreciated.

Thanks,

Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Thu, 06 Aug 2020 12:19:12 GMT

Hi Rod,

I haven't been able to look much into your case, however, things are starting to normalize in the support department and that will leave more time to help you.

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Thu, 30 Jul 2020 06:44:18 GMT

Hi Øyvind,

I have captured the terminal output below. Its reporting it can't find an LTE Link and them seems to reboot.

As I have just got this working, I have not set up the server side (nfcloud etc) I guess that's what causing the failure? Sorry, when I saw this initially I thought it was not finding a bootable image or similar.

As I'm not interested in writing to the cloud, I just want to get BLE working between the boards, I have commented out the code in main as below

	buttons_leds_init();
	ble_init();

	work_init();
//	cloud_init();
//	modem_configure();
//	cloud_connect(NULL);

	while (true) {
//		nrf_cloud_process();
//		send_aggregated_data();
		k_sleep(K_MSEC(10));
		k_cpu_idle();

This has enabled me to connect the nRF9160Dk to Thing52, I'm seeing this.

SPM: NS image at 0xc000
SPM: NS MSP at 0x2002bae0
SPM: NS reset vector at 0x1245d
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Bluetooth Receiver Demo Started
Initializing Bluetooth..
Bluetooth ready
Scanning...
Device found: e0:54:b8:7a:61:9d (random)
Connected: e0:54:b8:7a:61:9d (random)
Orientation: 2

So, I'm now back to my initial problem of connecting the nRF52833DK to the nRF9160DK

Regards,

Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Wed, 29 Jul 2020 19:36:03 GMT

[quote user="RodWatt"]Ok, that worked, thanks. I was able to build and flash "at_client". [/quote]

That's good news!

[quote user="RodWatt"]When I tried to build "lte_ble_gateway", the code is looping continually. [/quote]

I'm not sure I'm following, the output that you have attached looks good. Can you please elaborate?

Thank you!

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Tue, 28 Jul 2020 15:50:30 GMT

Hi Øyvind,

Ok, that worked, thanks. I was able to build and flash "at_client".

When I tried to build "lte_ble_gateway", the code is looping continually.

Watts-MBP-2:lte_ble_gateway Watt$ pwd
/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway
Watts-MBP-2:lte_ble_gateway Watt$ west build -b nrf9160dk_nrf9160ns
-- west build: generating a build system
Including boilerplate (Zephyr base): /Users/Watt/ncs/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway
-- Zephyr version: 2.3.0-rc1 (/Users/Watt/ncs/zephyr)
-- Found Python3: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 (found suitable exact version "3.8.1") found components: Interpreter 
-- Board: nrf9160dk_nrf9160ns
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/Watt/gcc-arm-none-eabi-8-2019-q3-update)
-- Found BOARD.dts: /Users/Watt/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Found devicetree overlay: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/nrf9160dk_nrf9160ns.overlay
nrf9160dk_nrf9160ns.dts.pre.tmp:394.32-398.5: Warning (simple_bus_reg): /soc/cryptocell-sw: missing or empty reg/ranges property
nrf9160dk_nrf9160ns.dts.pre.tmp:93.42-105.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:202.18-208.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/uart@a000: duplicate unit-address (also used in node /soc/peripheral@40000000/i2c@a000)
  also defined at nrf9160dk_nrf9160ns.dts.pre.tmp:504.8-507.3
  also defined at nrf9160dk_nrf9160ns.dts.pre.tmp:611.8-619.3
nrf9160dk_nrf9160ns.dts.pre.tmp:342.19-348.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
-- Generated zephyr.dts: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/Kconfig
Loaded configuration '/Users/Watt/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig'
Merged configuration '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf'
Configuration saved to '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/.config'
Kconfig header saved to '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 8.3.1
-- The CXX compiler identification is GNU 8.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /Users/Watt/gcc-arm-none-eabi-8-2019-q3-update/bin/arm-none-eabi-gcc
-- Cache files will be written to: /Users/Watt/Library/Caches/zephyr
Changed board to secure nrf9160dk_nrf9160 (NOT NS)

=== child image spm - nrf9160dk_nrf9160 begin ===
Including boilerplate (Zephyr base): /Users/Watt/ncs/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/ncs/nrf/samples/nrf9160/spm
-- Zephyr version: 2.3.0-rc1 (/Users/Watt/ncs/zephyr)
-- Found Python3: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 (found suitable exact version "3.8.1") found components: Interpreter 
-- Board: nrf9160dk_nrf9160
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/Watt/gcc-arm-none-eabi-8-2019-q3-update)
-- Found BOARD.dts: /Users/Watt/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/Watt/ncs/nrf/samples/nrf9160/spm/nrf9160dk_nrf9160.overlay
nrf9160dk_nrf9160.dts.pre.tmp:95.42-107.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@50000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@50000000/kmu@39000)
nrf9160dk_nrf9160.dts.pre.tmp:344.19-350.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@50000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@50000000/power@5000)
-- Generated zephyr.dts: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/spm/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/spm/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/Watt/ncs/zephyr/Kconfig
Loaded configuration '/Users/Watt/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_defconfig'
Merged configuration 'prj.conf'
Merged configuration '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/child_secure_partition_manager.conf'
Configuration saved to '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/spm/zephyr/.config'
Kconfig header saved to '/Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/spm/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 8.3.1
-- The CXX compiler identification is GNU 8.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /Users/Watt/gcc-arm-none-eabi-8-2019-q3-update/bin/arm-none-eabi-gcc
-- Cache files will be written to: /Users/Watt/Library/Caches/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/spm
=== child image spm - nrf9160dk_nrf9160 end ===

CMake Warning at /Users/Watt/ncs/zephyr/CMakeLists.txt:1384 (message):
  __ASSERT() statements are globally ENABLED


Changed board to secure nrf9160dk_nrf9160 (NOT NS)
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build
-- west build: building application
[6/210] Performing build step for 'spm_subimage'
[7/193] Preparing syscall dependency handling

[188/193] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:         32 KB        48 KB     66.67%
            SRAM:        5416 B        64 KB      8.26%
        IDT_LIST:          40 B         2 KB      1.95%
[193/193] Linking C executable zephyr/zephyr.elf
[203/210] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      163848 B       976 KB     16.39%
            SRAM:       58422 B       128 KB     44.57%
        IDT_LIST:         152 B         2 KB      7.42%
[210/210] Generating zephyr/merged_domains.hex
Watts-MBP-2:lte_ble_gateway Watt$ west flash
-- west flash: rebuilding
[0/9] Performing build step for 'spm_subimage'
ninja: no work to do.
-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: /Users/Watt/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/merged.hex
Parsing hex file.
Erasing page at address 0x0.
Erasing page at address 0x1000.
Erasing page at address 0x2000.
Erasing page at address 0x3000.
Erasing page at address 0x4000.
Erasing page at address 0x5000.
Erasing page at address 0x6000.
Erasing page at address 0x7000.
Erasing page at address 0xC000.
Erasing page at address 0xD000.
Erasing page at address 0xE000.
Erasing page at address 0xF000.
Erasing page at address 0x10000.
Erasing page at address 0x11000.
Erasing page at address 0x12000.
Erasing page at address 0x13000.
Erasing page at address 0x14000.
Erasing page at address 0x15000.
Erasing page at address 0x16000.
Erasing page at address 0x17000.
Erasing page at address 0x18000.
Erasing page at address 0x19000.
Erasing page at address 0x1A000.
Erasing page at address 0x1B000.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Erasing page at address 0x1E000.
Erasing page at address 0x1F000.
Erasing page at address 0x20000.
Erasing page at address 0x21000.
Erasing page at address 0x22000.
Erasing page at address 0x23000.
Erasing page at address 0x24000.
Erasing page at address 0x25000.
Erasing page at address 0x26000.
Erasing page at address 0x27000.
Erasing page at address 0x28000.
Erasing page at address 0x29000.
Erasing page at address 0x2A000.
Erasing page at address 0x2B000.
Erasing page at address 0x2C000.
Erasing page at address 0x2D000.
Erasing page at address 0x2E000.
Erasing page at address 0x2F000.
Erasing page at address 0x30000.
Erasing page at address 0x31000.
Erasing page at address 0x32000.
Erasing page at address 0x33000.
Erasing page at address 0x34000.
Applying system reset.
Checking that the area to write is not protected.
Programming device.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960040578 flashed successfully.

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Tue, 28 Jul 2020 13:38:12 GMT

Rod, you must create NCS outside of zephyrproject. (/Users/Watt/NCS/). And you must not run "west init ~/newinstall" and "west update", as this causes confusion and initializes zephyr. NCS includes zephyr inside, and will not be able to initialize if already initialized.

Unless you are using the zephyrproject folder, please delete this along with other folders that you have created.

Then do the following steps:

cd ~

mkdir ncs && cd ncs

west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.3.0

west update

west zephyr-export

pip3 install -r zephyr/scripts/requirements.txt
pip3 install -r nrf/scripts/requirements.txt
pip3 install -r bootloader/mcuboot/scripts/requirements.txt

If this still does not work, please install the Toolchain Manager from the nRF Connect for Desktop.

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Mon, 27 Jul 2020 20:36:10 GMT

I have tried to build another application to see if I can get a clue to what's wrong. (I am managing to build basic stuff such as "blinky" and "button".

I have tried to build "at_client", I can only get this to build when I remove the following lines from the prj.conf file

CONFIG_AT_HOST_LIBRARY=y
CONFIG_LTE_NETWORK_MODE_NBIOT=y
CONFIG_LTE_NETWORK_MODE_LTE_M=n
CONFIG_BSD_LIBRARY=y

Looking at other tickets, most have had success when they recreate a brand new work space. So, I unset the ZEPHYR_BASE variable and carry out the following.

https://raw.githubusercontent.com/Homebrew/install/master/install)"

brew install cmake ninja gperf python3 ccache qemu dtc

pip3 install west
west init ~/newinstall
cd ~/newinstall
west update

west zephyr-export

pip3 install -r ~/newinstall/zephyr/scripts/requirements.txt

pip3 install -U west

Watts-MBP-2:newinstall Watt$ pwd
/Users/Watt/newinstall
Watts-MBP-2:newinstall Watt$ ls
bootloader	modules		tools		zephyr

Watts-MBP-2:newinstall Watt$ mkdir ncs
Watts-MBP-2:ewinstall Watt$ cd ncs

Watts-MBP-2:ncs Watt$ west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.3.0

FATAL ERROR: already initialized in /Users/Watt/newinstall, aborting.

Unfortunately this reports and error, even though this is a new workspace.

Would appreciate your thoughts?

Thanks,

Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Sat, 25 Jul 2020 15:31:26 GMT

I have carried out a clean install, installed NCS version 1.3.0 and have tried to build as below. Still seeing errors.

Watts-MBP-2:lte_ble_gateway Watt$ pwd
/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway
Watts-MBP-2:lte_ble_gateway Watt$ west build -b nrf9160dk_nrf9160ns
-- west build: generating a build system
Including boilerplate (Zephyr base (cached)): /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway
-- Zephyr version: 2.3.0-rc2 (/Users/Watt/zephyrproject/zephyr)
-- Board: nrf9160dk_nrf9160ns
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/Watt/gnuarmemb)
-- Found BOARD.dts: /Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
nrf9160dk_nrf9160ns.dts.pre.tmp:92.42-104.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:341.19-347.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
-- Generated zephyr.dts: /Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/build/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/Watt/zephyrproject/zephyr/Kconfig
Loaded configuration '/Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig'
Merged configuration '/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf'

warning: UART_2_NRF_FLOW_CONTROL (defined at drivers/serial/Kconfig.nrfx:195) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: UART_2_NRF_UARTE (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_UART_2_NRF_FLOW_CONTROL.html and/or
look up UART_2_NRF_FLOW_CONTROL in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:18: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:19: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:22: warning: attempt to assign the value 'y' to the undefined symbol AT_HOST_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:25: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:28: warning: attempt to assign the value 'n' to the undefined symbol BSD_LIBRARY_TRACE_ENABLED

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:31: warning: attempt to assign the value 'y' to the undefined symbol NRF_CLOUD

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:34: warning: attempt to assign the value 'y' to the undefined symbol GPS_USE_SIM

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:37: warning: attempt to assign the value '30' to the undefined symbol GPS_SEARCH_INTERVAL

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:38: warning: attempt to assign the value '15' to the undefined symbol GPS_SEARCH_TIMEOUT

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:45: warning: attempt to assign the value 'y' to the undefined symbol DK_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:46: warning: attempt to assign the value 'n' to the undefined symbol DK_LIBRARY_INVERT_LEDS

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:58: warning: attempt to assign the value 'y' to the undefined symbol BT_GATT_DM

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:59: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:60: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN_FILTER_ENABLE

/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/prj.conf:61: warning: attempt to assign the value '1' to the undefined symbol BT_SCAN_UUID_CNT

error: Aborting due to Kconfig warnings

CMake Error at /Users/Watt/zephyrproject/zephyr/cmake/kconfig.cmake:217 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake:510 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -B/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/build -S/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway -GNinja
Watts-MBP-2:lte_ble_gateway Watt$

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Fri, 24 Jul 2020 16:28:50 GMT

Hi Øyvind,

I deleted everything and started again. I followed this

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_installing.html#setting-up-the-command-line-build-environment

All very straight forward until I try this.

Watts-MBP-2:ncs Watt$ pwd
/Users/Watt/zephyrproject/ncs
Watts-MBP-2:ncs Watt$ west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.3.0
FATAL ERROR: already initialized in /Users/Watt/zephyrproject, aborting.

What am I doing wrong here?

I know this is difficult to debug remotely, I was hoping clean install would fix it. If you have instructions for a complete reinstall please let me know, happy to start again

Rod

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Fri, 24 Jul 2020 12:15:44 GMT

I have created

/Users/Watt/zephyrproject

in here I have

bootloader

modules

ncs

tools

zephyr

I have set up ZEPHYR_BASE as follows

ZEPHYR_BASE=/Users/Watt/zephyrproject/ncs/zephyr

then when I try to build

Watts-MBP-2:lte_ble_gateway Watt$ west build -b nrf9160dk_nrf9160ns
-- west build: generating a build system
Including boilerplate (Zephyr base (cached)): /Users/Watt/zephyrproject/ncs/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway
-- Zephyr version: 2.3.99 (/Users/Watt/zephyrproject/ncs/zephyr)
-- Board: nrf9160dk_nrf9160ns
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
CMake Error at /Users/Watt/zephyrproject/ncs/zephyr/cmake/generic_toolchain.cmake:64 (include):
  include could not find load file:

    /Users/Watt/zephyrproject/ncs/zephyr/cmake/toolchain//Users/Watt/armgnuemb/generic.cmake
Call Stack (most recent call first):
  /Users/Watt/zephyrproject/ncs/zephyr/cmake/app/boilerplate.cmake:509 (include)
  /Users/Watt/zephyrproject/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /Users/Watt/zephyrproject/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
  CMakeLists.txt:20 (find_package)


-- Found BOARD.dts: /Users/Watt/zephyrproject/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Found devicetree overlay: /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/nrf9160dk_nrf9160ns.overlay
CMake Error at /Users/Watt/zephyrproject/ncs/zephyr/cmake/dts.cmake:153 (message):
  command failed with return code: No such file or directory
Call Stack (most recent call first):
  /Users/Watt/zephyrproject/ncs/zephyr/cmake/app/boilerplate.cmake:510 (include)
  /Users/Watt/zephyrproject/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /Users/Watt/zephyrproject/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 -B/Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/build -S/Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway -GNinja
Watts-MBP-2:lte_ble_gateway Watt$

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Fri, 24 Jul 2020 11:27:11 GMT

It should be pointing to the Zephyr folder inside of the NCS folder that you initiated. e.g. /Users/Watt/NCS/zephyr

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Fri, 24 Jul 2020 10:34:55 GMT

Watts-MBP-2:~ Watt$ printenv ZEPHYR_BASE
/Users/Watt/zephyrproject/zephyr

Where should I be pointing?

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Fri, 24 Jul 2020 09:35:58 GMT

Rod, it looks like it's still fetching information from the zehpyrproject folder (Including boilerplate (Zephyr base): /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake)

Have you set zephyr base?

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Thu, 23 Jul 2020 22:15:36 GMT

Hi Øyvind,

No problem. I followed your instructions above but still seeing problems.

atts-MBP-2:lte_ble_gateway Watt$ west build -b nrf9160dk_nrf9160ns
-- west build: generating a build system
Including boilerplate (Zephyr base): /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway
-- Zephyr version: 2.3.0-rc2 (/Users/Watt/zephyrproject/zephyr)
-- Found Python3: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 (found suitable exact version "3.8.1") found components: Interpreter 
-- Board: nrf9160dk_nrf9160ns
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/Watt/gnuarmemb)
-- Found BOARD.dts: /Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Found devicetree overlay: /Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/nrf9160dk_nrf9160ns.overlay
nrf9160dk_nrf9160ns.dts.pre.tmp:92.42-104.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:201.18-207.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/uart@a000: duplicate unit-address (also used in node /soc/peripheral@40000000/i2c@a000)
  also defined at nrf9160dk_nrf9160ns.dts.pre.tmp:498.8-501.3
  also defined at nrf9160dk_nrf9160ns.dts.pre.tmp:605.8-613.3
nrf9160dk_nrf9160ns.dts.pre.tmp:341.19-347.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
-- Generated zephyr.dts: /Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/build/zephyr/include/generated/devicetree_unfixed.h

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:18: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:19: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:22: warning: attempt to assign the value 'y' to the undefined symbol AT_HOST_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:25: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:28: warning: attempt to assign the value 'n' to the undefined symbol BSD_LIBRARY_TRACE_ENABLED

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:31: warning: attempt to assign the value 'y' to the undefined symbol NRF_CLOUD

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9Parsing /Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/Kconfig
Loaded configuration '/Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig'
Merged configuration '/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf'
160/lte_ble_gateway/prj.conf:45: warning: attempt to assign the value 'y' to the undefined symbol DK_LIBRARY

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:46: warning: attempt to assign the value 'n' to the undefined symbol DK_LIBRARY_INVERT_LEDS

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:58: warning: attempt to assign the value 'y' to the undefined symbol BT_GATT_DM

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:59: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:60: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN_FILTER_ENABLE

/Users/Watt/zephyrproject/ncs/nrf/samples/nRF9160/lte_ble_gateway/prj.conf:61: warning: attempt to assign the value '1' to the undefined symbol BT_SCAN_UUID_CNT

error: Aborting due to Kconfig warnings

CMake Error at /Users/Watt/zephyrproject/zephyr/cmake/kconfig.cmake:217 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake:510 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 -B/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway/build -S/Users/Watt/zephyrproject/ncs/nrf/samples/nrf9160/lte_ble_gateway -GNinja -DBOARD=nrf9160dk_nrf9160ns
Watts-MBP-2:lte_ble_gateway Watt$

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Thu, 23 Jul 2020 07:42:30 GMT

Good morning Rod,

My apologies for the late reply. From your last comment, I agree that something is messed up.

[quote user="RodWatt"]Whats the easiest way to reinstall?[/quote]

Try to add a new folder to /Users/Watt/ e.g. NCS. Follow the instructions given here. Inside of /Users/Watt/NCS run the following command in terminal:

west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.3.0

This will clone the manifest repository into NCS. Once complete, run the following commands:

west update

west zephyr-export

Lastly, make sure to install dependencies:

pip3 install -r zephyr/scripts/requirements.txt
pip3 install -r nrf/scripts/requirements.txt
pip3 install -r bootloader/mcuboot/scripts/requirements.txt

Let me know how that works for you.

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Wed, 22 Jul 2020 07:22:05 GMT

Morning Øyvind,

This is what I have in my /Users/Watt/zephyrproject directory...

Watts-MacBook-Pro-2:zephyrproject Watt$ pwd

/Users/Watt/zephyrproject

Watts-MacBook-Pro-2:zephyrproject Watt$ ls

bootloader modules ncs tools zephyr

Yes, my Zephyr base is set to.

ZEPHYR_BASE=/Users/Watt/zephyrproject/zephyr

Under ncs, the only directory is nrf. Its empty.

I agree, it looks like my directory structure is messed up. I have tried to reinstall, please see my last posting, but this has failed.

Whats the easiest way to reinstall?

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Wed, 22 Jul 2020 06:59:45 GMT

Looks like there is some confusion ongoing. What is /Users/Watt/zephyrproject/? In your environment, ZEPHYR_BASE is set to: /Users/Watt/zephyrproject/zephyr

Have you tried to initialize NCS inside of a zephyr repo? As the output from your previous comment:

Watts-MacBook-Pro-2:nrf Watt$ pwd
/Users/Watt/zephyrproject/ncs/nrf

NCS is initialized inside of zephyrproject, and this includes another zephyr folder:
/Users/Watt/zephyrproject/ncs/zephyr

Please try to fix this first.

Kind regards,
Øyvind

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Tue, 21 Jul 2020 22:57:48 GMT

Watts-MacBook-Pro-2:nrf Watt$ west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.3.0
FATAL ERROR: already initialized in /Users/Watt/zephyrproject, aborting.
Note:
    In your environment, ZEPHYR_BASE is set to:
    /Users/Watt/zephyrproject/zephyr

    This forces west to search for a workspace there.
    Try unsetting ZEPHYR_BASE and re-running this command.

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Tue, 21 Jul 2020 22:43:19 GMT

sorry, forgot to add. I tried updating NCS, but see this

Watts-MacBook-Pro-2:nrf Watt$ pwd
/Users/Watt/zephyrproject/ncs/nrf
Watts-MacBook-Pro-2:nrf Watt$ git checkout master
fatal: not a git repository (or any of the parent directories): .git
Watts-MacBook-Pro-2:nrf Watt$

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

RodWatt — Tue, 21 Jul 2020 22:34:21 GMT

Hi Øyvind,

Not sure what version of NCS I'm using. This is what Im seeing..

Watts-MacBook-Pro-2:lte_ble_gateway Watt$ west build -b nrf9160dk_nrf9160ns
-- west build: generating a build system
Including boilerplate (Zephyr base (cached)): /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake
-- Application: /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway
-- Zephyr version: 2.3.0-rc2 (/Users/Watt/zephyrproject/zephyr)
-- Board: nrf9160dk_nrf9160ns
-- Found west: /Library/Frameworks/Python.framework/Versions/3.8/bin/west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/Watt/gnuarmemb)
-- Found BOARD.dts: /Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
nrf9160dk_nrf9160ns.dts.pre.tmp:92.42-104.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:341.19-347.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
-- Generated zephyr.dts: /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/build/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/Kconfig
Loaded configuration '/Users/Watt/zephyrproject/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig'
Merged configuration 'prj.conf'

prj.conf:18: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL

prj.conf:19: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT

prj.conf:22: warning: attempt to assign the value 'y' to the undefined symbol AT_HOST_LIBRARY

prj.conf:25: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY

prj.conf:28: warning: attempt to assign the value 'n' to the undefined symbol BSD_LIBRARY_TRACE_ENABLED

prj.conf:31: warning: attempt to assign the value 'y' to the undefined symbol NRF_CLOUD

prj.conf:45: warning: attempt to assign the value 'y' to the undefined symbol DK_LIBRARY

prj.conf:46: warning: attempt to assign the value 'n' to the undefined symbol DK_LIBRARY_INVERT_LEDS

prj.conf:58: warning: attempt to assign the value 'y' to the undefined symbol BT_GATT_DM

prj.conf:59: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN

prj.conf:60: warning: attempt to assign the value 'y' to the undefined symbol BT_SCAN_FILTER_ENABLE

prj.conf:61: warning: attempt to assign the value '1' to the undefined symbol BT_SCAN_UUID_CNT

error: Aborting due to Kconfig warnings

CMake Error at /Users/Watt/zephyrproject/zephyr/cmake/kconfig.cmake:217 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /Users/Watt/zephyrproject/zephyr/cmake/app/boilerplate.cmake:510 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /Users/Watt/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -B/Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway/build -S/Users/Watt/Documents/Switch_That/ZEPHYR_Code/nRF9160DK/lte_ble_gateway -GNinja

RE: Connecting the nRF9160DK to the nRF52833 over Bluetooth

Øyvind — Tue, 21 Jul 2020 18:47:59 GMT

[quote user="RodWatt"]1. The LTE_BLE_Gateway code is designed to run with the Thingy52 (or '91 I assume) only[/quote]

Thingy:52 only, as the Thingy:91 is LTE (reference design) similar to the nRF9160DK.

[quote user="RodWatt"]2. If I want want to connect the nRF9160DK to the nRF5233DK I should use the BT Peripheral LBS code. Do I use that on both systems? i.e on both the nRF9160DK and the nRF5233DK[/quote]

No, you have to keep the LTE_BLE_Gateway, however, you will need to modify it to connect with your application on the nRF52833DK. This application can be based on e.g. the BT Peripheral LBS sample. This way the 833 will send something to the nRF9160DK, where the nRF52840 Board controller running bluetooth-hci-uart sample will send this via UART to the application LTE Sensor Gateway sample running on the nRF9160.

[quote user="RodWatt"]I'm having problems building the LTE_BLE_Gateway code for the nRF9160DK;[/quote]

Can you please explain what the problem is? What version of NCS are you running?

Kind regards,
Øyvind