Problem with MQTT_Simple

[craig.goldman]

I am having a problem running MQTT_Simple on my nRF9160 DK.

The COM Port shows the following:

***** BUS FAULT *****
  Precise data bus error
  BFAR Address: 0x4002a514
***** Hardware exception *****
Current thread ID = 0x20000324
Faulting instruction address = 0x6704
Fatal fault in essential thread! Spinning...

I have recently updated SES, but the code still produces the bus fault.

Case ID: 226428 seems to be similar, but the discussion involves several "experiments" only some of which were productive.

So, could someone explicitly lists the steps needed to get this example working.  I wish to use it as the basis for a new product that sends data to the cloud.

Thank you,

-Craig Goldman

[JKST]

Have you tried updating to the latest firmware for the nrf9160 DK? Did you try "west update" to get the latest release?

Also when, using the latest versions, you have to use build solution, connect target and then program the merged.hex file like mentioned here:

https://devzone.nordicsemi.com/f/nordic-q-a/47032/mqtt_simple-programmed-to-wrong-address-range-00008000----00020abb

[craig.goldman]

Thank you for your response (and sorry for the delay in responding).  I was not aware that I had to do something special to program the merged file.

I am preparing to do a complete new download of the NCS directory and will try all these suggestions in the next few days.  I will report my results.

[craig.goldman]

I am using SES version v.16

I re-downloaded the entire NCS project.

I have opened mqtt_simple as an nRF connect project for board "nrf9160_pca10090"

The project build produces the following error...
    C:/Users/info/Dropbox/64Seconds/NCS/nrf/lib/bsdlib/bsd_sanity.c:8:2: error: #error bsdlib must be run as non-            secure firmware. Are you building for the correct board ?
         Build failed

The code window indicates the failure is in "bsd_sanity.c"
     #ifndef CONFIG_TRUSTED_EXECUTION_NONSECURE
     #error  bsdlib must be run as non-secure firmware.\
        Are you building for the correct board ?
    #endif

Will mqtt-simple work with the nRF9160 DK?  (PCA10090)

Another question... How do I determine the version of the modem firmware on the PCA10090 board?

[JKST]

Craig,

In the current version of SES, you have to select the 'nrf9160_pca10090ns' instead of the normal one as the Secure build will be automatically included. Try following the steps then that I put in the previous link for building and loading the project.

The firmware you should be able to check over UART, f.e. through the LTE Link Monitor (or another).

[craig.goldman]

I appreciate your help, but I am not making much progress.

I switched the board to nrf9160_pca10090ns.
I cleared out the build directory so I get a clean build.

The "Open nRF Connect SDK Project" fails.

The end of the log shows the following....

Zephyr version: 1.14.99
-- Found PythonInterp: C:/Python37/python.exe (found suitable version "3.7.2", minimum required is "3.4")
-- Selected BOARD nrf9160_pca10090ns
-- Found west: C:/Python37/Scripts/west.exe (found suitable version "0.5.8", minimum required is "0.5.6")
-- Cache files will be written to: C:\Users\info\AppData\Local/.cache/zephyr
USING OUT OF TREE BOARD
CMake Error at C:/Users/info/Dropbox/64Seconds/NCS/zephyr/cmake/kconfig.cmake:135 (message):
  File not found:
  C:/Users/info/Dropbox/64Seconds/NCS/zephyr/boards/arm/nrf9160_pca10090ns/nrf9160_pca10090ns_defconfig
Call Stack (most recent call first):
  C:/Users/info/Dropbox/64Seconds/NCS/zephyr/cmake/app/boilerplate.cmake:500 (include)
  CMakeLists.txt:10 (include)

-- Configuring incomplete, errors occurred!
Project load failed
Reported error: solution load command failed (1)

Any thoughts?

There are three pca100090ns files:

nrf9160_pca10090ns.dts
nrf9160_pca10090ns.yaml
nrf9160_pca10090ns_defconfig

Is something else needed?

-Craig Goldman

[Øyvind]

Hi Craig, 

In SES, can you please go to:
Tools --> Options --> nRF Connect

Make sure your Zephyr Base is pointing to: 
C:/Users/info/Dropbox/64Seconds/NCS/zephyr/

Let me know how that works for you.

Kind regards,
Øyvind