This folder contains 9 prebuild binaries intended to be used to get a first impression of CoAP / DTLS 1.2 CID. The compiled in destination server is californium.eclipseprojects.io. To gather more experience, please build and modify this example on your own.
Starting with 0.10.0, the "..._full.hex" binaries are required to be applied first using Jlink. That's required to initialize the new introduced settings service. Afterwards the update binaries may be used to update the device with new functions.
Also starting with 0.10.0, the prebuild binaries doesn't longer support updates via the serial bootloader interface. It's still supported using XMODEM or FOTA. For custom builds it may be reenabled using mcuboot.conf.
Please refer to NOTICE.
- NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. 6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.
- full image: circuitdojo_feather_nrf9160_ns_full.hex using a debug probe, this is the preferred approach and since 0.10.0 required as initial step.
- signed app image: circuitdojo_feather_nrf9160_ns_app_signed.hex app signed with the demo keys. May be used for updates using a debug probe after the initial full image.
- signed app update: circuitdojo_feather_nrf9160_ns_app_update.bin update app signed with the demo keys. May be used FOTA (CoAP) or XMODEM updates after the initial full image.
If the serial bootloader interface is enabled again for custombuilds, the "..._app_signed.hex" may be used for updates without debug probe via USB and bootloader with newtmgr. You need to ensure also, that "~/.zephyrtools/newtmgr/" and "~/.zephyrtools/zephyr-tools/" are added to your PATH.
In difference to the original mcuboot loader of the feather, which uses a baudrate of 1000000, the contained bootloader uses a baudrate of 115200, in line with the baudrate of the later logging and sh-communication.
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.
- full image: thingy91_nrf9160_ns_full.hex using a debug probe, this is the preferred approach and since 0.10.0 required as initial step.
- signed app image: thingy91_nrf9160_ns_app_signed.hex app signed with the demo keys. May be used for updates using a debug probe after the initial full image.
- signed app update: thingy91_nrf9160_ns_app_update.bin app signed with the demo keys. May be used for FOTA (CoAP) or XMODEM updates after the initial full image.
If the serial bootloader interface is enabled again for custombuilds, the "..._app_signed.hex" may be used without debug probe via USB and nRF Connect Programmer.
- full image: nrf9160dk_nrf9160_ns_full.hex using the onboard debug probe of the devkit. Since 0.10.0 required as initial step
- signed app update: nrf9160dk_nrf9160_ns_app_signed.hex app signed with the demo keys. May be used for updates using a debug probe after the initial full image.
- signed app update: nrf9160dk_nrf9160_ns_app_update.bin app signed with the demo keys. May be used for FOTA (CoAP) or XMODEM updates after the initial full image.