Mqtt_simple sample error.

[henninglindseth]

Trying to up load mqtt_simple sample, however getting bus fault on terminal. have browsed after the same issue here, but don't work after doing git pull ect...

here's the output:

***** BUS FAULT *****

 
 Precise data bus error

  
BFAR Address: 0x4002a514

***** Hardware exception 
*****

Current thread ID = 0x2000033c

Faulting instruction address = 0x70b8

Fatal 
fault in essential thread! Spinning...

[Øyvind]

Hello Henning, 

Did you see this thread? Similar bus fault with the MQTT Simple Sample.

Kind regards,
Øyvind

[henninglindseth]

Yess, gjorde alt på vei ned til ninja flash.     fikk dette ut på terminalen:

C:\gnuarmemb\bin\arm-none-eabi-objcopy.exe: zephyr.hex 64-bit address 0x4b4fa300000000 out of range for Intel Hex file
C:\gnuarmemb\bin\arm-none-eabi-objcopy.exe:zephyr.hex: bad value
ninja: build stopped: subcommand failed

[henninglindseth]

and on west init:

USN+103438@S-HVE9127 MINGW64 /c/ncs2
$ west init -1 nrf
usage: west init [-h] [-m MANIFEST_URL | -l] [--mr MANIFEST_REV] [directory]
west init: error: unrecognized arguments: nrf

[Øyvind]

The ninja flash stopped because you whitelisted important libraries. 

[Øyvind]

This should fix this; it is not -"one" it is -"small L"

west init -l nrf

(liten L)

[henninglindseth]

Yea, I'm embarrassed, I found it out yesterday, sorry for the inconvienience.

I'm very thankful for the help.

best regards

Henning

[wischmi2]

Was anyone ever able to get the "bus fault" fixed?  I'm also having this issue after trying to use mqtt sample.

[craig.goldman]

I am having this same problem.  Quite frankly the software updates in this thread are hard to follow (at least for me).  Can someone summarize what really needs to be done to get MQTT Simple running.

I have just (today) upgraded SES.

To re-iterate what I think others are seeing, the terminal is outputting...

***** 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...

Should I create a separate case or is this one still open?