nRF9160 DK - at_client hex

[epetin]

Hi,

I have set up nRF9160 DK by following instructions here: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK/GetStarted#infotabs

By using nRF Connect v2.6.1 and Getting Started Assistant, I have configured Toolchain, cloned nRF Connect SDK from GitHub and configured SEGGER Embedded Studio successfully. I have set up project at_client successfully in SES. Now when I build the solution 'at_client', the only output hex file is "zephyr.hex". Is this the application that can be flashed to the device for example using nRF Connect Programmer? Or should I do some additional configurations to the SES before building?

tl;dr: how do I generate at_client.hex using SEGGER Embedded Studio?

[Einar Thorsrud]

Hi,

The zephyr.hex file is the application firmware, which is the AT Client in your case. Assuming the bootloader is already there you don't need anything else. Now that you have compiled it you can for instance program it using nrfjprog:

nrfjprog.exe --program zephyr.hex --sectorerase -r -f nrf91 --verify

[epetin]

Thanks! This is the information I needed.

[toninehjam]

Hello epetin,

Can you share your at_client.hex please? i cannot compile mine.

Best regards.

Toni

[epetin]

Hi Toni,

Could you paste your console output here so that we could try to resolve your compilation issue?

[toninehjam]