I'm evaluating the NRF9160 DK, and have run into some interesting issues.
I find that the AT client works, sort of, though it's quite flaky and I quite often get timed out commands, especially with the automatic sequences that LTE Link Monitor sends. In particular, I have to manually re-send the AT+CFUN? command several times to get anything to happen at all.
The real fun started when I tried to try out the asset tracker demo. I'd explain everything in detail, but it's exactly the same as issue #222766. I've updated the radio, I've tried everything Erik tried, with the same results.
However, I have something new to add.
I tried running the lte_ble_gateway app, which resulted in hanging with an exception. Then I re-programmed the AT firmware, and it didn't work, giving me this error:
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 200265f0
Secure Boot: prepare to jump to Non-Secure image
***** HARD FAULT *****
Fault escalation (see below)
***** BUS FAULT *****
Precise data bus error
BFAR Address: 0x50008120
***** Hardware exception *****
Current thread ID = 0x20023130
Faulting instruction address = 0x0
Fatal fault in ISR! Spinning...
What I noted is that if I kept resetting it using the reset button, eventually it worked, without any other changes, like so:
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 200265f0
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs2 *****
The AT host sample started
This seems really strange, and perhaps supports the defective hardware theory. It took about 8 cycles to get it to work. Hitting reset again landed it in the fault.
