Release v0.6.0.

Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>

CMakeLists.txt

@@ -104,8 +104,18 @@ if (COPY_PREBUILDS)
    # and a second time with -DCOPY_PREBUILDS=On
 
    message(NOTICE "copy prebuild binaries into ${CMAKE_BINARY_DIR}/../prebuild")
-   file(COPY_FILE ${CMAKE_BINARY_DIR}/zephyr/merged.hex ${CMAKE_BINARY_DIR}/../prebuild/${BOARD}_full.hex)
-   file(COPY_FILE ${CMAKE_BINARY_DIR}/zephyr/app_signed.hex ${CMAKE_BINARY_DIR}/../prebuild/${BOARD}_app_signed.hex)
+   if (EXISTS "${CMAKE_BINARY_DIR}/zephyr/merged.hex")
+      file(COPY_FILE ${CMAKE_BINARY_DIR}/zephyr/merged.hex ${CMAKE_BINARY_DIR}/../prebuild/${BOARD}_full.hex)
+   else()
+      message(NOTICE "missing ${CMAKE_BINARY_DIR}/zephyr/merged.hex")
+   endif()
+   if (EXISTS "${CMAKE_BINARY_DIR}/zephyr/app_signed.hex")
+      file(COPY_FILE ${CMAKE_BINARY_DIR}/zephyr/app_signed.hex ${CMAKE_BINARY_DIR}/../prebuild/${BOARD}_app_signed.hex)
+   else()
+      if (NOT "${BOARD}" STREQUAL "nrf9160dk_nrf9160_ns")
+         message(NOTICE "missing ${CMAKE_BINARY_DIR}/zephyr/app_signed.hex")
+      endif()
+   endif()
 endif()
 
 if (CONFIG_COAP_SEND_INTERVAL)

README.md

@@ -35,7 +35,7 @@ For now, only [nRF9160](https://www.nordicsemi.com/products/nrf9160) based devic
 | Device | |
 | :- | - |
 | [Nordic Semiconductor, Thingy:91](https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91)<br>Works "out-of-the-box" in the "wild". Not easy to extend with custom sensors. | ![Thingy:91](./docu/thingy91.jpg) |
-| [Circuit Dojo, nRF9160 feather v5](https://www.jaredwolff.com/store/nrf9160-feather/)<br>Requires additonal batteries, antennas, and closures to work in the "wild". The design of the feather allows to easily add custom sensors. | ![nRF9160-DK](https://docs.jaredwolff.com/img/nrf9160-feather-v4-nobg.jpg) |
+| [Circuit Dojo, nRF9160 feather v5](https://www.jaredwolff.com/store/nrf9160-feather/)<br>Requires additonal batteries, antennas, and closures to work in the "wild". The design of the feather allows to easily add custom sensors. | ![nRF9160-feather-v5](https://docs.jaredwolff.com/img/nrf9160-feather-v4-nobg.jpg) |
 | [Nordic Semiconductor, nRF9160 DK](https://www.nordicsemi.com/Products/Development-hardware/nRF9160-DK)<br>Works "out-of-the-box" on the desk. The design allows to easily add custom sensors. | ![nRF9160-DK](https://www.nordicsemi.com/-/media/Images/Products/DevKits/nRF91-Series/nRF9160-DK.png) |
 
 The demo works with [ncs-2.3.0](https://github.com/nrfconnect/sdk-nrf/tree/v2.3.0).

docu/FASTTRACK.md

@@ -14,6 +14,10 @@ Download one of the [pre-build firmware images](../prebuild/) matching your devi
 
 Connect the `Thingy:91` to your debug probe and use the [nRF Connect Programmer](https://infocenter.nordicsemi.com/index.jsp?topic=/struct_nrftools/struct/nrftools_nrfconnect.html) to apply the downloaded pre-build firmware.
 
+Using [nRF Connect Programmer](https://infocenter.nordicsemi.com/index.jsp?topic=/struct_nrftools/struct/nrftools_nrfconnect.html) requires, that the device is detected as "genuine" Nordic devices. That unfortunately doesn't support to use other USB controllers. If a JLink probe is used, that target must be a "genuine" Nordic device and must be already connected starting the programmer app. Otherwise you may get an error message as
+
+   Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.
+
 ## Run It
 
 Go back to [README](../README.md#run-it).

docu/ROADMAP.md

@@ -11,6 +11,8 @@
 | 01-June-2022 |  v0.1   | Initial version.<br/>Known issues:<br/>Does not reconnect after network lost.<br/>Does not start proper without network |
 | 26-June-2022 |  v0.2   | Test experience.<br/>Both network issues are solved. |
 | 01-August-2022 |  v0.4   | Enable sensors.<br/> Includes support for Bosch Sensortec library for BME680 |
+| 11-November-2022 |  v0.5   | Add support for low quiescent current. |
+| 02-May-2023 |  v0.6   | Improve stability. Support AS-RAI and persistent storage. |
 
 (The 0.3 has been skip in order to not mix up to different build alreay used the 0.3.)
 
@@ -24,8 +26,8 @@ Ongoing developments:
 
 | Planed Date    | Version | Description |
 | -------------- | ------- | ----------- |
-| ??-September-2022 |   v?.?  | Improve accelerometer-meter |
-| ??-November-2022 |   v?.?  | GNSS |
+| ??-September-2023 |   v?.?  | Improve accelerometer-meter |
+| ??-November-2023 |   v?.?  | GNSS |
 
 # Roadmap - Server
 

prebuild/README.md

@@ -2,9 +2,9 @@
 
 # Zephyr - Coaps Demo Client with Eclipse/TinyDtls
 
-## Prebuild binaries v0.5.0
+## Prebuild binaries v0.6.0
 
-This folder contains 3 prebuild binaries intended to be used to get a first impression of CoAP / DTLS 1.2 CID.
+This folder contains 5 prebuild binaries intended to be used to get a first impression of CoAP / DTLS 1.2 CID.
 To gather more experience, please build and modify this example on your own.
 
 ## License
@@ -23,6 +23,19 @@ Please refer to [NOTICE](../NOTICE.md).
 
 Therefore, before you start, ensure, that you're common with the tools in order to reset you device back in the state before you apply this firmware.
 
+## [nrf9160 feather](https://www.jaredwolff.com/store/nrf9160-feather/)
+
+- [full image: dojo_feather_nrf9160_ns_full.hex](../../../raw/main/prebuild/dojo_feather_nrf9160_ns_full.hex) using a debug probe, this is the preferred approach
+- [signed app image: dojo_feather_nrf9160_ns_app_signed.hex](../../../raw/main/prebuild/dojo_feather_nrf9160_ns_app_signed.hex) app signed with the demo keys. Maybe used without debug probe via USB and [bootloader with newtmgr](https://docs.jaredwolff.com/nrf9160-programming-and-debugging.html#bootloader-use).
+
+For automatic bootloader support on linux, please ensure, that the permissions are granted by
+
+   SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60" GROUP="users", MODE="0666"
+
+in a file e.g. "50-nrf9160-feather.rules" and put in "/etc/udev/rules.d".
+
+For Windows you still need to switch on the bootloader mode manually by pressing the mode button during reset. 
+
 ## [nrf9160 Thingy:91](https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91)
 
 - [full image: thingy91_nrf9160_ns_full.hex](../../../raw/main/prebuild/thingy91_nrf9160_ns_full.hex) using a debug probe, this is the preferred approach