Load via bootloader doenst seem to work after upgrade to v 0.3

[JeppeMariagerLam]

When i run build in the new version, the build now gets put into build/circuitdojo_feather_nrf9160_ns, but it doesnt seem that the load via bootloader command actually reads this dir - Instead, it just does nothing. If I copy the files into just build/ it seems to work, so I'm guessing the load via bootloader command isnt updated to follow the new build path or something? Also, I didnt get an error message for some reason :)

[jaredwolff]

Hi @JeppeMariagerLam!

By default the 'sysbuild' flag is active when building. That means you need to activate MCUboot using 'sysbuild.conf'.

SB_CONFIG_BOOTLOADER_MCUBOOT=y

You can read more up on it here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/config_and_build/configuring_app/sysbuild/index.html

I'm still learning about it as well so I may not have all the answers. 😄

Alternatively you can disable it and go back to using the original MCUBOOT config value by running the Zephyr Tools: Change Sysbuild Enable and select "No".

Hope that helps!

[JeppeMariagerLam]

I just tried both creating the sysbuild.conf file (in my app root), and setting the enabled flag to no, with build pristine inbetween both, but neither seemed to do the trick - No matter what, Load via Bootloader does nothing :( Note that no matter what I do with the sysbuild, it seems to place the build in build/circuitdojo_feather_nrf9160_ns - Not sure if that's expected or not

[JeppeMariagerLam]

I can jump on a quick call any time if you want to see it live - Might be faster than github issues :)

[jaredwolff]

@JeppeMariagerLam ahh gotcha. I think I know what's going on. v2.7.x branch is not fully supported and tested yet. I still need to configure the partitions to match the ones that are in the current bootloader. I'll try to give it a go later today. For now I'd recommend holding off using it if your only means of programming is via the USB bootloader.

[JeppeMariagerLam]

Gothca! I will downgrade to zephyr tools 2.4 and use that instead for now 😊

[jaredwolff]

@JeppeMariagerLam which board/target were you using? circuitdojo_feather_nrf9160/nrf9160/ns?

[JeppeMariagerLam]

I was using circuitdojo_feather_nrf9160_ns

…

On Fri, 2 Aug 2024 at 16.59, Jared Wolff ***@***.***> wrote: @JeppeMariagerLam <https://github.com/JeppeMariagerLam> which board/target were you using? circuitdojo_feather_nrf9160/nrf9160/ns? — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEXSIMUMWRCNYR2JJRBUVLZPOND5AVCNFSM6AAAAABL4MJ47WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGU4TGMRRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jaredwolff]

@JeppeMariagerLam board targets also change in NCS 2.7. It will be circuitdojo_feather_nrf9160/nrf9160/ns moving forward.

[jaredwolff]

@JeppeMariagerLam I just pushed 0.3.3 which should address the issues you were having. Make sure when you use Zephyr Tools: Change Board that you select the aforementioned build target. (circuitdojo_feather_nrf9160/nrf9160/ns)

It now builds with the correct partition layout and also accommodates for the new DFU output file (dfu_application.zip) payload.

[jaredwolff]

It may take some time to propagate. You can manually install with the attached zip/vsix file if you don't want to wait. 😉

zephyr-tools-0.3.3.zip

[jaredwolff]

Any luck @JeppeMariagerLam?