• State Verified Answer
  • Replies 4 replies
  • Subscribers 75 subscribers
  • Views 853 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 304390
Options

nRF52840 - FOTA - DFU Buttonless - Has Reserved Flash Issue Been Resolved - Address 0x27000 ?

johnwest

Hello All,

Working on the DFU buttonless build - have noticed the Reserved Flash overlap at address 0x27000 still exists - I tried to fix that in the flash_placement.xml file - but it still appears to be an issue.

We're using version 5.68 of the build tools.  With 7.2.1 - the app(s) won't even build.

Our app will download - starts to run but stops due to address conflicts in downloaded code (assumption at the moment) - when I connect with debugger it really doesn't say much other than the code is in the weeds.

Since apparently rRF SDK v17.1.0 isn't officially supported (where all of the 'easy to find' DFU code is) - for those of us that aren't using Zephyr in our project and never plan to - is this the best example to follow:

https://novelbits.io/nrf52-ota-dfu-ble-part-4/

Does Nordic have *any* DFU examples using the nRF Connect SDK 2.3.0 that *does not* require Zephyr?  If so - can you please post the link/reference here?

Thanks In Advance,
John W.

Parents
  • +1

    Hi,

    Since apparently rRF SDK v17.1.0 isn't officially supported

    The nRF5 SDK is still supported. However, it is in maintenance mode, so it will not receive updates with new features.
    See the nRF Connect SDK and nRF5 SDK statement for more information.

     

    Does Nordic have *any* DFU examples using the nRF Connect SDK 2.3.0 that *does not* require Zephyr?

    The nRF Connect SDK is built on the Zephyr RTOS. If you do not run Zephyr, you do not run the nRF Connect SDK.

    However, the bootloader and the application generally do not have to care about each other.
    This means you should be able to run an nRF5 Bootloader to boot an nRF Connect SDK application or vice versa.
    However, I would not recommend this approach unless there are specific reasons to do so.

    Regards,
    Sigurd Hellesvik

Reply
  • +1

    Hi,

    Since apparently rRF SDK v17.1.0 isn't officially supported

    The nRF5 SDK is still supported. However, it is in maintenance mode, so it will not receive updates with new features.
    See the nRF Connect SDK and nRF5 SDK statement for more information.

     

    Does Nordic have *any* DFU examples using the nRF Connect SDK 2.3.0 that *does not* require Zephyr?

    The nRF Connect SDK is built on the Zephyr RTOS. If you do not run Zephyr, you do not run the nRF Connect SDK.

    However, the bootloader and the application generally do not have to care about each other.
    This means you should be able to run an nRF5 Bootloader to boot an nRF Connect SDK application or vice versa.
    However, I would not recommend this approach unless there are specific reasons to do so.

    Regards,
    Sigurd Hellesvik

Children
Related
Terms of service