issues with migration from ncs v2.5.0 to 2.6.1

RE: issues with migration from ncs v2.5.0 to 2.6.1

Elfving — Wed, 25 Sep 2024 12:24:41 GMT

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

RE: issues with migration from ncs v2.5.0 to 2.6.1

Dor Sadeh — Wed, 11 Sep 2024 14:43:00 GMT

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

RE: issues with migration from ncs v2.5.0 to 2.6.1

Jesse_Carpenter — Tue, 21 May 2024 14:11:37 GMT

Hi guys,
Thanks for the updates and suggestions. For me specifically, I used the DSP_FILTERING and DSP_STATISTICS config calls, and it seems that function calls from the filtering library no longer exist. The config options available in 2.6.99 seem to bring back this functionality, so I'm hopeful that when NCS 2.7 is released with Zephyr 3.6 this will be fixed.

RE: issues with migration from ncs v2.5.0 to 2.6.1

Elfving — Tue, 21 May 2024 11:02:48 GMT

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:

[quote user="ziv123"]

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

[/quote]

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.

[quote user="ziv123"]

CONFIG_CMSIS_DSP=y

[/quote]

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

RE: issues with migration from ncs v2.5.0 to 2.6.1

ziv123 — Sun, 12 May 2024 09:15:08 GMT

hi Elfving

though there is some more messages here still hoping for your replay on FFT issue mentioned ahead or other directions to reduce size of flash use .. there is also a question on this issue on discord under Nordic channel and there is also same question i saw on cmsis channel .. this is a blocker for migration and i hope there will be given some solution soon, its not mentioned in any guides that i see 🙏

RE: issues with migration from ncs v2.5.0 to 2.6.1

ziv123 — Sun, 12 May 2024 06:54:04 GMT

its possible that we use different api or include set, you can send the functions you have issues with and i can look if i use them and what i include for them

RE: issues with migration from ncs v2.5.0 to 2.6.1

Jesse_Carpenter — Fri, 10 May 2024 13:45:22 GMT

Hi Ziv,
Thanks for getting back to me.Im suprised you were able to get it to compile with just that call. When I remove the other config lines, my code still does not compile because the filtering functions are no longer included. I did however notice that in the 2.6.99 build, they are including those configs in the documentation. My guess is that they forgot to include them in the latest build, and are working to fix that in the next iteration. Glad its working for you though.

RE: issues with migration from ncs v2.5.0 to 2.6.1

ziv123 — Fri, 10 May 2024 07:19:31 GMT

Hi Jesse

basically just for the build to pass i removed all DSP configs which it did not recognise (my guess they are defined somewhere within now) but i keep this one only

CONFIG_CMSIS_DSP=y

and it compiles

the problem i see is that because this configs has been removed

# 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

the code now include all FFT tables which increases its size dramatically, i have no idea why they did it

.. still working on figuring out how to include only the FFT tables we need ..

any idea on that Nordic will be huge help

RE: issues with migration from ncs v2.5.0 to 2.6.1

Jesse_Carpenter — Thu, 09 May 2024 16:10:08 GMT

Hi Ziv,
I'm running into similar problems with the DSP libraries. Specifically I used to enable DSP filtering and DSP statistics, but now its not working. Simply commenting them out does not work and some of the function calls are not defined. Can you elaborate on how you solved most of your issues?

RE: issues with migration from ncs v2.5.0 to 2.6.1

ziv123 — Wed, 08 May 2024 14:35:42 GMT

i can not get memory report if build fail

but if i look at the nrf52840 board which i can build and i compare memory report of the same code build in 2.5.0 and 2.6.1 i see 25.52kb diff in Nordic Proprietary Libraries (58.31kb in ncs2.6.1 vs 32.79 in ncs 2.5.0)

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

so where does this come from and how can i reduce it back ?

RE: issues with migration from ncs v2.5.0 to 2.6.1

Elfving — Wed, 08 May 2024 12:52:28 GMT

Hard to say.

I would recommend having a look at the "memory report" in the Actions menu. You could open that up for the previous version of your application as well and compare.

Regards,

Elfving

RE: issues with migration from ncs v2.5.0 to 2.6.1

ziv123 — Wed, 08 May 2024 12:23:34 GMT

hi Elfving

solved most of the issues, and one board (nrf52840) builds fine but another board (nrf52832) fails on region.

region `FLASH' overflowed by 31504 bytes

31kb is a lot for a 64k ram and 512k flash.. seems very strange to me

any idea what configs maybe became =y by default that made such an increase ?

RE: issues with migration from ncs v2.5.0 to 2.6.1

Elfving — Tue, 07 May 2024 14:43:01 GMT

Hello Ziv,

[quote user=""]

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 ?

[/quote]

CONFIG_BT_CTLR_ADVANCED_FEATURES seems to have been dependent on the Zephyr controller in both 2.5.0 and 2.6.1, no changes there. My understanding is that CONFIG_BT_CTLR_ADVANCED_FEATURES opens up for some features that are only available for the Zephyr controller.

[quote user=""]

2. we use cmsis dsp

[/quote]

There is an overview over the available configurations here. Simply search for CMSIS_DSP to see what is available on a given version of NCS. Could you try to simply remove the configs that aren't supported and see what error you get? Maybe CONFIG_CMSIS_DSP will cover a lot.

[quote user=""]

[/quote]

Here it is: CONFIG_MEMFAULT_ROOT_CERT_STORAGE_CUSTOM. I think the link brought you to the latest version of Zephyr, in which it might not be anymore. I guess it defaults to not being selected. Could you expand a bit on the issue here?

[quote user=""]

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

[/quote]

I'll have to get back to you on this part, but I guess we might as well start with the 3 first points either way.

Regards,

Elfving