nRF9160 DK nRF52

RE: nRF9160 DK nRF52

Hoang — Thu, 07 Mar 2019 09:38:21 GMT

Thanks, I will try it later

RE: nRF9160 DK nRF52

Martin Lesund — Tue, 05 Mar 2019 13:16:09 GMT

Hi Hoang,

Could you confirm that you used these settings when building the samples?

- SW5 to nrf52

- hci_uart

-build and flash for the nrf52

-SW5 to nrf91

- Build and flash for nrf91

Then power cycle the nrf91 DK and check the LTE Link Monitor. (it may take a while to get a link to the basestation the first time)

- make sure to uncheck the "Automatic requests" to use the LTE Link Monitor as a regular serial terminal:

I am adding the .hex files as well.

You can flash these .hex files using the command line:

nrfjprog --program hci_uart.hex -f nrf52 -r --sectorerase --verifydevzone.nordicsemi.com/.../hci_5F00_uart.hex

nrfjprog --program lte_gateway.hex -f nrf91 -r --sectorerase --verifydevzone.nordicsemi.com/.../lte_5F00_gateway.hex

Best Regards,

Martin L.

RE: nRF9160 DK nRF52

Hoang — Tue, 05 Mar 2019 09:00:32 GMT

Dear Martin,

I tried to follow the userguide:
1. Programmed Bluetooth: HCI UART for nRF52: done

2. Programmed Secure Boot and LTE_BLE_Gateway for nRF91: Done

then run Putty to test:

Secure Boot: SPU: set SRAM region 12 as Non-Secure
Secure Boot: SPU: set SRAM region 13 as Non-Secure
Secure Boot: SPU: set SRAM region 14 as Non-Secure
Secure Boot: SPU: set SRAM region 15 as Non-Secure
Secure Boot: SPU: set SRAM region 16 as Non-Secure
Secure Boot: SPU: set SRAM region 17 as Non-Secure
Secure Boot: SPU: set SRAM region 18 as Non-Secure
Secure Boot: SPU: set SRAM region 19 as Non-Secure
Secure Boot: SPU: set SRAM region 20 as Non-Secure
Secure Boot: SPU: set SRAM region 21 as Non-Secure
Secure Boot: SPU: set SRAM region 22 as Non-Secure
Secure Boot: SPU: set SRAM region 23 as Non-Secure
Secure Boot: SPU: set SRAM region 24 as Non-Secure
Secure Boot: SPU: set SRAM region 25 as Non-Secure
Secure Boot: SPU: set SRAM region 26 as Non-Secure
Secure Boot: SPU: set SRAM region 27 as Non-Secure
Secure Boot: SPU: set SRAM region 28 as Non-Secure
Secure Boot: SPU: set SRAM region 29 as Non-Secure
Secure Boot: SPU: set SRAM region 30 as Non-Secure
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 2002c898
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs2 *****
Application started
Bluetooth init failed (err -19)
[00:00:28.585,662] <err> bt_hci_core.bt_enable: No HCI driver registered

How can i fix it ?

Regards,

hng

RE: nRF9160 DK nRF52

Hoang — Tue, 05 Mar 2019 07:36:09 GMT

Dear Martin,

Thanks for helping, I will try

Regards

hng

RE: nRF9160 DK nRF52

Martin Lesund — Tue, 05 Mar 2019 07:34:46 GMT

Hello Hoang,

You cannot build/flash bluetooth samples to "nrf9160_pca10090" since it is not a chip that supports BLE.

If you are building for the nrf52840 chip that is on the nrf91DK you need to change the "Board directory" to "nrf52840_pca10090".

- nrf9160/nrf52840 (decides which chip)

- pca10090 (is the name of the nrf91 DK)

A recommended exercise for you to do is to build/flash the LTE Sensor Gateway sample.

Since there you will need to build/flash one sample to the nrf9160 and one for the nrf52840. (remember to use SW5 to the correct chip you want to program)

if you have a Thingy:52 as well you can now test out that sample by turning the Thingy:52 to each side and you will see on the nRF Cloud that an alarm will be sent each time the THingy:52 is on a specific side.

Hope this makes things a bit clearer.

Best Regards,

Martin L.