v2.7.0 thingy53

RE: v2.7.0 thingy53

runsiv — Mon, 08 Jul 2024 09:00:10 GMT

[quote user="tldr"]

There was no mention of the ipc_radio changes in migration/release notes; without it my 2.6.1 code that worked no longer worked without the change. https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/ipc_radio/README.html I don't see anything else to read up on about this.

[/quote]

It is mentioned in the migration note https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.7.html#samples_and_applications_using_short-range_radio

[quote user="tldr"]

the new_name project builds as expected. The output is not in zephyr\zephyr.elf it now is within c:\ncs\v2.7.0\nrf\samples\new_name\build\new_name\zephyr\zephyr.elf

This is strange.

[/quote]

I agree. I have tried to reproduce what you are seeing however I can't replicate it with using either sysbuild or the old build system. . Do you build with or without sysbuild?

If you are using sysbuild the .elf should be inside buildname/b0n/zephyr

Shot in the dark. Which version of the nRF Connect extension for VScode are you using? Do you see the same behaviour if use switch to pre-release?

Regards

Runar

RE: v2.7.0 thingy53

tldr — Fri, 05 Jul 2024 12:00:49 GMT

The build produced a zephyr.elf in the expected location in 2.6.x;

When I build now it does not show up there, it shows up in build/project_name/zephyr/zephyr.elf.
I have the project inside c:\ncs\v2.7.0\nrf\samples\project_name.

I didn't see where project_name was coming aside from the folder name so I copied the project to another folder in samples.

Strangely, the newly copied project now named new_name; references the old project even when doing a --pristine. I deleted the build folder manually and it no longer referenced the old project (pristine is not enough apparently).

the new_name project builds as expected. The output is not in zephyr\zephyr.elf it now is within c:\ncs\v2.7.0\nrf\samples\new_name\build\new_name\zephyr\zephyr.elf

This is strange.

Additionally, in case this is helpful, the name I have defined in CMakeLists.txt is not used...at least not for this output location. Maybe these settings are affecting the build, IDK but the elf file is not where it typically is.

project(another_name)

zephyr_compile_definitions(PROJECT_NAME=${PROJECT_NAME})

RE: v2.7.0 thingy53

runsiv — Fri, 05 Jul 2024 11:36:10 GMT

Hi David

[quote user=""]

I'm not sure if its the ipc_radio is needed; it by itself did not fix it, it was a combination of the two and now bluetooth is working.

[/quote]

With NCS 2.7 all samples and applications fore multi image SoC was migrated to use IPC radio fw as the default image for the network core.

Is this a readymade sample or a custom application?

[quote user=""]

but there is no elf in zephyr?

[/quote]

It should be. I checked a few samples that I have compiled today and I have them. There is also no mention of any changes to zephyr.elf in the sysbuild migration guide

Regards

Runar