Where is app_update.hex equivalent used for OTA in SDK 0.15.0?

Golioth Device Help
1

The instructions at Zephyr Firmware Update Example Walkthrough | Golioth say to update CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION and use the output file build/zephyr/app_update.bin but this is no longer valid in SDK 0.15.0

Looking at the upstream Nordic SDK documents it’s all there in ncs-2.6.0 but I can’t find the equivalent file in the ncs-2.7.0 documents. I think it’s build/app/zephyr/zephyr.signed.bin but I can’t confirm this.
Where do I find the file to upload to the Golioth console?

Note: This page also includes a broken link to the deprecated Zephyr SDK that needs to be fixed.
Note: The Zephyr and Nordic pages have a ‘version’ selection to view documentation for different SDK versions. The Golioth documentation is not versioned at all so I never know which version of the SDK it’s referring to. This doesn’t work at all when you have different customers on different SDK versions and only one set of documentation that doesn’t reference what version it’s documenting. The entire documentation methodology needs to be updated.

3

Hey @john.stuewe ,

Thanks for catching that! We’ll update the Zephyr Firmware Update Example Walkthrough page to match the changes introduced in the Firmware SDK v0.15.0.

You can find the latest OTA update process in the fw_update example. The firmware version number is updated in the VERSION file, and the file to upload is zephyr.signed.bin located in the build/<app-name>/zephyr/ folder.

4

Thanks Marko.
Will Golioth be moving to a revision-tagged document system like Zephyr and Nordic? You’re starting to get a lot of SDK revisions out in the field and things like this change with every revision.

5

We have updated the Zephyr Firmware Update Example Walkthrough and it is in line with the recent changes made to the Firmware SDK and the Golioth Console.

Additionally, we discussed adding revision-tagged documentation to track changes but decided it makes the most sense to start doing that with version 1.0.0 of the Firmware SDK. By then, the SDK should be stable enough for version-specific documentation to be useful.