issues with migration from ncs v2.5.0 to 2.6.1

[ziv123]

hello Nordic

i am working with ncs v2.5.0 (with nrf52840 and nrf52832) and trying to migrate to ncs v2.6.1

i have looked at this migration notes and guids:

https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/releases_and_maturity/releases/release-notes-2.6.1.html

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_guide_2.6.html

https://docs.zephyrproject.org/latest/releases/migration-guide-3.6.html

https://docs.zephyrproject.org/3.6.0/releases/release-notes-3.6.html

yet i did not find solution fo some things there:

1. the config CONFIG_BT_LL_SW_SPLIT was set to =n in v2.5.0 in order to work with softdevice instead of zephyr ble controller and it enables some ble features like connection report and dynamic tx power etc.

now, in zephyr 3.5.99 this config CONFIG_BT_CTLR_ADVANCED_FEATURES  is dependent on CONFIG_BT_LL_SW_SPLIT=y (which appears to be experimental but do i really have a choice to not use it if i want the mentioned features? ), so it seems like it is forcing me to work with zephyr ble controller am i missing something ? 

and this is actually an issue because now i see that 'sdc_hci_vs.h' i get "No such file or directory " because it is under the softdevice controller dir ?? 

2. we use cmsis dsp

and now they are all undefined so what can i use instead , cause i have undefined api in mt code now ? 

3.

 

4. init a device with APPLICATION level is deprecated now, what can i do instead ?

this is for now, there will probably be more issues as i continue

hope to read you soon

best regards

Ziv

[Elfving]

Hi again and sorry about the wait

I see you've posted a bit to the discord channel before, so I am not sure what questions are left. Though here is a few comments:

ziv123 said:

also under the No paths there is a 11kb extra in 2.6.1

Hard to say where this exact part comes from. 

You are right in that you won't get a memory report when the build doesn't finish, and I understand how that can be annoying in this situation. One thing you could try in order to simply analyze the memory requirements is to build it for a board with a larger memory. 

Either way, the best way forward is to try to add back one feature at the time and see what that takes up memory wise. 

ziv123 said:

CONFIG_CMSIS_DSP=y

I think a bit of the reasoning is mentioned here, and looks like the finer control over what features to use is added back in Zephyr 3.6 (~NCS 2.7). You can have a look through the KConfig options of 2.6.99 and see if you like what we've done there.

Here is also an issue which might be both interesting to you and maybe solve the issue Jesse here is facing.

Regards,

Elfving

[Dor Sadeh]

We are now trying to migrate to NCS 2.7.0 and I can't still hand pick FFT tables as was possible in ncs 2.5.0 by using

CONFIG_CMSIS_DSP_TABLES_ALL_FFT=n

CONFIG_CMSIS_DSP_TABLES_RFFT_FAST_F32_1024=y

CONFIG_CMSIS_DSP_TABLES_RFFT_FAST_F32_4096=y

this makes the code size too big to fit into one of our devices.

any ideas how to hand pick only the RFFT_FAST_F32_1024 and RFFT_FAST_F32_4096 FFT tables?

in the image: ROM report, specifying that some tables such as twiddleCoef_2048 is added and increasing code size

[Elfving]

Hi,

Hmm I thought all of the control you previously had would come back in 2.7, though I guess not. Since this is mainly a zephyr problem, as opposed to Nordic I am not sure what more to suggest if you still want to use this NCS version. 

Could you try asking about this in the Zephyr discord?

Regards,

Elfving