Just checking in, I am recently starting to develop cellular communication and looking to develop on the nRF9160. I have been in nRF52 space and with that I develop inside the SDK 17 directory structure. I build and deploy binaries from the armgcc directory, meaning that I use the make toolchain to build and program my devices. Starting my development of the nRF9160 I am reading the mounds of documentation available which is directing me into another directory structure for the SDK, 1.6.1.
I understand the process to change the .hex file to accommodate a certain chip or a certain board but to change the board on the new development paradigm, not so much. How do I change the the ability to accommodate the nRF9160 DK for the at_client sample?
I have started developing RTOS a couple of years ago and I have a toolchain for Zephyr and it is based on the git repository using a tool called west. I understand that SDK 1.6.1 has this same structure. I am reading over some things and see a folder structure that calls out what a correctly installed Zephyr directory looks like, I compare that to mine and their is no module directory in mine. I am wondering if my old Zephyr toolchain will work with my new SDK 1.6.1?
Thank you!
