Firmware Version and SDK Version

K2AAE

What is a working combination?
Does FW 1.2.3 play well with 1.4.0 1.4.1 1.5.0 ?
Does FW 1.1.4 play well with 1.4.2 and 1.5.0 ?
Define Play well: as in allow building network application NOT Hello World.
I tried FW 1.1.2 but SDK 1.2.1 has no nrf9160dk only the nrf9160pdk and no feather.
What combination are you using?

jaredwolff

K2AAE I’ve been using 1.4.1 and 1.5.0 with 1.2.3.

There is an important distinction for the MFW versions. The 1.1.x branch is for Verizon and the 1.2.x branch is for vendors like AT&T. This is due to the different requirements the providers have for the functionality of the device itself. It only really matter when you go to deploy. You want to make sure the MFW is supported by that specific vendor and the LWM2M implementation for MFW upgrades also aligns with the providers requirements.

K2AAE

jaredwolff I was working (exploring) how NimbleLink can have FW 1.1.2 and use SDK 1.4.99, I think they are on 1.5.0 now since what I was reading was three months old. This could explain the Feather not connecting to Verizon with FW 1.2.3
More answers more questions

jaredwolff

K2AAE well.. from what I know from the process before technically they can’t. LWM2M OTA library is only certified to a specific NCS version. It’s very possible thought that they’ve built that into their at command image so it’s something that you’re not even exposed to.

K2AAE

jaredwolff Your right, they have completely changed the build method, SDK and how the app images are build. I do not have the required C++, python and GIT experience to even setup their build environment it seems. Reading their description of the process is like reading a foreign language. Matters not, I’m sticking a STM32L412 as a front end to their Verizon certified modem, I can work with CubeIDE, perhaps when I have a few months to spare I’ll revisit using their SDK. Meanwhile I can work with the Feather, I can understand it enough to more forward with the nRF9160. Bonus, not dealing with Thingspace!