• State Not Answered
  • Replies 13 replies
  • Subscribers 76 subscribers
  • Views 1678 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 326427
Options

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

Parents
  • 0

    Hello Ziv,

    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 ? 

    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.

    2. we use cmsis dsp

    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.

    3.

     

    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?

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

    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

Reply
  • 0

    Hello Ziv,

    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 ? 

    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.

    2. we use cmsis dsp

    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.

    3.

     

    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?

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

    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

Children
Related
Terms of service