Re: Zephyr x nRF52 Inquiry
You can package them up using nrfutil so that they can update over the old Nordic SDK bootloader, you would just need to adjust the kernel load offset to after the softdevice and you wouldn’t be able to erase the softdevice, and would then use nrfutil like you would packaging a Nordic SDK application. The issue you have is that you’re using an nRF52832 with 512 or 256KB of flash and the current S132 softdevice uses 152KB of flash, the bootloader was 48KB or so if I remember rightly so that’s 200KB of 256/512KB flash used, to which you want to add a zephyr application with it’s own Bluetooth stack… Depending on the application and if you have any non-volatile data, you might find there is insufficient space for it to fit.
From: David Rances <david@...>
Sent: 03 May 2021 14:30
To: Jamie Mccrae <Jamie.Mccrae@...>
Subject: Re: [Zephyr-devel] Zephyr x nRF52 Inquiry
Thanks for the response.
Does that mean that if I have devices out in the field running firmware built on older Nordic code (SoftDevice and nRF52 SDK), the only way to get firmware built on Zephyr onto those devices would be to bring them in and physically erase/flash them? Since any existing methods to update the bootloader/application would be dependent on tools from Nordic that utilize the SoftDevice (OTA DFU) or their serial DFU using SLIP.
On Fri, Apr 30, 2021 at 4:51 PM Jamie Mccrae <Jamie.Mccrae@...> wrote:
David Rances | Embedded Engineer
Cell: +1 917 476 3696
NOTICE: This email and its contents/attachments may be confidential and are intended solely for the individual to whom it is addressed. If you are not the named addressee or if this email is otherwise received in error, please immediately notify the sender without reading it; do not take any action based on its contents or otherwise copy or disclose it to anyone, and note that any review, reliance or dissemination of this communication is expressly prohibited. Any opinions or views expressed in this transmission are solely of the author and do not necessarily represent those of StrongArm Technologies Inc. or its affiliates.