Same problem here - same build errors when building nrf/applications/asset_tracker on tag v0.4.0.
I'm using command-line build on my Windows PC using cmake and ninja to build the apps. Zephyr samples build, as does nrf/samples/nrf9160/at_client.
I'll track down the issue and update this thread.
Problem compiling zephyr/misc/generated/configs.c.
In file included from C:/iot/nordic/ncs/zephyr/include/toolchain.h:21:0, from zephyr/misc/generated/configs.c:7: zephyr/misc/generated/configs.c: In function '_ConfigAbsSyms': C:/iot/nordic/ncs/zephyr/include/toolchain/gcc.h:325:51: error: expected expression before ')' token "\n\t.type\t" #name ",%%object" : : "n"(~(value)))
Now with the asset_tracker application built, I am trying to run it without success - it fails with "Fatal fault in ISR! Spinning..". The "combined" image, containing the bootloader (so-called SPM = secure partition manager) and the actual application, is provided as merged.hex and is loaded to the board with the following command:
ninja flash
After flashing & rebooting, the console output is this:
....
SPM: NS image at 0x8000
SPM: NS MSP at 0x2002a638
SPM: NS reset vector at 0xfd55
SPM: prepare to jump to Non-Secure image.
Exception occurred in Secure State
***** HARD FAULT *****
Fault escalation (see below)
***** BUS FAULT *****
Precise data bus error
BFAR Address: 0x50008120
***** Hardware exception *****
Current thread ID = 0x20020470
Faulting instruction address = 0x12464
Fatal fault in ISR! Spinning...
I had already updated to the latest modem firmware: 0.7.0-29.alpha
But I ran it again... the DFU tool seems to work:
Start polling IPC.MODEM_CTRL_EVENT to receive root key digest Modem responded with a5000001 Modem root key digest received: 72b3d7c13e549acf08bbc48cb936b9b861e4cbae28a7537c9859a6d945ee9489 Store IPC DFU executable into shared memory Send IPC.APP_CTRL_TASK Start polling IPC.MODEM_CTRL_EVENT To receive 'Started' indication from DFU executable IPC DFU 'Started' indication from DFU received Updating modem firmware
...
Firmware digest received from modem: bf002e90453a1ed0566e8ff81580d78ef8bbd44cdf3886abf51dc853f9443349 Verification success
This did not help. Furthermore, the at_client sample application has never worked - before or after modem DFU - no response received from the modem, all AT commands time out. Is there any way to debug this? Does anyone know what's going on?
Now with the asset_tracker application built, I am trying to run it without success - it fails with "Fatal fault in ISR! Spinning..". The "combined" image, containing the bootloader (so-called SPM = secure partition manager) and the actual application, is provided as merged.hex and is loaded to the board with the following command:
ninja flash
After flashing & rebooting, the console output is this:
....
SPM: NS image at 0x8000
SPM: NS MSP at 0x2002a638
SPM: NS reset vector at 0xfd55
SPM: prepare to jump to Non-Secure image.
Exception occurred in Secure State
***** HARD FAULT *****
Fault escalation (see below)
***** BUS FAULT *****
Precise data bus error
BFAR Address: 0x50008120
***** Hardware exception *****
Current thread ID = 0x20020470
Faulting instruction address = 0x12464
Fatal fault in ISR! Spinning...
I had already updated to the latest modem firmware: 0.7.0-29.alpha
But I ran it again... the DFU tool seems to work:
Start polling IPC.MODEM_CTRL_EVENT to receive root key digest Modem responded with a5000001 Modem root key digest received: 72b3d7c13e549acf08bbc48cb936b9b861e4cbae28a7537c9859a6d945ee9489 Store IPC DFU executable into shared memory Send IPC.APP_CTRL_TASK Start polling IPC.MODEM_CTRL_EVENT To receive 'Started' indication from DFU executable IPC DFU 'Started' indication from DFU received Updating modem firmware
...
Firmware digest received from modem: bf002e90453a1ed0566e8ff81580d78ef8bbd44cdf3886abf51dc853f9443349 Verification success
This did not help. Furthermore, the at_client sample application has never worked - before or after modem DFU - no response received from the modem, all AT commands time out. Is there any way to debug this? Does anyone know what's going on?
