v2.7.0 thingy53

[tldr]

I'm going from v2.6.1 to v2.7.0; I'm using a thingy53.  I'm getting a voltage error prior to boot.

[00:00:00.002,929] <err> voltage: setup: -134
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***

and my bluetooth is not getting setup correctly.
[00:00:06.025,360] <err> bt_hci_driver: Endpoint binding failed with -11
[00:00:06.025,360] <err> bt_hci_core: HCI driver open failed (-11)

[00:00:06.025,421] <err> bt_hci_driver: Failed to send (err -2003)

ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:333
command opcode 0x1009 timeout with err -11
[00:00:16.025,573] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00000002
[00:00:16.025,573] <err> os: r3/a4: 0x00000003 r12/ip: 0x00000010 r14/lr: 0x0001a24d
[00:00:16.025,573] <err> os: xpsr: 0x09000000
[00:00:16.025,604] <err> os: Faulting instruction address (r15/pc): 0x0001a25c
[00:00:16.025,634] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:16.025,665] <err> os: Current thread: 0x20003c68 (main)
[00:00:16.252,563] <err> os: Halting system

I tried to 

arm-zephyr-eabi-addr2line -e build\zephyr\zephyr.elf
arm-zephyr-eabi-addr2line: 'build\zephyr\zephyr.elf': No such file

but there is no elf in zephyr?

found it in arm-zephyr-eabi-addr2line -e build/<projectname>/zephyr/zephyr.elf 0x0001a25c
C:/ncs/v2.7.0/zephyr/subsys/bluetooth/host/hci_core.c:335

If I don't call bt_enable(NULL); the program runs as exected (still with voltage error)

--

ran as expected but without bluetooth; looking at multiple_adv_sets; I saw a new sysbuild and Kconfig.sysbuild.  Pulled those, it didn't crash as before instead gave opcode 0x2005 status 0x0c.

added

CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_MAX_ADV_SET=2

CONFIG_BT_DIS=y
CONFIG_BT_DIS_PNP=y
CONFIG_BT_DIS_MANUF="Nordic Semiconductor ASA"
CONFIG_BT_DIS_PNP_VID_SRC=2
CONFIG_BT_DIS_PNP_VID=0x1915
CONFIG_BT_DIS_PNP_PID=0xEEF1
CONFIG_BT_DIS_PNP_VER=0x0100

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.

I'm not sure how to resolve the <err> voltage: setup: -134.

[runsiv]

Hi David

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.

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? 

but there is no elf in zephyr?

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

[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.

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})