Re: Managing/structuring multi image/binary projects for (OTA updatable products etc)
Marc Reilly
Hi Marti, Sebastian, list Thanks for the ideas, my replies are inline below. > Hi, I see you are using nrf. This led me to find the "multiple images" documentation for the NCS Zephyr (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/application/index.html#building-and-configuring-multiple-images) ... > So if not using vanilla Zephyr is an option then see: .. it looks like the NCS capabilities will do what I wanted with regard to building a bootloader + app in one go. I haven't had time to look at it properly, but it seems like the strategy is to make the bootloader an extra output of the primary 'app' project (ie extra targets in the app project cmake). This is a different approach than what I was thinking of. I was envisaging that the bootloader and app were treated as more isolated projects, and were configured and glued together by another higher level _something_. Traditionally, I tend away from relying too much on vendor 'BSP's for the long term, they've tend to stagnate or diverge too much from mainline as time goes on. Does anyone know if there are any plans to bring NCS's 'multi-image' functionality into mainline zephyr? --snip--
This is useful to know, thanks ! I thought about your BOARD_ROOT question. I've gotten other similar I think what I was envisaging was something to glue together the above commands (and keep some separation between the specific 'app' and the bootloader), I thought this would be 'west', but maybe not.. to take this approach would mean having to invoke the build/sign/whatever commands from the 'west installation' folder, and it would only be available from the manifest repo folder.
Done!, thanks. Marc |
|