Topics created by d00616

@lorenzo said in nRF5 OTA updates: Hi, Any news on that? If needed I can help developping. No news from my side. Currently I have no time to work on this feature. You can fork my Repository https://github.com/d00616/ArduinoHwNRF5 to finish the work. It's possible to send a new firmware and the image is new replaced by the bootloader but with the first interrupt the MCU is crashing. For NF52 MCUs, I think this problem is fixable by moving the IV-Pointer to the image maybe there is an problem by different memory layouts of Arduino and Zephyr (used to compile mcuboot).

https://github.com/sandeepmistry/arduino-nRF5 Install this and find libraries for whatever sensors you have on that board. @basaksts said in nRF5 Multi Sensor Board (12-14€): Also I need an bootloader No, you really don't. You need ST-Link, or J-Link SWD programmer/debugger. Connect it to SWDIO, SWCLK, 3.3V and GND and program it using Arduino IDE.

@Eurbaix partially correct. All radios have encryption support in version 2.0 of the library for obfuscation. (I know that you know that now, I just add it here for documentary reasons). But there are limitations in the security solution. Primarily due to the limitations of the HW "base" supported at the time of implementation.

I agree. In general, security mechanisms other than OTA/message related (signing/encryption) should be part of the bootloader, since that is the area where absolute control can be enforced on what to execute (fw validation, etc).

I have checked the hwGetentropy() on my x86 Linux. When https://github.com/mysensors/MySensors/pull/830 is merged, I create a new Pull Request.